Thanks Jacob.
Once I manually
xyz.txt on the Android..syncthing.xyz.txt.tmp to xyz.txt
the folder then shows as synced.
So, provided the folder shows as synced, this should mean no bad database entries, right?
(I’ve stopped syncing for the moment, so not creating any new bad entries)
As far as I understand the situation, what you do with files (temporary or not) should have no effect on the problem. The bad entries are in the index, which is sent in any case and produces an error on the receiving side. Did you actually connect two devices after doing what you described and it worked?
Do you keep your files in the app-specific folder (Android/data/com.nutomic.syncthingandroid) on the internal or external SD card? If not you could just export the config from syncthing android, safe it somewhere, remove syncthing, install an older playstore version e.g. from here and import the config again. Your files won’t be touched unless they are in the app specific folder.
I did so. Backed up /data/data/com.nutomic.syncthingandroid/files and /data/data/com.nutomic.syncthingandroid/shared_prefs. Switched over to 0.10.4 app and deleted the folder /data/data/com.nutomic.syncthingandroid/files/index-*.db before first run. WARNING: This could lead to data loss if devices were not fully in sync before doing this.
Yup, thanks for adding more detailed instructions. However to do it this way one needs a rooted device, my simplified explanation also works without it.
All my shared folders are elsewhere on my internal storage. I hadn’t noticed that I could export and import the config - that makes life much easier. Is that apkpure site trustworthy?
What’s this about possible data loss if not fully in sync? Given the problem with 0.10.5, I can’t seem to be fully in sync. Is it risky to downgrade?
All my shared folders are elsewhere on my internal storage. I hadn’t noticed that I could export and import the config - that makes life much easier. Is that apkpure site trustworthy?
It doesn’t really matter if the site is trustworthy as the google play releases are cryptographically signed, which means you can’t install a modified/malicious version over a genuine one installed from the play store. BUT THIS ONLY WORKS AS LONG AS THE GENUINE VERSION IS STILL INSTALLED. So to make sure you can try to install the manually downloaded apk after exporting the config. If it works, it’s not been tampered with. If there is an error like the one you get when you troy to install the F-Droid version, then you should really search for another source (btw: the f-droid version is perfectly fine, it just causes the same error message as it’s slightly different from the play store version).
What’s this about possible data loss if not fully in sync? Given the problem with 0.10.5, I can’t seem to be fully in sync. Is it risky to downgrade?
If you didn’t add any files on either device after upgrading to 0.10.5 you should be fine. Otherwise you could just sort for the ones with the latest changes/creation date and manually copy them or make a backup in case they get deleted on resync, so you can restore it in case it gets deleted. Then the worst case is that a file you deleted reappears and you have to delete it again.
Did you actually connect two devices after doing what you described and it worked?
yes, exactly.
I don’t normally leave syncthing running on Android - I run it when I want to sync, then exit.
So:
After changing a file (say) xyx.txt on a laptop
I run syncthing on the Android, but get an error on the android that the directory is “Out of Sync” and the directory contains both the old xyz.txt and .syncthing.xyz.txt.tmp
I exit syncthing on the Android
I delete the original xyz.txt on the Android.
I rename the new .syncthing.xyz.txt.tmp to xyz.txt on the Android
I run again on the Android, and the folder now shows as ‘synced’. Being a careful chap, I now exit Syncthing on the Android.
So my assumption is that the database is now ok. What do you think?
Well, if it is working, then good - it still sounds like either another problem or wodoo to me 
Anyway 0.15.16 is out that contains a fix for the absolute path problem that shows in your log.
woodoo: I guarantee I only use woodoo to clean my socks, never on my devices
another problem: yes, I wondered this. But honestly I just can’t understand the bug description, or how it relates to my log, well enough to comment.
In any case, my Androids are still on 0.10.15. When G play updates they will update. When it does I will try to sync, and we will see if the problem is still there.
I can see why the connection isn’t straight forward, the symptoms are manifold. To be perfectly honest, I didn’t try to wrap my head around all those symptoms, because when I saw the leading slashes in
tcp-client closed: protocol error: index update: “/.thumbnails”: filename is invalid
tcp-server closed: protocol error: index update: “/1wiki-info”: filename is invalid
it was already clear that you are affected by the major problem Jakob linked to and unless that’s solved, I default to assuming any other problem is caused by that as well. So lets wait for 0.10.16.
And just to be sure because I my comments are possibly a bit snippish: Your reports are great and very much appreciated. Their quality (mainly that they include the relevant logs) made it possible to identify the problem immediately - so thanks for that.
OK, the problem seems not related to Android versions. It occurs in Android 6.0.1 and 8.1.0. It seems to start with the recently updated Android App 10.15 (syncthing .14.45). Installing the f-droid version 10.14 (syncthing .14.43) resolves the issue of broken (spasmodic) connections and incomplete syncing.
Other devices on my network are running .14.46-rc1. Rolling back to .14.45 on these has no effect on the Android devices.
(Sigh, come back Felix, you’re needed!)
a bit snippish
do not worry - not at all.
Your mild direct comments are welcome, and I massively appreciate the effort that goes into syncthing, and often remind myself often how grateful I was to drop dropbox.
(see New User Experience: Comparing Syncthing Vs Dropbox)
mc
I won’t be updating anymore either. I left my play store apps to update last night, woke up today in horror to find out every folder on Syncthing failed to synchronize to Windows PC. Went to IRC channel for support but didn’t get any.
I went back to Syncthing v0.10.2 on Android, but that was not all. Syncthing created 500 mb of .syncthing files which I had to scan & delete individually by opening the 30+ folders I was syncing to PC with Syncthing. That & a few other folders simply failed to synchronize, spent time setting them up again. Wasted 2+ hours on this. 
I can’t believe a stable update pushed to the play store would break everything like this.
A new play store version 0.10.6 by Numotic is on its way today @downloaderfan you can update to that to clean up the mess.
Thanks @Nutomic for the new Google Play Store release, which seems to fix the problem. Do we still need to reset the db?
Also thanks for your development over the years.
No you don’t, the new release removes the faulty entries from the database.
Just updated on Android from G play store to
and synced, on 3 Androids.
All works, all now in sync. the sun shines and bluebirds sing - thanks.
Didn’t reset database.
I ran into this issue and reverted two Android devices to 10.4 (.14.43) on f-droid. While both are now working again, I had to -reset-database on three laptop and a Raspberry PI sharing a folder with the Android devices. Resetting deltas was not sufficient.
ST was showing a difference between local and global states. The difference was one file (70M) that had been deleted from one of the Android devices while it was running Android 10.5.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.