syncthing-android: syncthing crashes since v1.26.0.0
Description of the issue
since the latest version syncthing crashes immediately after the app starts it
Reproduction Steps
sometimes the app works fine but otherwise syncthing just starts crashing. sorry I can’t provide more details 😦
if I use the button to force the app to not run syncthing and then force start it it’ll launch for ~2 second (status icon goes green, appnseems to connect to the syncthing spi) but then syncthing crashes after that 1 second 😦
Version Information
- App Version: 1.26.0.2
- Syncthing Version: Settings -> About -> syncthing version is blank
- Android Version: LineageOS 19.1
- Device manufacturer: OnePlus
- Device model: 9 Pro
Device platform info
[ro.product.ab_ota_partitions]: [abl,aop,bluetooth,boot,cpucp,devcfg,dsp,dtbo,engineering_cdt,featenabler,hyp,imagefv,keymaster,modem,multiimgoem,odm,oplus_sec,oplusstanvbk,product,qupfw,qweslicstore,shrm,splash,system,system_ext,tz,uefisecapp,vbmeta,vbmeta_system,vbmeta_vendor,vendor,vendor_boot,vendor_dlkm,xbl,xbl_config]
[ro.product.board]: [lahaina]
[ro.product.brand]: [OnePlus]
[ro.product.build.date]: [Mon Nov 6 04:02:33 UTC 2023]
[ro.product.build.date.utc]: [1699243353]
[ro.product.build.fingerprint]: [OnePlus/OnePlus9Pro_EEA/OnePlus9Pro:11/RKQ1.201105.002/2109102008:user/release-keys]
[ro.product.build.id]: [TQ3A.230901.001]
[ro.product.build.tags]: [release-keys]
[ro.product.build.type]: [userdebug]
[ro.product.build.version.incremental]: [cc8b4d8489]
[ro.product.build.version.release]: [13]
[ro.product.build.version.release_or_codename]: [13]
[ro.product.build.version.sdk]: [33]
[ro.product.cpu.abi]: [arm64-v8a]
[ro.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi]
[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.product.cpu.abilist64]: [arm64-v8a]
[ro.product.device]: [OnePlus9Pro]
[ro.product.first_api_level]: [30]
[ro.product.locale]: [en-US]
[ro.product.manufacturer]: [OnePlus]
[ro.product.model]: [A0001]
[ro.product.name]: [OnePlus9Pro]
[ro.product.odm.brand]: [OnePlus]
[ro.product.odm.device]: [OnePlus9Pro]
[ro.product.odm.manufacturer]: [OnePlus]
[ro.product.odm.model]: [A0001]
[ro.product.odm.name]: [OnePlus9Pro]
[ro.product.product.brand]: [OnePlus]
[ro.product.product.device]: [OnePlus9Pro]
[ro.product.product.manufacturer]: [OnePlus]
[ro.product.product.model]: [A0001]
[ro.product.product.name]: [OnePlus9Pro]
[ro.product.system.brand]: [OnePlus]
[ro.product.system.device]: [OnePlus9Pro]
[ro.product.system.manufacturer]: [OnePlus]
[ro.product.system.model]: [A0001]
[ro.product.system.name]: [OnePlus9Pro]
[ro.product.system_ext.brand]: [OnePlus]
[ro.product.system_ext.device]: [OnePlus9Pro]
[ro.product.system_ext.manufacturer]: [OnePlus]
[ro.product.system_ext.model]: [A0001]
[ro.product.system_ext.name]: [OnePlus9Pro]
[ro.product.vendor.brand]: [OnePlus]
[ro.product.vendor.device]: [OnePlus9Pro]
[ro.product.vendor.manufacturer]: [OnePlus]
[ro.product.vendor.model]: [A0001]
[ro.product.vendor.name]: [OnePlus9Pro]
[ro.product.vendor_dlkm.brand]: [OnePlus]
[ro.product.vendor_dlkm.device]: [OnePlus9Pro]
[ro.product.vendor_dlkm.manufacturer]: [OnePlus]
[ro.product.vendor_dlkm.model]: [LE2125]
[ro.product.vendor_dlkm.name]: [OnePlus9Pro]
[ro.product.vndk.version]: [33]
Android Log
About this issue
- Original URL
- State: closed
- Created 8 months ago
- Reactions: 5
- Comments: 36 (16 by maintainers)
Forum post: https://forum.syncthing.net/t/syncthing-1-26-crashing-on-android-in-syncthing-fork/21115
Also for reference I have now managed to capture the Logcat output of the crash that has slightly more detail: https://gist.github.com/blu3id/cddab7352ce6586e3ba999e346795206
Had the same issue, and the same workaround seems to have helped for me. Thanks for sharing it!
For the record:
Syncthing native excited with code 2, no errors or panics in the log. I expect that it did panic and print the panic output to a different file descriptor than where other logs land!? Tried the log to file option but didn’t manage to then find the logfile.
Yeah, upstream did a fix on that. Will need to wait for 1.27 to be released including the fix.
Great to see that there is an issue and some progress on this problem. I updated today and have the same issue with exit code 2 notification and no logs.
Can’t really say much, unfortunately:
When I force start it, it runs ok.It also crashes shortly after the manual start.@Soundtoxin Others in this thread sound like they’ve had success in exporting to the official/non-forked app.
And for whatever it’s worth I am experiencing this same bug.
Exporting, downgrading, then importing again worked for me.
As a final note, I’ve tried syncing the v1.24 instance to v1.26.1 (Linux) and v1.26.1 (Windows) and neither to crashes upon start. The Android version seems to be the only one affected.
Please capture the full native crash log and show it on the forum together with the pointer to the different versions.
Just as a sidenote: I think we could benefit from taking this issue to the Syncthing forum. My feeling says this is Syncthing(native) related and has nothing to do with the wrapper I’m maintaining here. Plus, the crash logs above are also native parts of Syncthing spitting them out.
@Catfriend1, I can update the Linux client, it didn’t seem to change anything. FreeBSD is more complicated, since stable only has 1.24 in their repos. For the latest version I think I’d need to build syncthing myself. Not a FreeBSD pro though, might be some other way.
Another observation, if I put the shared folder on
Pause, the v1.24 instance can remain running and ST-Fork will start just fine. I can even resume it afterwards and the sync will continue without issue.FWIW, I can confirm @libreinator’s observation about importance of instance start order. Some additional notes:
TCP WAN, so I’m guessing no relay is involved and thus it’s not a requirement.Edit: in case it’s relevant, both of my instances share different folders with ST-Fork, they’re not syncing a common resource.
@libreinator I have turned off all discovery methods on my phone (4 disabled check boxes). Then I configured my servers IP in the device entry (Android). The server sits on the same network, connected via Lan cable, my phone uses Wifi.
Update: I have now tried enabling the 4 discovery + connection methods, disabled static IP and it did not crash.
I have the same issue (similar logs) and I found it does not crash when the other devices are offline at the time syncthing-fork on android starts.
This is what I have tried so far:
I’m on Syncthing-Fork v1.26.0.2 with syncthing v1.26.0 on android (installed from f-droid) and syncthing v1.26.1 on arch linux.
Same here: the app crashes, the native one no, with the very same settings backup restored.
Edit: tried with v1.26.0.0 and latest v1.26.1.0, both version.
Here app logs https://pastebin.com/TmWSacRe
As another data point: I have done what @phillipberndt did and imported export from fork into the official app and started it while connected to the network that will reliable cause the fork to crash and it didn’t. So while I still suspect this is networking related upstream/official build doesn’t seem to be impacted so may well be build options related.
Also having the same issue. The workaround didn’t work. I also can’t get more useful logging beyond the native exit of code 2.
However this is likely related to networking somewhere as I can reliably cause Syncthing to crash when started if connected to a particular network with mobile data on. It seems to start fine on other networks and if either mobile or wifi is disabled. It remains stable if started and then networks change. I suspect that upstream is unlikely to see this bug because Synching remains running constantly rather than being started on multiple different networks.
I will try to get useful logging and post bug report upstream.