-
-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] - Crash on 'Bad Adress' #229
Comments
Update your app 3.4.6 https://github.com/zaneschepke/wgtunnel/releases/tag/3.4.6 |
Interestingly, even after 5 days, the app is not updated nor on fdroid, nor on Zach's depot: https://f-droid.org/fr/packages/com.zaneschepke.wireguardautotunnel/ I will update from the release page and update the results tomorrow. |
The app is updated on my personal fdroid repo here: https://github.com/zaneschepke/fdroid Fdroid's main repo build/deployment process takes up to 1 week to update an application. |
May be connected to #144 as the crash log is the same. |
Describe the bug
When enabling a VPN config with a bad address in the AllowedIPs list, the app crashes. Going through the logs, the cause is by the Android's VpnService raising a 'Bad address' error.
Stack trace:
Smartphone:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The app should catch that error and display it to the end user like what the official Wireguard does.
The text was updated successfully, but these errors were encountered: