Today, I performed the update (6.0.0.17092) for the desktop client (MacOS 13.7.7 Intel). Afterwards, everything was resynchronized and numerous errors were reported. In the end, 159 files and folders were deleted from the server. The log states that they were added to the blacklist. However, some of these files and folders have been there for years. PDF, JPG, text files, and many other file types, as well as entire folders. There is no logic to be found in the criteria used to delete and blacklist them.
What happened?
This is a disastrous situation, and I will have to uninstall OC if I want to save my data!
h.
Translated with DeepL.com (free version)
/EDIT:
The files are not deleted locally. The client always displays the following entry under “Not synchronized”: File /path/name cannot be deleted due to a conflict with the local file name of /path/ name/. At the end of the list it says: Added to blacklist.
EDIT/
Expected behaviour
proper synchronization
Actual behaviour
Numerous files and folders are deleted from the server and the files are blacklisted.
Thank you very much for this information. I missed this thread because it only referred to umlauts and I didn’t see this (correct) connection yet. Furthermore, the thread does not mention the fatal circumstance that not only is synchronization not working, but also that masses of files and folders are being deleted on the server.
I deleted the client, reinstalled the previous version, and restored everything in a few hours.
I don’t understand why there have been recurring problems with the character set for decades. Some people should perhaps be given a globe as a gift.
I kinda understand the frustration. Macs do things differently when it comes to encoding in file names, and have historically done so. It’s a mess, but my main question centers around your processes: if such a severe bug was introduced in major release version of a dedicated Mac desktop client, it seems like there was no testing done at all on the Mac client? Because otherwise the bug would have been pretty easy to spot. I hope after this is over, you are also taking a thorough look at your testing and release processes?
Thanks for your efforts in this unfortunate matter, also clearly visible in the other thread and fingers crossed that we get a fixed and syncing and stable version soon. Best regards, Florian
May I ask for clarification, just to be on the safe side? I downgraded my version to 5.3.2.
Am I correct in understanding that this particular problem was fixed in version 6.0.1? Version 6.0.2 is now available. So I can safely perform the update?
Yes! Could somebody please confirm this as fixed in 6.0.2 – we’re dealing with substantial data loss, dozens of folders are continually deleted unless we replace the umlaut in the folder name