There is a discussion in github about this ongoing, please join if you want to chime in or if you can provide additional research and user or market stories!
opened 10:09AM - 08 Feb 17 UTC
closed 11:33AM - 17 Apr 19 UTC
Design & UX
Known Issue / Workaround
Original issue: https://github.com/nextcloud/server/issues/3036
Closed there, b… ecause it's a client issue and those should be tracked here, I was told.
If an SQLite file, that's currently open in its application, is synced and the client resolves a conflict by downloading the server version of the file, saving it under the original file name in the local folder and renames the local file to "...conflict...", the application that uses the file has troubles accessing the file and data is lost.
### Expected behaviour
The client should not rename local files (because they could be in use). Instead, my suggestion would be that the server version of the file, that's downloaded, is saved under the local name "...conflict..." instead.
### Actual behaviour
explained above
### Steps to reproduce
1. Put as SQLite file (e.g. a file created with NoteCase Pro (www.notecasepro.com) using the ncdb file format (not the other formats, as they are not SQLite-based!) into an owncloud-synced directory. Leave the file open in NoteCase Pro.
2. Trigger, that owncloud/nextcloud wants to sync the file in both directions (in my case, the reason was, that I moved the entire data repository to a new directory and updated the server; for some reason, occ wanted to sync "down" the server version of the file then. I have not modified the file on the server or any other client - a server bug? But not relevant here.)
3. Make changes to the local version of the file, to also trigger a sync
4. Start the owncloud client and let it sync the file, renaming the local version
5. In NoteCase Pro, file still open, make changes to the file and save (*)
6. See, that in NoteCase Pro the changes are not persistent (selecting another note and then the modified note again --> changes are gone!)
(*): Please do, like I did, a LOT of very important changes, about 2 hours of work. Then you get a feeling how frustrated I was when I finally realized that no data was saved! ;-)
### Server configuration
Operating system: Linux 4.7.0-0.bpo.1-amd64
Web server:
Apache 2.4.10
Database:
MariaDB
PHP version:
5.6.29
ownCloud version:
Nextcloud 11.0.1
Storage backend (external storage):
### Client configuration
Client version:
Nextcloud client 2.2.4 (build 1)
Operating system:
Mac OS X 10.11.6
OS language:
de
Qt version used by client package (Linux only, see also Settings dialog):
--
Client package (From ownCloud or distro) (Linux only):
--
Installation path of client:
default: /Applications/nextcloud.app
### Logs
n/a