Couln't download. Remove incompatible characters from the filename

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.

Yeah the annoying thing is that Dropbox can't tell if there are files that end in tilde because of the restrictions from File Provider, so it can't even tell if you delete them from your mac. I suggest ignoring the error, but the other option is to delete them from the web or from a non-mac computer.

dsspiegelI suspect Apple pressured Dropbox into using File Provider. Apple seems to like making sure things are done 'their way' and in my opinion 'their way' often has weird quirks.

If I had any advice for Dropbox at this point it would be to make these errors clearer, so that instead of a generic message of "remove incompatible characters like /\"<>?*:|" that doesn't mention tilde, it would be more specific and say "cannot sync files that end in tilde on Mac - these files are still available on other platforms". 

Again, I have had success ignoring the error (since all my non-mac computers can still see the tilde files fine) except the Dropbox app on my Mac is now stuck "syncing". I'd like the option to thoroughly ignore these errors on Mac so that the app behaves properly otherwise.

NanoExplorer  Interesting.  This is consistent with what you're saying: https://news.ycombinator.com/item?id=34650987

However, as far as I can tell, this is to enable a feature I'm not using — showing remote files that have never been downloaded as though they're on the local file system.  It's unfortunate that Dropbox is giving me a degraded syncing experience on the files that I want to sync in order to enable me to use a feature that I'm not using anyway.

Also, not only is ~ not listed among the problematic characters, but . is listed as a problematic character.  And "starting with . and ending with .swp" is not listed as a problem.  So their error message is not as helpful or accurate as it could be.

I'm having the same issue for the last 2 weeks. Restarting Dropbox doesn't resolve it.

Same issue over here. Still searching for a solution.

Same here. Also, deleting the corresponding files doesn't remove the red notification!

Hi all,  thanks for your reports so far and your patience while we looked into this internally. 

We checked back with the engineering team (they're already aware of this) and here's what we found:  

A change was made recently which surfaces these issues in Dropbox's Sync issues UI, but this specific issue existed before that recent change.

When Dropbox on macOS uses File Provider, macOS specifies certain filenames types that they will ignore, including filenames ending in a '~'. This ignore list is built-into macOS. Because of this, Dropbox can't sync files that match one of these ignored filename patterns. 

If you have a file that matches this ignore list in your Dropbox on our servers (maybe you uploaded it from a different device, for instance), we cannot download that file onto a device running macOS. It is still safe on Dropbox servers while you can either ignore the warning or remove the file from your Dropbox through the website if you don't want to sync it to any of your devices.

Hi Walter, thanks for your reply.

I am neither using File Provider, nor do the filenames contain any incompatible characters.

However, I am able to download the problematic files.

I've tried with one, renamed it from '0 Paste here' to '0 Copy here'. No issues so far.

I've also not been using File Provider (never heard of it). In my case I deleted the offending files and I'm still getting the errors and the constant notification despite the fact that the files no longer exist.

Hello Dropbox, how it is possible to block filenames with . in the filename? And it's written in your FAQ! Nowadays practically all filenames are with dots. What's wrong with this filename - "libserial9bit.so"?  Looks like you fired all qualified staff and hired students.

I uploaded picture here.