You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a user tries to connect 2 custodial wallets (in this case Gemini) to the same payment ID, a notification should be shown on the panel per #16468. This is working in the Uphold case, but not Gemini.
Additionally, there is another problem where instead of seeing "Verify wallet" UI after attempting to connect the second account the "Disconnected" UI is shown. This will be logged separately.
Steps to Reproduce
Clean install, staging env. Enable Gemini in flags and restart.
Enable Rewards, link KYC'd Gemini wallet
Manually disconnect from Gemini (from wallet panel)
Confirm you are returned to pre-link state (UI, no balance, etc)
Link a second (different) KYC'd Gemini wallet
Logs show 403 error like below:
[ REQUEST ]
> URL: https://grant.rewards.bravesoftware.com/v3/wallet/gemini/9......b/claim
> Method: POST
> Content: {"linking_info":"eyJ0......
[98738:259:0819/115838.142307:VERBOSE6:logging_util.cc(136)]
[ RESPONSE - OnRequest ]
> Url: https://grant.rewards.bravesoftware.com/v3/wallet/gemini/9.......b/claim
> Result: Failure
> HTTP Code: 403
> Body: {"message":"error linking wallet: unable to link wallets: unable to match wallets: wallets do not match","code":403}
--> no error modal like the one requested in #16468 is shown
--> UI shows "Disconnected" and a balance (balance part will likely be fixed with #17474). "Disconnected" problem is logged as #17570 .
Actual result:
No notification indicating the problem like Uphold case has.
Expected result:
Notification should be shown indicating the problem (attempting to link a second Gemini account)
Reproduces how often:
easy
Brave version (brave://version info)
Brave 1.29.64 Chromium: 92.0.4515.159 (Official Build) beta (x86_64)
Revision 0185b8a19c88c5dfd3e6c0da6686d799e9bc3b52-refs/branch-heads/4515@{#2052}
OS macOS Version 11.5.1 (Build 20G80)
Version/Channel Information:
Can you reproduce this issue with the current release? n/a
Can you reproduce this issue with the beta channel? yes using 1.29.64.
Can you reproduce this issue with the nightly channel? nightly shows a different notification (pictured below), but it is still not the expected notification.
Other Additional Information:
Does the issue resolve itself when disabling Brave Shields?
Does the issue resolve itself when disabling Brave Rewards?
Is the issue reproducible on the latest version of Chrome?
Confirmed an error message is shown. Note, error text is generic and not descriptive of the problem. To be addressed with #17661. This does not reproduce for Uphold but does reproduce for bitFlyer (#17592):
Confirmed UI returns to pre-link state. It does not show "Disconnected" UI or a balance. "Verify wallet" is shown and no balance is displayed:
Description
If a user tries to connect 2 custodial wallets (in this case Gemini) to the same payment ID, a notification should be shown on the panel per #16468. This is working in the Uphold case, but not Gemini.
Additionally, there is another problem where instead of seeing "Verify wallet" UI after attempting to connect the second account the "Disconnected" UI is shown. This will be logged separately.
Steps to Reproduce
--> no error modal like the one requested in #16468 is shown
--> UI shows "Disconnected" and a balance (balance part will likely be fixed with #17474). "Disconnected" problem is logged as #17570 .
Actual result:
No notification indicating the problem like Uphold case has.
Expected result:
Notification should be shown indicating the problem (attempting to link a second Gemini account)
Reproduces how often:
easy
Brave version (brave://version info)
Brave 1.29.64 Chromium: 92.0.4515.159 (Official Build) beta (x86_64)
Revision 0185b8a19c88c5dfd3e6c0da6686d799e9bc3b52-refs/branch-heads/4515@{#2052}
OS macOS Version 11.5.1 (Build 20G80)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
cc @Miyayes @jumde
The text was updated successfully, but these errors were encountered: