Open srett opened 2 months ago
Using the browser on the device and navigating to http://127.0.0.1:8384 shows syncthing is running just fine. I managed to log in, add devices and get it to sync files. Just the wrapper app kept claiming syncthing would not be running or is still starting up. So syncthing would indeed run just fine if the relay pool is not reachable.
Still not convinced this has anything to do with the problem, I copied the two root certificates to /sdcard/certs
and then added SSL_CERT_DIR=/sdcard/certs
to the environment via the Debug menu, as this tells go about additional locations for trusted certificates. Lo and behold, now the GUI works perfectly fine. Just as to why, I don't really understand.
Just in case this isn't a problem specific to this device, or Xiaomi's fork, and given that it didn't start working for completely unrelated reasons, I suggest that in case you want to actually support devices with Android <= 7, the Syncthing-Android (probably even upstream) app should just ship the two ISRG certs (X1 X2) and pass them via the environment if running on affected devices. But I'd be happy if someone could confirm this issue first.
Description of the issue
Installed Syncthing-Fork from GPlay (v1.27.9.0) on an old Xiaomi Phone with Android 6. The app starts up just fine, but fails to launch the native app.
Reproduction Steps
Install the app.
Version Information
Device platform info
Android Log
Similar story with logcat:
My guess now is that Syncthing shuts down when it can't connect to the relay service, but it's odd there is no further log output indicating that it will shutdown, making me doubt that theory. But in any case, I guessed the problem regarding the relay setup is that Android 6 doesn't have the recent ISRG root certificates; I added the two root certificates manually in the Android settings, but the error didn't change. I've no clue which certificate store the native go application within the Android wrapper would be using anyways...