I’ve got a laptop, with a read-only share called ‘Books Read-Only’.
I have two android clients, 1 & 2, on the local network with the server, that are connected to ‘Books Read-Only’. I have told each android client in their Folder settings, that the folder is Receive Only.
Laptop is running SyncTrayzor 1.1.24, SyncThing 1.3.1 Androids are running SyncThing-Fork 220.127.116.11, SyncThing 1.3.2-preview 1 (From FDROID)
Androids had a previous copy of Books that was out of sync (a manual copy). ‘Books’ on the Androids is at /storage/emulated/0/Books, physically on an adopted, formatted-as-internal, 128GB A2 SanDisk SD card. I’ve had no file system problems, the cards were ordered from Amazon from SanDisk, so they aren’t fake.
Laptop is Windows 7 Pro. The Send-only ‘Books’ is at E:\Books, a partition on the SSD. Again, the SSD is new, has had zero file system errors.
I keep getting a BIG RED WARNING on the Androids, a red cloud with an up arrow: “REVERT LOCAL CHANGES!!!”, sometimes even though it shows in terms of # of files, the local android copy is the same as the global (laptop) copy. And Failed Items (xxx), some random amount [right now it’s 160 out of 16597 global items] on Android 1. Similar things happen on Android 2.
The other annoying thing, is really old invitations like “Default Folder” are not expiring. For instance, I get the “LAPTOP WOULD LIKE TO SHARE DEFAULT FOLDER” on the Androids, even though Laptop NO LONGER HAS that shared folder, at all. It’s been deleted - gone! It’s like the Android clients memorize every invitation, then re-iterate it at every opportunity, although that folder is no longer being offered (it’s been weeks now).
I’m starting to call SyncThing SyncBug among my friends.