I know that the culprit is that the model isn't in the CloudKit schema.
I also know that the fix is to push the model to the development environment which is why I described the steps I'd take to do just that.
As I said in the beginning, I've had this model in CloudKit since its inception. And I've added other models previously.
From day 1 I've never had to do anything with NSPersistentStoreDescription or Request Core Data load the store synchronously, to guarantee that the load finishes before you attempt to initialize the CloudKit schema.
I did do any of that when I first created the data models or when I added models or anything.
I've always just opened the app in Test Flight and then the new models were in CloudKit development and then I could deploy the schema changes.
So, you're telling me....that method doesn't work any longer?
And now I have to write a segment of code I've never had to write before in order to get the new model into CloudKit?
I mean, I guess thank you for the links but that seems unusual that a method that's worked for multiple apps over the past year or so just...doesn't work any more?
Topic:
App & System Services
SubTopic:
iCloud & Data
Tags: