Mikescher/AlephNote

Sync error with StandardNotes causing lots of conflict notes

Closed this issue · 4 comments

icheyne commented

Log.xml.log

Mikescher commented

Hmm

Seems like a bug in the conflict resolution strategy "Use Client Note and create conflict file".
We create a conflict file but the note is still recognized as an conflict in the next sync

By the way: Better not upload your log files publicly on github, if you're unlucky you had an expired token in that session and AlephNote had to re-auth with the server. Then it would be possible to reverse-engineer half of your password (the server-auth part) from the logs
But - to be fair - without the log files I would be totally stumped what the problem is. So I'm not sure what the solution is. Perhaps email me the log separately?

  • 👍1
Mikescher commented

Argh what a stupid bug. I probably looked for half an hour at the code without seeing it.

This line note.RawModificationDate = item_syncconflict.servernote.ModificationDate should be this note.RawModificationDate = item_syncconflict.servernote.RawModificationDate

  • 😄1
icheyne commented

Thank for doing this so quickly. I'll upgrade and let you know how I get on. :-)

  • 👍1
icheyne commented

I upgraded and it works perfectly. Thanks again. 😁