are you saying the changes are not in the iOS copy the next time you BUILD the iOS version?
or are you saying they changes don’t just “appear” when you change the desktop version?
The first I would expect to work, the second I would not, since each device has its own instance of the database file.
I have a similar situation (although I haven’t gotten to the “synch” stage yet). But what I plan to do is use iTunes filesharing to allow the desktop access to a copy of the iOS database, and then move the updated desktop database back to the i device. I hope you have a method in place (UUID?) to be able to tell which device added, deleted or changed a record so they CAN be synched.
Also, and I’m not sure if this is correct or not (Norman??), but the encryption between the desktop version and iOS version is not compatible??? If that is the case, you need to share an unencrypted version… but I may be wrong in the assumption about compatiblity.
Ah… well in XCODE, you need to do a “Clean Project”, as each app/device combo gets its own “working space” in the simulator and that is not necessarily rebuilt on each compile.
HOWEVER, that is what XCODE does, I don’t know what Xojo for iOS does.
I thought you meant keeping a iOS version of the data in synch with a Desktop version . Which is what I am needing, as the iOS version of my app updates a database, and the desktop version can update its database, but at some point BOTH need to be reconciled and end up with the same data. Part of this requires that records NEVER be deleted (just marked as such) until the two platform synch.
When app goes for apple review a test DB need to be in there (Resource) so app will be usable?
And when the user first get the app the test DB is there for the user, but only gets copied if not already in Doc folder so that when user iTunes Sysc his DB it will replace the test DB?