We repeatedly encounter significant issues with Windows clients starting with version 3.16.x and also with the current client 4.0.6 in connection with long path and file names (longer than 256 characters).
If a check mark is removed for a folder in the sync client, it appears that this folder cannot be deleted on the local drive. The sync client displays the following error message: “Temporary error removing a local object removed from the server.” Strangely enough, all files in this subfolder structure are deleted, but the folders remain. They are then just empty. The fatal flaw in this problem is that if you re-check the box for this folder, all files and folders for this specific folder will be deleted from the Nextcloud server during the next synchronization.
They can only be restored from the “Deleted Files” folder or from a backup.
However, the older client with version 3.15.3 does not seem to have this problem.
Here, everything works fine when a folder check mark is deactivated. The folder is deleted locally, no error message appears, and the data is still available in Nextcloud. This can be easily verified with a test folder (with long and deep paths).
Problem that can be reproduced so far:
If a check mark is removed from a folder in the Nextcloud sync client because it is no longer needed locally and contains very long path and file names, it is not deleted locally. Although all files appear to be deleted, the entire folder structure remains on the local drive (D:\Nextcloud). Afterwards, the error message “Temporary error removing a local object removed from the server” is displayed.
Under no circumstances should you attempt to delete or move this folder manually. Also, do not check the box again! Otherwise, the folder will also be deleted in the cloud, which must be prevented at all costs. If this is detected, the Nextcloud client must be paused and terminated immediately!
Since I have determined after several tests that this problem does not appear to exist with the older client in version 3.15.3, it would be advisable to downgrade to this version until the problems with Nextcloud are resolved by a current, stable, and error-free client.
Has anyone else encountered this problem, and is there a workaround for it?