bestsync.us

Greetings,

I've discovered that BestSync doesn't like how I've named certain of my files. I can't tell for certain, but it seems like BestSync is failing on certain file names that contain both single quotes and commas. I'm not quite sure about the exact pattern. However, I have created a BestSync task that fails on 15 of these files with unusual names. Also, the file names of all these files are quite long (but still legal within Windows).

While these files use unusual characters, these unusual characters are valid file name characters since at least Windows 2000.

I've attached 4 files with file comments. I believe the file comments are all self explanatory.

Please, can BestSync be modified to work with all these file names?

Regards,

Jeff

We have confirmed that this is a bug when encrypt a file with long name. This bug has been fixed in version 7.3.11.
Please uninstall the current version, then install the new version.
But I recommend you not to use so long files, because though the local file system can support a very long file path up to 32768 characters, but the FTP server may not support so long file names.