-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Show error notification when user tries to connect second custodian account in wallet generation
flow
#17271
Comments
wallet generation
flowwallet generation
flow
@brave/legacy_qa #17265 can be tested along side this issue |
Verification passed with
Verified scenarios from brave/brave-core#9669 (comment) Upgrade CaseConfirmed 1.28.105 is in the correct state (see brave/brave-core#9669 (comment) as a guide)
Logs:
Upgrade to 1.29.x.
Logs do not repeatedly show the 403 error, which is expected now per #17265. Logs:
Additionally, looking at brave://rewards-internals I can now see that I am no longer in the "PENDING" state, I have moved (as expected) to "NOT_CONNECTED".
Clean ProfileConfirmed that after attempting to link the second KYC'd Uphold account I do not see the 403 errors repeatedly in the logs:
Confirmed message is shown on panel.
Verification passed on
Verified scenarios from brave/brave-core#9669 (comment) Clean profileConfirmed that after attempting to link the second KYC'd Uphold account I do not see the 403 errors repeatedly in the logs:
Confirmed message is shown on panel.
Upgrade profileConfirmed 1.28.106 is in the correct state
Upgrade to 1.29.x.
Logs do not repeatedly show the 403 error, which is expected now per #17265. Logs:
Additionally, looking at brave://rewards-internals I can now see that I am no longer in the "PENDING" state, I have moved (as expected) to "NOT_CONNECTED".
Verified with
Verified scenarios from brave/brave-core#9669 (comment) Upgrade CaseConfirmed 1.28.106 is in the correct state (see brave/brave-core#9669 (comment) as a guide)
Logs:
Upgrade to 1.29.x.
Logs do not repeatedly show the 403 error, which is expected now per #17265. Logs:
Additionally, looking at brave://rewards-internals I can now see that I am no longer in the "PENDING" state, I have moved (as expected) to "NOT_CONNECTED".
Clean ProfileConfirmed that after attempting to link the second KYC'd Uphold account I do not see the 403 errors repeatedly in the logs:
Confirmed message is shown on panel.
|
Description
When a user tries to connect a second Uphold/custodian account in the
wallet generation flow
, no error modal is shown.Solution
The relevant error modal should show for the "2 custodian accounts to 1 browser" error case.
The text was updated successfully, but these errors were encountered: