I'm migrating an existing Core Data app to SwiftData and encountering a persistent schema hash mismatch that prevents the store from loading. The Core Data store has been in production for years with version 4 of the model. I have two models, lets call the Crew and Astronaut Create is a parent in the to-many relationship to Astronaut, the child. When I try the migration, the Crew model‘s hash matches, but the Astronaut model’s mismatches. I also tried changing relationship parameters; deleteRule, maximumModelCount, inverse, originalName, and hashModifier. hashModifier changes the hash, but to a third value, so it does not appear to be a way to match the existing Core Data hash. So, is there a supported way for SwiftData to generate an optional to-one relationship that is Core Data hash-compatible with optional=YES minCount=1 maxCount=1? Or is a migration/rehash/copy step required before SwiftData can adopt this V4 store in place?

Upon updating to Xcode 14.0, then selecting the Editor > Validate Settings, a resulting dialog with a single item for WatchKit is displayed. The item is to upgrade existing Watch and Watch Extension targets to a single-target watch app. When I hit the button Perform Changes, Xcode instantly crashes. Is this happening to anyone else? The problem report contains ... Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction: 4 Terminating Process: exc handler [27932] Application Specific Information: com.apple.main-thread Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 Xcode3UI 0x131df0e98 Xcode3UpgradeWatchKitExtensionlessUpgradeTask.upgrade() + 14392 1 Xcode3UI 0x131df191b @objc Xcode3UpgradeWatchKitExtensionlessUpgradeTask.upgrade() + 27 2 IDEKit 0x10be7ffa5 __49-[IDEUpgradeTaskWindowController performChanges:]_block_invoke + 483

Hello:My app's entire production public database was cleared. All user data is gone. I do not see how that could have happened. But it looks to have happened this morning at around 5 AM GMT.Has anyone experienced this before?