[GH-ISSUE #70] Updated the app, cannot turn on the tunnel now #35

New issue

Open

opened 2026-10-13 21:05:25 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

2026-10-13 21:05:25 +00:00

Owner

Originally created by @ztx-lyghters on GitHub (Apr 12, 2026).
Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-android/issues/70

After updating the app via Play Market I have lost the ability to use it, as the tunnel refuses to turn on (without giving any sensible error).

Log file:
amneziawg-log.txt

Originally created by @ztx-lyghters on GitHub (Apr 12, 2026). Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-android/issues/70 After updating the app via Play Market I have lost the ability to use it, as the tunnel refuses to turn on (without giving any sensible error). Log file: [amneziawg-log.txt](https://github.com/user-attachments/files/26649506/amneziawg-log.txt)

bsakaguchi commented

2026-10-13 21:05:26 +00:00

Author

Owner

@romkazor commented on GitHub (Apr 16, 2026):

confirm. downgrade to 1.1.2 solve problem

@romkazor commented on GitHub (Apr 16, 2026): confirm. downgrade to 1.1.2 solve problem

bsakaguchi commented

2026-10-13 21:05:26 +00:00

Author

Owner

@ztx-lyghters commented on GitHub (Apr 17, 2026):

I had to remove junk packets options (i1-i5) from my connection config for the new version of the app to work. However, in the previous version it has worked just fine. Did something change in terms of what can be a valid value or something like that? The app can outright crash trying to enable interface like that, not only give a meaningless error message.
I think some precautions needs to be implemented to avoid app crash on (possibly) invalid values, as well as providing meaningful error messages that can give some insight into the nature of the problem.

@ztx-lyghters commented on GitHub (Apr 17, 2026): I had to remove junk packets options (i1-i5) from my connection config for the new version of the app to work. However, in the previous version it has worked just fine. Did something change in terms of what can be a valid value or something like that? The app can outright crash trying to enable interface like that, not only give a meaningless error message. I think some precautions needs to be implemented to avoid app crash on (possibly) invalid values, as well as providing meaningful error messages that can give some insight into the nature of the problem.

bsakaguchi referenced this issue

2026-10-13 21:05:41 +00:00

[PR #35] [CLOSED] Allow comments in wireguard configs #59