the app still save automatically, even when you just view the file, not edit it.
the app destroy my important .doc file, it make the .doc file blank !!
This issue seems to have been fixed in the latest 6.4.13 version.
@xxxddd, please update your Collabora office version and test again.
thank you. I download the app from Index of /downloads/Collabora-Office-Android-Snapshot
I try the new arm64 version. the problem is not fixedā¦
Hello all.
We are in June 2023 and the bug is still there.
As soon as you start modifying a file, it is automatically saved without your consent. Thatās very bad when amending a file from someone else.
Itās a pity. I wonāt be able to use this software.
Iām curious - how do other applications deal with this? Ultimately an app on Android can be expired and torn out from underneath you by the OS without any user interaction at all. Clearly until you start editing by explicitly pressing the āeditā button we will not save anything but ā¦ what is the standard? If you edit a note for example - and donāt hit save what happens; for eg. Samsung Notes (my first random test) - I get the same behavior.
Now of course - if you are viewing, and not editing the file; we should not save anything of course; but quite probably we just badly need to get a new 23.05 based version into the app store for testing.
Iām curious - how do other applications deal with this?
Yep, Iād be interested too.
I mostly just use basic text editors on Android, and only mess with TXT files. These do not modify the original file at all until I explicitly hit the āSaveā button.
And I suspect these donāt often (ever?) get shoved out by the OS because they have such low RAM usage, that the OS has bigger fish to fry.
Ultimately an app on Android can be expired and torn out from underneath you by the OS without any user interaction at all.
Yes, this is a thing too.
This might get much more complicated, because weāre not dealing with basic TXT filesābut ODT/DOCX + much larger files (may push on deviceās free RAM, ā¦).
These types are much more likely to get:
- aggressively put to sleep or flushed by the OS.
- ripped away while in the middle of autosaving a large/complicated file.
- You may think nothing is occurring, so you swap to other apps or turn off screen.
Similar situation if youāre flipping back/forth between browsers+apps. So often, I lose Private Mode tabs or what I was just trying to copy/paste between apps, because the dang OS flushes the RAM in between steps.
This makes multi-tasking on mobile much harder, so I tend to just do:
- Viewing + very light editing on Mobile
- Heavy editing + everything else on Desktop
but quite probably we just badly need to get a new 23.05 based version into the app store for testing.
Yes, this is key. I am all for that! 
Once we get Android up-to-date with the latest version, that should (hopefully) mitigate many of these issues too.
Perhaps it would be worth saving an āautosave copyā to a separate file like some editors on desktop do and then restoring it if we are expired by the OS? That would avoid the original file being modified and also avoid losing all your work if the app is closed.
Of course thatās possible - the down-side is that when you next try to load a document youāll have to go through a recover-saved-edited-version flow, and also handle the matrix of problems there: what if the original version has meanwhile been upgraded - what does the UX look like for this ?
Iām convinced that if you press the āeditā button in the UI - and start editing the file instead of viewing it; you should be prepared for it to silently save on exit. If we can reproduce a problem whereby it saves & over-writes in view mode in 23.05 - as/when we release that - then thatās something we should fix: that should never happen.
Otherwise - if the industry comparison shows that everyone else is doing it some different way - fine, lets re-think. For me the basic text file thing - of Samsung notes auto-saves - and for other TXT file editors - Iād love to see screenshots of the flow of force quitting the app, re-loading another TXT file and seeing what the de-confliction UI looks like, as well as when another app has changed the TXT underneath. Thanks.
2 Likes