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
Currently in production, with a clear cache, when connecting a KeepKey with a Segwit balance only in Account 0, we do not detect the balance and require the user to manually add their BTC address.
References and additional details
I was able to get balances to load initially for a personal KeepKey with a higher BTC balance (Segwit Native) on initial load with a clear cache, but could not get the same results for my test KK that only has BTC in a segwit address.
Overview
Currently in production, with a clear cache, when connecting a KeepKey with a Segwit balance only in Account 0, we do not detect the balance and require the user to manually add their BTC address.
References and additional details
I was able to get balances to load initially for a personal KeepKey with a higher BTC balance (Segwit Native) on initial load with a clear cache, but could not get the same results for my test KK that only has BTC in a segwit address.
Jam of no BTC account detection even though there is a BTC balance: https://jam.dev/c/f034e8b5-3ea1-48e9-b8d0-0e8baf1eec78
A user in this situation could think they have lost their BTC, panic, and not know how to toggle their accounts in manage account to reveal them.
Acceptance Criteria
KeepKey accounts with balances are detected for all supported chains without the need to manually add them.
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response
The text was updated successfully, but these errors were encountered: