Records should be synced before the Mobile file is updated, right? Otherwise, data from the current Mobile file would be lost.
Plus, the records should be synced again, after the update, because the new version inside the EasyDeploy container doesn't necessarily have all the data.
I tested the sample files, including EasyDeploy, which contained a new version of the Mobile file. Unfortunately, modifications to the current Mobile file were lost during sync, I think because the Mobile file was replaced before it could sync with the host.
Can you confirm please if I'm on the right track here... The sequence for sync should be:
1. Sync with host.
2. Replace current Mobile file if update is available.
3. Sync with host again if Mobile file was just updated.
Thanks,
=L=