Syncthing does not activate automatically after always-on VPN drops and reconnect

[Knud3]

Setup:

• Samsung S22, Android 12, Syncthing-Android 1.20.2
• Run on Wi-Fi and Run on mobile data is enabled from Syncthing
• Always-on VPN and Block connections without VPN is enabled from Android settings
• I use WireGuard client (if that even matter) and can't verify does this occur with something else

Reproduce: Disable WireGuard connection > Syncthing goes disabled state > Enable WireGuard connection > Syncthing stays in disabled state

Expected: Disable WireGuard connection > Syncthing goes disabled state > Enable WireGuard connection > Syncthing activates again

Workaround: Sometimes opening app is enought to get it working again but sometimes there is notification Syncthing is disabled and tapping Change settings and returning to main screen fixes it. Nothing else is needed.

I get that this is not support forum, but is it possible to get Syncthing to sync every possible network without any checking for workaround?

[Catfriend1]

Hi, what does the SyncthingNative log say when that happens? I wonder if the binary somehow gets stuck or bound to a wrong interface? I also wonder why its a problem in the official app. We have it in both fork and official - but the fork has a configurable method of binding to mobile/wifi/etc interface. The official app does not bind to a specific interface. I've got no clue why the "stuck in starting" happens yet. Also, a logcat would be nice to further dig into this in case it turns out not to boil down to a stuck SyncthingNative instance.

[Knud3]

@Catfriend1 Nowadays I use your Syncthing-Fork and with Bind to active network and Force start ignore run conditions it works perfectly for me.