Today I found a small typo in a file writing subroutine of ThunderSync 2, causing a fallback writing command to fail. No data is lost, but under certain conditions the synchronisation process exits prematurely.
These conditions are met when the user has chosen a non-Unicode export charset and wants to export data containing characters outside the charset.
Workaround: If you encounter this error (indicated by entries in the error console), switch to Unicode as export charset. Without the typo, ThunderSync would use Unicode automatically because a conversion into your preferred charset is not possible.
I’ll fix this in March.