Windows app's Sync is STILL renaming files that contain %number strings

Bug Reporting Mount & Sync
#1

Reference: Windows desktop app Sync replaces any literal "%20" in names with literal space (October 2022).

Recap: the Sync feature replaces all occurrences in source filenames of a percentage sign followed by a number with a unicode character in the destination filename. For example, “Very%20Important%21File%22Don’t%23Rename” becomes “Very Important!File1Don’t#Rename”.

I’ve also noticed that if we use one-way instead of two-way sync to avoid it also renaming the source files on the next interval, it will repeatedly copy such files as if they were new.

I’ve been using the app’s virtual drive with robocopy as a workaround, but that runs into the dreaded “1m timeout restriction” for small files - the drive transfer mechanism can copy any number of multi-megabyte files in a row without blinking (which, kudos) but give it any multi-kilobyte files via robocopy and the app may or may not fail to transfer them - and, unfortunately, if it does fail it will always fail the same way each time so I can’t just run the robocopy command again to catch only the ones it missed the first time.

#2

Hey @Shane thank you for the feedback. I have forwarded to our dev team to take a look.

#3

Hi Chris. I’ve just noticed it’s doing the same thing even when copy/pasting files into the virtual drive. I can’t recommend Icedrive as-is.

#4

Hi @Chris. Decided I’d take another look at Icedrive.

It has been fourteen months since I first reported this error.
It is easily reproduced.
It can result in data loss (e.g. two files “test test.txt” and “test%20test.txt” becomes just one file “test test.txt” that has the content of “test%20test.txt”).
It’s STILL not fixed (now on v2.75).

That’s not encouraging.

Did the dev team ever get back to you at all?