I just updated from 1.18.0 to 1.19 on my Android 6.0.1 phone.
Syncthing asks me for location permission and to reset the database.
When I click Reset Database, Syncthing crashes.
So I can’t use Syncthing any more.
I tried to downgrade to the previous version (I have the 1.18.0 APK)
but installation fails. (“App not installed” message)
For the record, you can downgrade applications by uninstalling them using adb uninstall -k <package-name> first, and then reinstalling, which retains the app data. However, please keep in mind that there’s no guarantee that the newer data will be compatible with the older app version, so I’d suggest to be very cautious and make a backup before experimenting with anything like this.
Otherwise, you can simply try uninstalling and reinstalling the app from the GUI, but then you’ll end up starting from scratch. This won’t touch the actual synced files, which will remain on the device nevertheless.
Yeah, I can’t help with that, but as for the blocked port, you can try enabling wireless ADB in the Developer Options (as long as the phone manufacturer hasn’t disabled it, which they sometimes do) and connect do the device with that.
Edit: You could try to post the crash logs here as well though. This way more people will be able to have a look at them and possibly help find out what’s wrong.
at org.apache.commons.io.FileUtils.forceDelete (FileUtils.java:1341)
at org.apache.commons.io.FileUtils.cleanDirectory (FileUtils.java:324)
at org.apache.commons.io.FileUtils.deleteQuietly (FileUtils.java:1236)
at com.nutomic.syncthingandroid.activities.FirstStartActivity.upgradeToApiLevel30 (FirstStartActivity.java:213)
at com.nutomic.syncthingandroid.activities.FirstStartActivity.access$500 (FirstStartActivity.java:51)
at com.nutomic.syncthingandroid.activities.FirstStartActivity$ViewPagerAdapter$3.onClick (FirstStartActivity.java:333)
at android.view.View.performClick (View.java:6312)
at android.widget.TextView.performClick (TextView.java:11202)
at android.view.View$PerformClick.run (View.java:23985)
at android.os.Handler.handleCallback (Handler.java:751)
at android.os.Handler.dispatchMessage (Handler.java:95)
at android.os.Looper.loop (Looper.java:154)
at android.app.ActivityThread.main (ActivityThread.java:6816)
at java.lang.reflect.Method.invoke (Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1563)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1451)
Which seems like that library is using some method that doesn’t exist on such old androids?!
I guess I need to manually implement recursive directory deletion then - not that it’s hard, but it’s ridiculous.
I’m not an Android developer and have no idea where I could find a crash log. (accessible without root?) I bet 99% of Android have not even heard of adb.
The ‘normal’ Syncthing logfile in the accessible data directory is from before the update.
Not that old; it’s my current phone (hardly used). I mainly use Syncthing on my previous phone (HUAWEI Y330 with Android 4.2.2) that I use as dedicated MP3 player.
(Runs more than a week with >10h playing on a single charge. great)
However it was not possible to install from the Play store. I guess there are other compatibility criteria checked. Possible screen resolution. The missing exit entry in the clipped main menu is the only issue found so far.
Unfortunately 126.96.36.199 does not seam to fix the crash on my device.
Exact same behavior as 1.19.0.
(I suppose installing 188.8.131.52 from the store, multiple crashes and “Force Stop” in the App Settings should be enough for the new code to be used.)
Android\data\com.nutomic.syncthingandroid\files\Syncthing.log is still the log file from 1.18; I don’t know where I could find the crash log.
I guess so, but I don’t have any crash report in the console matching this issue and Android is borked enough that I’d suggest restarting the phone to make sure. If it doesn’t help, I’ll need logs/crash reports (I’ll have a look into the console later to day if any came in late).
That was progress
Yeah I’ll see if that works, but I am pretty confident an emulator won’t be able to repro this kind of error. If it doesn’t, ould you be able to install an apk if I provide one from our CI, so we can test again before I release again?