Hi folks, I switched to the “new” sync client with the Apple FileProvider API (yes, i immediately switched over), and since then I am having constant sync conflicts. Unfortunately I seem unable to actually resolve them:
the list does not show any errors as far as I can see
the “resolve” button does … nothing
So I am kinda stuck here
Also, I know this is very broad – i don’t have more information, unfortunately.
Still – any hints / recommendations?
The Basics
Nextcloud Server version (e.g., 29.x.x):
Nextcloud 32.0.12.1
Operating system and version (e.g., Ubuntu 24.04):
Mac OS 26.5.2 (25F84)
Web server and version (e.g, Apache 2.4.25):
hosted offering, no idea
Reverse proxy and version _(e.g. nginx 1.27.2)
hosted offering, no idea
PHP version (e.g, 8.3):
hosted offering, no idea
Is this the first time you’ve seen this error? (Yes / No):
no, but before I had methods to resolve it – that changed.
When did this problem seem to first start?
after updating to the Apple FileProvider sync method
Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
client: DMG install via homebrew
server: hosted offering, no idea
Are you using CloudfIare, mod_security, or similar? (Yes / No)
hosted offering, no idea
Summary of the issue you are facing:
having sync conflicts in the desktop client without information what it is, or a way to resolve.
Steps to replicate it (hint: details matter!):
upgrade client
switch to new FileProvider sync method
work with the file system
see sync conflicts (“X” as menu symbol, message telling me files could not be synced)
this sounds close to two open client bugs: one where Resolve does nothing, and another where the client says files failed without naming them:
what exact desktop client version are you on? before resetting File Provider, copy anything with local-only changes somewhere outside it.
quitting and reopening the client may restore per-file conflict resolution temporarily. if it still happens, enable File Provider debug logging, reproduce it once, then turn logging off again: