I have a similar issue - the encrypted data show 'conflicts' on 2 separate encrypted devices (Debian) - which is strange, since it doesn't know what the original filenames are!
The un-encrypted sync'd device is 100% fine otherwise with the original device..eg Device A (Win10) sends unencrypted to Device B (Debian) without any conflicts, so this appears to be an encryption naming issue of some type.
All using Version: 2.7.2 (1375)
Windows 10 - Source Device
3 other Devices: Linux 5.10.52-v8+ #1441 SMP PREEMPT Tue Aug 3 18:14:03 BST 2021 aarch64 GNU/Linux, of which 2 are using the encrypted keys and causing having conflicts.
