You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Couln't download. Remove incompatible characters from the filename
Recently all of my computer with Dropbox have started showing a sync error "Couln't download. Remove incompatible characters from the filename. e.g. emojis, /\"<>:|?*"
The problem filename isn'...
Hey Roy2010, no worries let me share Sam's response here as well.
Hi everyone,
Sharing an update on the topic: our team is working on adjusting this, and it's expected to roll out in our next Stable Build (V190).
You can check our releases here, and we'll keep you informed on the progress.
Thanks,
Sam
I appreciate your patience on this, thank you!
I'm getting sync errors, but not sure why.
Presumably it's because of the ~ character at the end. (This character is fairly common in the Unix world as they are created by apps like emacs as backup copies of the previous version of a file that's been changed.)
It's not 100% clear since ~ isn't listed in the character examples.
More importantly, how do I fix this? How can I exclude these files, e.g. with wildcard rules, from having Dropbox try to sync them?
I don't want to keep getting sync errors every day.
Dropbox v189.3.8308 (beta)
macOS 13.6.2 (Ventura, ARM)
I'm having this issue, too. Similarly to what other users have reported, the files are about ten years old and I have a huge number of them. As someone pointed out, the ~ is very common in file names on Linux systems. Renaming them is not an acceptable solution for a number of reasons. This is a bug that affects many paying users and it should be fixed!
I'm experiencing the issue on an Intel Mac with MacOS 13.5.2 and Dropbox version v189.4.8395
That is the root issue and yes I agree should be fixed. But it has been documented and so users know what to do. Thus is a feature not a bug.
But that is not the bug that we in this thread want to solve.
The issue is that if Dropbox reports them as any error. It suggests that you delete the files. I have done so but the errors are still being reported.
Where is it "documented"? Dropbox does not list the tilde in their list of problematic filename characters. And they've not acknowledged this, instead using passive voice ("a change was made") to deflect.
