starred/CoreStore
1
0
Fork 0
mirror of https://github.com/JohnEstropia/CoreStore.git synced 2026-01-11 20:00:30 +01:00
Code Issues 95 Packages Projects Releases 10 Wiki Activity

Crash: looking for .momd file when using CustomMappingProvider #235

New Issue
Closed
opened 2025-12-29 15:27:10 +01:00 by adam · 1 comment
adam commented 2025-12-29 15:27:10 +01:00
Owner
Copy Link

Originally created by @mbain on GitHub (Oct 23, 2018).

I get the following crash when using a CustomMappingProvider:

❗ [CoreStore: Fatal Error] XcodeDataModelSchema.swift:57 from(modelName:bundle:migrationChain:)
  ↪︎ Could not find "Tocca.momd" from the bundle "io.tocca.ina". Other model files in bundle: 0 item(s) []

Both models are CoreStoreObjects, and I do not have a .xcmodeld file. As such, I don't have a good way to generate a .momd file. My understanding of the situation is that CoreStore should be able to handle the migration given the CustomMappingProvider, without a .momd file. Am I missing something?

Originally created by @mbain on GitHub (Oct 23, 2018). I get the following crash when using a CustomMappingProvider: ``` ❗ [CoreStore: Fatal Error] XcodeDataModelSchema.swift:57 from(modelName:bundle:migrationChain:) ↪︎ Could not find "Tocca.momd" from the bundle "io.tocca.ina". Other model files in bundle: 0 item(s) [] ``` Both models are CoreStoreObjects, and I do not have a .xcmodeld file. As such, I don't have a good way to generate a .momd file. My understanding of the situation is that CoreStore should be able to handle the migration given the CustomMappingProvider, without a .momd file. Am I missing something?
adam closed this issue 2025-12-29 15:27:11 +01:00
adam commented 2025-12-29 15:27:11 +01:00
Author
Owner
Copy Link

@JohnEstropia commented on GitHub (Nov 3, 2018):

@mbain This usually means you are accessing CoreStore somewhere earlier than your DataStack creation, which would trigger creation of a lazy, default-configured DataStack. You can put a breakpoint inside get in public static var defaultStack: DataStack inside CoreStore.swift to see where in your code triggers the lazy creation.

@JohnEstropia commented on GitHub (Nov 3, 2018): @mbain This usually means you are accessing `CoreStore` somewhere earlier than your `DataStack` creation, which would trigger creation of a lazy, default-configured `DataStack`. You can put a breakpoint inside `get` in `public static var defaultStack: DataStack` inside *CoreStore.swift* to see where in your code triggers the lazy creation.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
abandoned
corestore bug
discussion
duplicate
enhancement
fixed
fixed
help wanted
in progress
investigating
ios/compiler bug
irreproducible
looking for workarounds
not a bug
pending
pending docs update
pull-request
Mirrored from GitHub Pull Request
 question
regression
user bug
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/CoreStore#235
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?