Couln't download. Remove incompatible characters from the filename

Hey AlexSzatmary, sorry to hear about this.

I just wanted to mention that periods should not be used in file names as they could result in errors or they won't be synced at all. For more information, you can have a look here.

I hope this helps a tad. 

Hi Walter, I mean that those are ordinarily legal filenames. I recognize that Dropbox does not currently handle them but I think it should. I routinely use filenames like confection2-decay_F-vary_gamma_E-r_L0.1phi_E1.00gamma_E1.00e-01.pdf and that particular file even does sync properly on Dropbox.

Thanks for your feedback on this AlexSzatmary - let me know if you have anything else to add. 

I am a developer, and one of the programs that I use requires me to have filenames like ".pve-ignore.ifcfg-eth0" (the program required me to add a ".pve-ignore." prefix to the files that should be ignored by the program).

Dropbox normally uploads and downloads these files from my computer, however, they are still showing up in "Sync issues".

What is the problem here?

Hey Arkadiy K., thanks for joining the discussion here.

Those dots in the filenames must be the culprit here. You can have a look at this Help Center article for more information about naming your files in Dropbox. 

Hope this helps!

I've basically given up on this issue as if feels like dropbox support doesn't seem to really understand the issue here. I - among others who have raised this issue - are fully aware of what dropbox recommends to put and not put in file names. I really wish dropbox could stop leading us to that same help article. 

What I want to know why dropbox says there are "sync errors" when there are not. Maybe initially there is an issue - hence the sync error message - but in the end, dropbox DOES upload those **bleep** files. So why is dropbox sending "false" sync errors messages, when eventually there isn't such an issue? 

nomadism 

because there is a sync issue - it may not sync to other devices and/or stop syncing on those devices. There is a reason they are detected and its to stop data loss and corruption not just on your machine but any others connected to it including shares. 

Um, no. Your comment, Mark, indicates that this issue is not fully understood by many people here. 

The screen shot that we - people who are raising these issues - are very specific "sync errors" even though they are simply labelled as a broad "sync error." The error message says that dropbox could not download (or in my case, upload) the file(s), but in the end the files are uploaded / downloaded without errors. 

So the sync error isn't simply saying that there might be a problem, as your comments suggests. The error message specifies what the problem is, but in the end the stated "problem" doesn't occur and actually self-corrects. 

That's why I had given up even raising - Dropbox repeats the same answer without addressing what the real issue is. 

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)