I observed similar behavior as the other user, where the contents of the note did change and reflect the correct contents when the slider was positioned at the latest version and after clicking the "Restore Note" button, but as soon as I interacted with the note in any way (clicking mouse cursor inside the text field, scrolling the window) the note would immediately revert to the incorrect version from 11:30 PM.
The correct version that should have been pulled down was from 6:35 PM. This was not simply the previous version, but 27 versions out-of-date.
#Force simplenote to sync update#
The last update for the note in question happened on 5:40 PM, but the Windows client had reverted that note to a much earlier version from 11:30 PM. It does not always pull down changes that have been made via Android or Web clients (and I can verify that those have synced properly because the note contents are identical.įor example, I just opened the Windows client and observed that my note did not reflect the changes that had been made via the Web client earlier. I have not had issues with syncing between the Android or Web clients, but Windows 1.12.0 is unreliable. When I look back through the history and select the version that had my last changes (from 3 days ago), that version stays on my screen - until I try to edit it, at which point it reverts. I am repeatedly seeing the note I'm currently working on revert back to an older snapshot, without my intervention.
Also, I expect that when I use the History function (to set the note back to a snapshot in time), that using the "Restore Note" button will reset the note to that version. I expect the that the note I'm working on saves to the last version in which anything was written. Can you please add some force-syncing option that will will not update a note's version unless there is confirmation the change has syncc'ed - or something? It's clear that the desktop app is not syncing reliably to the Web right now. If I can't rely on my edits getting saved, I'm hosed. Guys, this is really frustrating and this is not the 1st time this has happened.
0 kommentar(er)
