-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Incorrect error dialog used when credentials fail #22972
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
Comments
@stephendonner cannot reproduce, could you recheck pls? |
Can still reproduce using
|
Verified
|
Brave | 1.46.68 Chromium: 107.0.5304.36 (Official Build) nightly (x86_64) |
---|---|
Revision | 2f9c7a5a1fe357d87e9bc07c65cca9136b3651c5-refs/branch-heads/5304@{#671} |
OS | macOS Version 13.0 (Build 22A379) |
Followed my original steps to reproduce from #22972 (comment).
Confirmed the correct payment-error dialog is triggered in this specific case, with the correct wording.
10/18/2022 |
11/1/2022 |
Edit payment method dialog |
---|---|---|
![]() |
![]() |
![]() |
@stephendonner @MadhaviSeelam I have followed the STR from the description. When I advance the system date to 1st of next month (1st Dec 2022) I am not getting
|
Same. Using
I follow the same steps, and after advancing to the 1st of next month (from today's correct issue date of 11-23-2022), and relaunching Brave, |
Verification PASSED on
Thread for the tokens expiry discussion https://bravesoftware.slack.com/archives/C021S0FN3V1/p1669314173558939?thread_ts=1669225513.288039&cid=C021S0FN3V1 Nov 30th
Dec 1st
|
Description
Incorrect error dialog used when credentials fail
Steps to Reproduce
Brave Premium login
>Purchasing VPN with a new account
from Implement Brave VPN on Desktop #15804, making sure to specify the current month and year for the credit card's expiration dateBrave VPN
accountDate & Time
inSystem Preferences
and advance the OS date to the1st of next month
Brave VPN
Actual result:
Expected result:
From Figma:
Reproduces how often:
100%
Brave version (brave://version info)
@aguscruiz @bsclifton @simonhong @brave/qa-team
The text was updated successfully, but these errors were encountered: