-
Notifications
You must be signed in to change notification settings - Fork 2.6k
[Desktop] user funds do not move to Uphold - follow up to 8428 #11298
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
I did not add |
Reproduced in |
uplift approved, waiting on new 1.13.x build to test |
Verification is passed on
Scenario 1: - PASSED
Scenario 2 - make sure that claim works with user funds and VG - PASSED
Scenario 3 - make sure that claim works with 0 balance - PASSED
Verification PASSED on
Created & Restored a wallet that had user funds (10 BAT in this case). Example:
Connected to a KYC'd account and ensured the following:
Created & Restored a wallet that had user funds (10 BAT in this case) and claimed a VG. Example:
Connected to a KYC'd account and ensured the following:
Verification passed on
Verified test plan from brave/brave-core#6000
Created & Restored a wallet that had user funds. Example:
Connected to a KYC'd account and ensured the following:
Created & Restored a wallet that had user funds and claimed a VG. Example:
Connected to a KYC'd account and ensured the following:
|
Additional scenario verified (not listed in test plan from PR) using
Confirmed claim process including getting KYC'd with Uphold.
|
Description
Follow up to #8428 and brave/brave-core#6000
If you have anon user funds and you connect a KYC'd uphold wallet, the user funds do not move to Uphold.
Steps to Reproduce
Test plan 4 from brave/brave-core#6000
Actual result:
Funds not moved. See below in the logs.
Expected result:
funds should move
Reproduces how often:
easily
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
cc @NejcZdovc @rebron @brave/legacy_qa
The text was updated successfully, but these errors were encountered: