Web GUI JSON Error with Non-English Paths in Config (Since v10.14.9+)

[ForestQ]

Hello!

I've encountered an issue with the Web GUI in recent Syncovery versions.

Paths containing non-English characters (e.g., Cyrillic) are saved in the configuration file using a non-Unicode encoding. This doesn’t affect normal operation when using the desktop application, but once the Web GUI is opened, it fails with the following error:

Profile list loading error: SyntaxError: Bad escaped character in JSON at position 96 (line 1 column 97)

The JSON conversion fails because of garbled characters (mojibake) in the profile paths.

The last version that handled these paths correctly was 10.14.9. All later versions, including the entire 11.x branch, crash on loading the Web GUI if such paths exist.

Would appreciate any suggestions or workarounds, or ideally a fix for Unicode path handling in future versions.

Thanks in advance!

[tobias]

Many thanks, I will work on it!

[tobias]

Hello,

OK so I've tried the complete Russian alphabet in both profile names and paths and cannot confirm the problem at all. Everything just works.

To be able to use Russian letters in profile names, you need to set the "Language for non-Unicode programs" in Windows to Russian. I assume you have that, otherwise you wouldn't be able to create jobs with Russian letters in the profile name.

Paths however can always contain all Unicode characters regardless of the Windows language.

A JSON encoding error can have many other reasons and could be related to some other setting in your profile which I can't guess.

Please send the exported profile that causes it to support@syncovery.com. If you can grab the invalid JSON too that would help also.

Thanks!