Some critical bugs in the application sync process:
1. Null pointers can occur on obfuscation of the entity sync results
2. Retrieving the synced time registrations (since a last successful sync) does
not set the sync-key if not already set
3. If an incoming entity to be synced has a sync key but the entity with that
sync key is not found the resolution needs to be NOT_ACCEPTED and
synchronization for that entity-instance should be aborted
4.
Original issue reported on code.google.com by dirkvran...@gmail.com on 14 Jan 2013 at 1:26
Original issue reported on code.google.com by
dirkvran...@gmail.com
on 14 Jan 2013 at 1:26