Autosave is unreliable

[the-antz]

I noticed that sometimes recent changes are lost when I get back. As a workaround I switched to always manually saving before closing the app which seems to be reliable.

The lost-changes thing seems to happen mostly when quickly leaving the app after making changes.

Maybe there could be a setting to switch the back-behaviour between save and cancel.

[tasn]

Interesting, thanks for reporting! A few questions:

1. Android or iOS?
2. How are you closing the app? Just "minimising" it, or actually closing it in the switcher or something?
3. What do you mean by switch the back-behaviour between save and cancel?

The data is supposed to be saved both periodically (every few seconds) and when leaving the page. What could be happening though, is that maybe it's not saving the recent changes you made and then tries to sync with the server causing the local changes to be removed. I can see how this could maybe be happening if you close the app quickly enough. It shouldn't be hard to fix, just please confirm the questions above.

[the-antz]

Hi, thx for the quick response.

1. Android (a LineageOS build with microG and some unrelated apps preinstalled)
2. I used the Android back button. I guess using the Android home button (or app switcher) won't trigger the bug as afaik it should not stop the app.
3. I did not know it saves the changes every few seconds, this makes the proposed "cancel-behaviour" not work anyway. What I meant was a setting like "on-close" with possible values "save" and "cancel", where "save" would be the current behaviour, and with "cancel" it would show a confirmation dialog when pressing back if there are unsaved changes. The use case for that would be that I can discard changes if I accidentally fat-finger up my notes :D.