What is the expected / best strategy to migrate a synced Core Data model to a new version?
The issue:
A new app version with a new Core Data model introducing new attributes or entities. DeviceA installs the update and edits data with new values and creates new entities.
DeviceB is still used and downloads these changes. The unknown attributes and entities are ignored, but the HistoryTracking gets updated.
A few days later DeviceB gets the update. The missing attributes and entities are not downloaded, as the history is up to date.
__
The issue exists with iOS 13, I hoped for iOS 14 to introduce a strategy. I tried with the first iOS 14 beta, but it is at least not handled automatically.
From the visible API changes I don't see a way to handle this specifically. Not sure if the talks will reveal anything about it.
Will apply for a lab session and would like to get as much input to prepare before that might take place.
The issue:
A new app version with a new Core Data model introducing new attributes or entities. DeviceA installs the update and edits data with new values and creates new entities.
DeviceB is still used and downloads these changes. The unknown attributes and entities are ignored, but the HistoryTracking gets updated.
A few days later DeviceB gets the update. The missing attributes and entities are not downloaded, as the history is up to date.
__
The issue exists with iOS 13, I hoped for iOS 14 to introduce a strategy. I tried with the first iOS 14 beta, but it is at least not handled automatically.
From the visible API changes I don't see a way to handle this specifically. Not sure if the talks will reveal anything about it.
Will apply for a lab session and would like to get as much input to prepare before that might take place.
