Same issue even without SwiftData, just boilerplate iOS 18 code

Encountered the same issue. Tried reinstalling and restarting, but none of it works. Hope this could be adressed soon, or at least a workaround would be provided. Already filed a report using Feedback Assistant.

Same here! do we all just wait after 24 hours?

Thanks. I have now translated English to English instead of just having the grayed-out version of the Keys in the String Catalog. I think this might be it. Will update once it's been released in the App Store.

Same. Feels like a mouse lag. Mostly encountered it when doing drag and drop, and highlighting a bunch of text.

It's now back. It seems filling-out the English Translations fixed it.

I've experimented with it a bit and these are what I found out. There are no automatic lightweight migrations, you have to write every changes to your model in the migration If you do not create a lightweight migrations, your app will crash. CONCLUSION: If you have transitioned to a VersionedSchema, you now have to write every lchanges to your model in the migration or else your app will crash.

@jonduenas thanks for this! Fixed the crashing issue. However, I still can't get my didMigrate closure to work. I ended up with the following setup just in case it might help someone Used solution above for handling container Used MigrationStage.lightweight in my migration plan Move manual migration code to a View.task This has worked for me.

Wow! Now I understand, thank you very much. This has been very insightful. Building up on the previous example, what could be possible causes why didMigrate is not being called? I wrote a print statement and some code, but it's never run. static let migrateV1toV2 = MigrationStage.custom( fromVersion: SchemaV1.self, toVersion: SchemaV2.self, willMigrate: nil, didMigrate: { context in print("Running Post Migration") // post-migration code here } ) My current workaround was to run the post-migration code outside the MigrationStage.

Same issue :( but relieved it's not isolated to me.

Thanks for posting this! It still has this problem with visionOS 2.4 I thought I was doing something wrong