-
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
When balance cannot be fetched from custodian or user is in Logged out
state, use unavailable text or "- -" for the Rewards balance
#20991
Comments
Logged out
state, use something like "N/A" for the Rewards balanceLogged out
state, use unavailable text or "N/A" for the Rewards balance
Logged out
state, use unavailable text or "N/A" for the Rewards balanceLogged out
state, use unavailable text or "N/A" for the Rewards balance
Even if user is in a logged out state and receives some vBAT (an edgier case), I still think it's more beneficial to show N/A. The user can either disconnect from their custodian completely to get rid of N/A and see their vBAT there, or they can connect again and then the vBAT will be instantly userdrained to their custodial account. |
Related questions:
|
This will help enforce correct vBAT vs. BAT balance states: #21588 |
See screenshots in the PR. |
Logged out
state, use unavailable text or "N/A" for the Rewards balanceLogged out
state, use unavailable text or "- -" for the Rewards balance
Verification PASSED on
Uphold_PASSED
Gemini_PASSED
bitFlyer_PASSED
|
Description
When a user is in a logged out state and can't query their balance from their custodian, their balance will usually show 0.0 BAT (since all vBAT has already been userdrained to the custodian).
Update: This will also happen when custodian has downtime and the balance cannot be fetched. So, might be more general than when user is in a logged out state.
Solution
Use "N/A" (or some other string), which may be less alarming to users than seeing a declaration of
0.0 BAT
.The text was updated successfully, but these errors were encountered: