First sync on tomdroid fails because of wrong LATEST_SYNC_REVISION
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Tomdroid |
Fix Released
|
Medium
|
Unassigned | ||
Beta |
Fix Released
|
Medium
|
Unassigned |
Bug Description
(line 61):
LATEST_
The LATEST_
Tomboy on linux also uses -1 as initial value, as one can see when opening the manifest.xml from tomboy before any syncing was done.
Because of the initial value of 0, I can reproduce a failed sync in the following scenario:
Set Tomboy to sync with the server for the very first time and initially send some notes -> The LATEST_
Now when using tomdroid to PULL those notes, Tomdroid successfully connects, retrieves a list of notes (which need to be pulled), and receive a server-side LATEST_
This bug does NOT appear if
a) you sync with tomboy fore more then 1 time before using tomdroid (as then the LATEST_
b) you create a note in Tomdroid prior to pulling the notes, as the first note will have a _local_ "last-sync-
and hence isn't that obvious to find :)
My suggestion: Change the initial value of LATEST_
Disclaimer: I am shooting into the dark here as I don't have an Android SDK and can't build the source, nor do I use Ubuntu1; all my assumptions are based on my work on an experimental new sync server, but which works currently for tomboy when doing 2way syncing. So please assure my suggestion do not break Ubuntu1 sync.
Changed in tomdroid: | |
milestone: | none → 0.7.3 |
assignee: | nobody → Stefan Hammer (j-4) |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in tomdroid: | |
status: | Fix Committed → Fix Released |
Hi!
I set the last-sync-revision initialisation to: SYNC_REVISION ("latest_ sync_revision" , -1L),
LATEST_
Could you please try with your setup again and report back, if it is fixed now?! Pretty please :-D
Thanks a lot!
grab the build here again: http:// goo.gl/ #analytics/ goo.gl/ fKg6N/all_ time