-
Notifications
You must be signed in to change notification settings - Fork 21
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
[Bug]: Unexpected Error (crash) as savings balance went to 0 #2297
Comments
I was unable to reproduce by letting a manual setup transfer confirm whilst watching the main wallet page. |
No idea why the balance would be wrong but the uncaught error is fixed with #2307 |
@pwltr We've seen the 0 balance a few times recently. @SeverinAlexB reported it happening after initial funding of new wallet via CJIT. Sev and I also witnessed something that could be related: the double-counting of savings balance after a transfer to spending. It feels to me like sometimes an address/output is either not being included in the balance or is being double-counted. Could this could be the result of simultaneous refreshes occurring, potential race condition? tracked by #2301 A manual refresh always corrects the balances. |
This issue is for the uncaught error crash, not zero balance. |
JS uncaught error was fixed here |
Tested on v1.0.6 (138) |
Describe the bug
A few minutes after initiating a Manual Setup transfer and boosting the transaction (CPFP), I was sitting on the home page waiting for the transaction to confirm and for my new spending balance to be available when my savings balance went from positive value 384k to 0 (see screenshot 1). I then tapped the savings balance and the 'Unexpected Error' page displayed (see screenshot 2) with the following report:
Reproduce
I'm unsure whether the manual setup and boost are relevant here but this is what I did
Screenshots / Recording
Screenshot 1
Screenshot 2
Operating system
Android 14
Bitkit version
b3f9f30
Log output
bitkit_ldk_logs_1728449292551.zip
The text was updated successfully, but these errors were encountered: