-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sync conflict - then crash #211
Comments
(by peter-frohberg) Environment-Setup:
Is there any chance to get a log? I'm not familiar with android development, but I would love to help solving this major(!) bug. |
(by khertan) This happen only when sync is initiated at start of the app. The workarround is to cancel sync via physical back button when tomdroid ask for a choice on a sync conflict. TomDroid is still maintained ? Using Grauphel 0.5.0 and TomDroid 0.7.5 on a galaxy a3 with Android 5.0.2 |
(by khertan) |
(by tobias-kaminsky) |
I am also affected by this. |
Same here :/ |
I'm using Tomdroid 0.7.5 with Grauphel 0.4.0 for about 2 Month.
recently Tomdroid came up the first time with a sync conflict between the server the local data (I don't really know why). Tomdroid shows me where the conflicts are (there are many lines) and gives me the choice which data to keep or to replace.
I select, keep the server data, but then Tomdroid crashes.
The same happens when I chose to make a copy of the note.
Now I'm stuck with that screen and can't get to my notes list. There is no "cancel" button there (I guess it would be good if there would be one there). Ah, I just noticed that I would have to go back and provoke the sync window to come up. then I can cancel the syncing and get to my notes. Still IMO there should be a cancel button on that conflict screen.
When I've canceled the process and I'm in the notes list and syncronise, THEN all of a sudden it syncs ok.
So I don't know why the conflict was there in the first place. But at least I found out that the above way solves the issue.
Imported from Launchpad using lp2gh.
The text was updated successfully, but these errors were encountered: