Open baltpeter opened 1 year ago
On the device, the tunnel is in fact still enabled.
Running adb shell am broadcast -a com.wireguard.android.action.SET_TUNNEL_DOWN -n 'com.wireguard.android/.model.TunnelManager$IntentReceiver' -e tunnel appstraction
manually doesn't help.
Even starting the WireGuard app and running the command didn't help.
And neither did force-stopping the app.
After manually disabling the tunnel in the app and re-enabling it, I still cannot control it via intents.
Curiously, just rerunning the analysis script did work. I don't think ensureDevice()
should have changed anything, so maybe the solution was to re-enable the tunnel via an intent, even though it was already enabled?
Another bug that came up during the https://github.com/tweaselORG/meta/issues/16 run:
From then on, every other app unsurprisingly failed with: