I am experiencing a serious problem with TeamDrive overwriting local changes without any notification. Something like this has been reported in "TeamDrive setzt Dateien zurück auf alten Inhalt" (http://forum.teamdrive.net/viewtopic.php?f=4&t=968), but in a different system environment and in "Speicher offline->TD ersetzt Dateien durch ältere Versionen?"(http://forum.teamdrive.net/viewtopic.php?f=4&t=2843), but only in relation to losing server connections.
I am using TeamDrive 4 Version 4.1.6 (Build 1443) on Android 5.1.1 and on Android 4.2.2, both showing the same behaviour.
How to repeat:
- Prerequisites:
- A file in a space on the mobile device (let's call it tdtest.odt, typically located in a path like /storage/emulated/0/Android/data/com.teamdrive.client/cache) with
- content "Status 1"
- synchronized with the server
- configured to be available offline
- Open file on mobile device through file manager in Android OpenOffice (AOO)
- Change content to "Status 2".
- Quit AOO.
- Open file through file manager again in AOO.
- Verify that content is still "Status 2".
- Quit AOO.
- Check on other client that no new version has been uploaded to the space.
- Open file on mobile device though the TeamDrive client in AOO.
- Verify that content is back at "Status 1".
- Quit AOO.
- Open file on mobile device though a file manager again.
- Verify that content is still at "Status 2".
Without any warning whatsoever, the TeamDrive Client has wiped the local change. Only when I open the file through the TeamDrive client, return from the editing application to the client, will the client ask me wether I actually want to keep the changes.
I have used the file manager here for clarity, but applications that keep their data in a standard file fall into this trap regularly.
Especially after switching from DropBox, which has no problems with this scenario, this is a very unpleasant suprise. I am thoroughly amazed that this quite normal use case is handled this way.