Opening the app with an expired token should sign the user out #107
Assignees
Comments
ethanndickson
added a commit
that referenced
this issue
Mar 18, 2025
Closes #107. When the menu bar icon is clicked, and the user is signed in, and the VPN is disabled, the app will check if the token is expired. If it is, the user will be signed out. We could have checked this when the VPN is enabled, but the UX seemed worse, and the implementation would have been messy. We would have needed to sign the user out and show an error. Instead, we'll check for expiry in a scenario where the next user step would likely be an interaction that requires a session. This approach also future-proofs for when functionality becomes usable without the VPN.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If the user's supplied session token expires whilst logged in, they won't find out until they next attempt to turn the VPN on, at which point they need to then log out, and log back in.
We should instead check if the token is expired when the app starts, and sign the user out if it is.
The text was updated successfully, but these errors were encountered: