Hello,
I am willing to understand how to do a graceful update at the client side, after a new deployment has been made at the SUP side.
Assume that you have an app (iOS for my case) working well integrated with the SUP backend. Then:
1) Make a change in the MBO model; it could be as simple as adding a new field into an existing MBO.
2) Deploy your changes. Create the new generated code in the process.
3) Apply the newly generated code to the app. Update the client app.
4) The calls to the SUP Backend fails with SUPSynchronizationException.
I understand why the calls to the backend are failing; the client database schemas are no longer in sync with the newly deployed backend database. There could also be versioning differences that SUP checks.
Basically, what is necessary is: During the update of the client app, the client database schemas also get updated. This is a known concept in the Core Data world in iOS (https://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/CoreDataVersioning/Articles/Introduction.html). Does such a concept exist in the SUP world as well?
Thanks,
Guven.