I have an untrusted device, which syncs separately with two trusted devices. With all three devices actually in sync, the untrusted device is reporting syncing at 99%, and the encrypted files are listed as “failed items” under Remote Devices in the GUI.
Here is my set up:
Device A (trusted): Windows desktop - v1.15.1, Windows (64-bit Intel/AMD) Device B (trusted): Windows laptop - v1.15.1, Windows (64-bit Intel/AMD) Device C (untrusted): RasPi - v1.15.1, Linux (32-bit ARM)
I have folder 1 shared among all three devices. That has been working for a long time.
I added folder 2 and shared it between Device A and Device C, configuring the folder on Device C as untrusted and providing a password on Device A. That works fine. The encrypted information shows up on Device C, and when I run the command line decrypt facility (output to an unshared folder) I get back the original information. Both device A and C report “Up to Date” in the GUI all around.
I then added folder 2 on Device B, shared only with Device C. On Device B I used the same password that was used on Device A.
The data now correctly syncs to Device B and I see changes made on Device B reflected back to Device A, and changes made on Device A reflected back to Device B. Both Device A and B report “Up to Date” in the GUI for devices and folders.
But at this point Device C is reporting syncing at 99%, and the encrypted files are listed as “failed items” under Remote Devices in the GUI. If I add a new item in folder 2 on Device A or B, it syncs to the other and Device C lists an additional encrypted file as a failed item.
The syncing of folder 1 across all three devices still works correctly.
Posted under support, but I’m not asking for support - just offering this experience with the new untrusted feature in case it is helpful. Happy to provide further info.