Just for the record, I am not using any Android device for syncing. I only use Linux and FreeBSD.
May I push this topic? I’m working with v0.11.10 server-side and v0.11.16 client-side and the problem persists.
I had this problem with a symlinked directory that had an absolute path on the source that didn’t exist on the destination (syncing foo, /home/user/foo/bar on Ubuntu, /Users/user/foo/bar on MacOS). The folder the symlink was pointing to existed inside the synced directory. Changing the symlink to be a relative path fixed the problem. This could be solved by rewriting the symlink targets by replacing the source base path with the destination base path.
Whatever you guys did in recent versiosn solved the issue for me. I have not had this problem for a month or so.
Sorry for the late reply.
You’re right. It seems that an update solved that issue.