-
Notifications
You must be signed in to change notification settings - Fork 141
Fix VPN-6774: VPN cannot be turned OFF after the server unavailable modal is closed #10995
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but maybe we also need to consider alerting the user, especially in the 'server not responding case'
Upd: re-reviewing following Slack discussion.
…ivate in all the other cases
…and popup is closed
…nect to the server is failed
… reached in the Controller
…e are in StateConnectionError and enable toggle and server list button
…atConnectionError with server unavailable errors
As this may lead to traffic leaks in some scenarios, let's change the approach to fix this bug and add a new Three different scenario where identified that leads to a server unavailable condition:
2 and 3 are fixed, 1 may unlikely lead to traffic leaks and needs discussion |
…Error is reached in the Controller" as this can be done in qml and systray This reverts commit a3a9a03.
…tate is ConnectionError
… in timer being locked to zero when successully connecting after a server unavailable error
…connection error screen is showed and vpn toggle is clickable when popup is ignored
Description
Fix VPN-6774 by adding new
StateConnectionErrortoControllerto properly handle connection failures caused by server unavailability (e.g. switching to or connecting to an offline server).Server unavailable events now trigger a transition to this new state, which displays a dedicated error view and updates the systray with a red status indicator.
Also, fixes a bug where the connection timer remain stuck after a server-unavailable error on first connection with a subsequent successful connection.
Reference
Jira Issue
Checklist