Changing Wireguard server often fails

[freebrowser1]

When in the Wireguard selection screen : Proxy => SIMPLE, changing often goes wrong. One of the VPN servers in the list is checked. But when clicking another one, the app tells 'Stop other active process to enable Wireguard'. So then I uncheck the checked server and then I check another one to connect. Then it goes wrong often: it checks another VPN server and in many cases with a third one so two servers are shown as connected of which one fails. Unchecking both these results in checking it again automatically. Then I have to switch to ADVANCED to uncheck all and recheck just ONE. Very weird behavior.

[ignoramous]

Sounds like an annoying bug.

Are you on v055n, the latest version (check the footer of the About UI)?

If possible, do share a screen recording (no pressure).

[freebrowser1]

Here is a screen recording in both portrait and landscape mode, the two VPNs trying to open simultaneously mostly occurs in landscape, but in portrait it also behaves sometimes weirdly. I indeed have v0.55n on Android 14 (Nothing 2a).

https://github.com/user-attachments/assets/011538ce-2863-4c90-b0c6-0e385058b27d

[ignoramous]

Definitely weird. Will take a look on priority. Unsure if we'd need logs (if you know how to take logs via adb logcat) but @hussainmohd-a will let you know, if so. Many thanks for sharing the screengrab.

[hussainmohd-a]

There were some UI-related issues where multiple WireGuard entries appeared to be enabled simultaneously. This was caused by view recycling in the list, especially when multiple WireGuard configurations were present and the list required scrolling. The view IDs were being reassigned incorrectly, which led to the status of one WireGuard configuration being reflected on another.

This issue has been addressed and resolved through a series of commits in version v055o

[hussainmohd-a]

The fix will be part of the v055o release, which should be available in a day or two. Feel free to reopen the issue if the problem persists after updating.

[freebrowser1]

But the v0.55o is not released yet.

[ignoramous]

Code is frozen, and we have a build candidate ready. We'll mostly likely ship v055o either today (Monday) or tomorrow.