Weird!
Well I rolled back to 1.8.10 and problem solved. (maybe it has to do with syncing bases?)
I don’t need bases for mobile anyway, so that is not an issue.
Thank you.
Weird!
Well I rolled back to 1.8.10 and problem solved. (maybe it has to do with syncing bases?)
I don’t need bases for mobile anyway, so that is not an issue.
Thank you.
but we you had the problem in a regular note, not a base?
How does the the local file history from the recovery plugin look like.
This has happened a few times to me. I think this is what happened the most recent time:
Another clue is that the sync file history does not contain the first version at all, but the file recovery does.
The issue may happen when there are multiple independent changes to a note.
For example we begin with Note A that is synchronized in both device 1 and device 2.
If device 1 and device 2 both independently make changes to note A, without having the possibility to synchronize in between, then the automatic merge algorithm can produce undesirable outputs.
However, there is no way really to fix this, because when there are multiple conflicting changes, only YOU (the user) know what’s right. No algorithm can merge them correctly.
There are currently two way to go about this:
Note A-conflict will be generated and you have to manually review it Note A and Note A-conflict for changes.I am asking anyone who is experiencing the issue in this thread to switch to the new “create conflict file” option and let me know what happens.
If after enabling the new “create conflict file” option, you experience conflict files being created even when NO editing has been done on multiple devices, please go here and provide the requested info.
Because Sync only notifies about conflicts in its activity log which is cleared when the app restarts, I suggest also bookmarking a search for File:“conflicted copy”.