[Bug]: 0 spending balance
Describe the bug
some UX issues not sure if its a bug but when I open a channel, I receive notification that Instant Payments are available - its says open connection but on the home screen it says pending balance. The app was ON during the entire time. Positive side is it took less than 5 min for Bitkit to open a channel. But then under spending balance I can see 0 - mixed messages (see screenshots).
I backed up wallet and try to wipe and restore. Initially app crashed without providing option to send a report. I then restored the wallet only to find out there was no channel opened (see screenshot), amount was taken and now missing after restore (wallet has not indicated it was even LN tx).
Reproduce
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Screenshots / Recording
bitkit_ldk_logs_1692108700214.zip
Operating system
iPhone 6S
Bitkit version
v63
Log output
No response
I encountered the same issue. Even though the transaction status had been confirmed of 11 times, my spending balance was 0 sats. After the 11th confirmation, the balance updated, and I am now able to perform Lightning transactions without any issues.
I think the zero spending balance issue might be just the app state not auto updating and being in sync with LDK. The restore bug is separate.
some UX issues not sure if its a bug but when I open a channel, I receive notification that Instant Payments are available - its says open connection but on the home screen it says pending balance. The app was ON during the entire time. Positive side is it took less than 5 min for Bitkit to open a channel. But then under spending balance I can see 0 - mixed messages (see screenshots).
The first part is a known issue and tracked here: https://github.com/synonymdev/bitkit/issues/1261
Since the channel wasn't actually open yet (it is under pending in the screenshot) we can't add the local channel balance to the overall spending balance since you cannot use it yet. So working as expected here.
Assigning to @Jasonvdb for the second part
Closing this, seems outdated.