-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
We should show a unique error when all credentials are spent #33031
Comments
cc: @mattmcalister @aguscruiz - help needed (including wording) For code change, we could potentially create a new state and then check here: |
Bumping down to a P4 after recent changes on Guardian VPN side have made this error happen a LOT less |
cc: @iambrianfung who recently ran into this Bumping from P4 => P3 |
Needs more work (UI mock ups, tests, etc)
Needs more work (UI mock ups, tests, etc)
This handles the condition where the all the credentials for a given day are redeemed and there are none left. This shouldn't happen - but can happen if there are network issues. Specifically, when the client doesn't receive response from server after redeeming the credential. Fixes brave/brave-browser#33031 Needs clean up - localization, tests, and updates for design.
This handles the condition where the all the credentials for a given day are redeemed and there are none left. This shouldn't happen - but can happen if there are network issues. Specifically, when the client doesn't receive response from server after redeeming the credential. Fixes brave/brave-browser#33031 Needs clean up - localization, tests, and updates for design.
This handles the condition where the all the credentials for a given day are redeemed and there are none left. This shouldn't happen - but can happen if there are network issues. Specifically, when the client doesn't receive response from server after redeeming the credential. Fixes brave/brave-browser#33031
This handles the condition where the all the credentials for a given day are redeemed and there are none left. This shouldn't happen - but can happen if there are network issues. Specifically, when the client doesn't receive response from server after redeeming the credential. Fixes brave/brave-browser#33031
This handles the condition where the all the credentials for a given day are redeemed and there are none left. This shouldn't happen - but can happen if there are network issues. Specifically, when the client doesn't receive response from server after redeeming the credential. Fixes brave/brave-browser#33031
Verification
Existing user (account.brave.com) - PASSED
New user (account.bravesoftware.com) - PASSED
|
Verification PASSED on
Verified the test plan from brave/brave-core#26272 Existing user (account.brave.com) - PASSED
New user (account.bravesoftware.com) - PASSED
|
@MadhaviSeelam: For both cases above (existing user and new user), for the step 19 the error message is not dismissed from the panel although the VPN status is |
@GeetaSarvadnya it was a natural wait as the testplan didn't mention these additional steps, I didn't know how long it takes for the error message to get dismissed. I was curious to see the timeframe it takes to dismiss the error message and as you can see, for existing user testcase, it took ~3 hours and for new user testcase, it took about ~48 hours. |
Test plan
See brave/brave-core#26272
Description
With the time limited v2 credentials system, folks are getting 2 credentials per day.
Even with the caching and safeguards we have in place, sometimes the person is running out of credentials. In the code, we are showing a session expired for that scenario, which looks like this:
If you examine the SKU state, you'll notice it looks like this (notice both spent):
We should show an error message which indicates that we're out of credentials.
Per Slack thread (for Brave employees - https://bravesoftware.slack.com/archives/C021S0FN3V1/p1730140219576869?thread_ts=1729197731.366099&cid=C021S0FN3V1), we should be showing an error:
Having trouble authenticating to the VPN server. Please contact support or try again later.
Help is needed to create a state inside the browser (ex: in the VPN panel, like session expired) to let folks know they've ran out of credentials. In an ideal world, this shouldn't happen - and if a user hits this situation, they will get a new set of credentials within 24 hours.
Figma for VPN (has most everything we've done so far):
https://www.figma.com/file/qtMYwoj3JWJO5xzwLt6j2f/Desktop-VPN?type=design&node-id=0-1&mode=design&t=eHDcKZkSPRxI60Se-0
The text was updated successfully, but these errors were encountered: