Question

I want to run a Core Data migration that applies a value transformation on a property, specifically mapping one string value to another, which I don't believe can be handled by a lightweight migration.

Eventually (but not in the next release of my app), I want to add iCloud sync. I read that iCloud sync requires you to only use light-weight migrations. Can I use a non-lightweight migration now and then integrate iCloud sync later, and will doing so make things harder for me later?

Was it helpful?

Solution

Yes, you can implement iCloud later, i.e. after the non-lightweight migration. No, things should not be harder for you later. You can assume iCloud does not store your versioned models to construct the final managed object model, but just takes the final one. It is the migration itself that iCloud would not support.

That being said, I have had dismal experiences with iCloud and Core Data. Don't say you have not been warned.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top