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
The fixes on the above issue fixed the problem with double splits happening in the open.
Still sometimes for an unknown reason after a split the balance in a wallet can turn negative. Luckily it is not affecting any real sats and as soon as the user logs in the balance within seconds jumps back into the positive.
After discussing this with @dni I thought the invoice listeners where the root cause, but since after all the big fixes the issue still persists, I think it must be something else.
Also the strange thing about this is that while the balance is negative no further transactions from this wallet are possible and simply getting the wallet balance via api doesn’t turn it positive.
So I am wondering:
What is different when logging in to a account than when using API calls?
And is there an API workaround to fix the balances until the root cause is identified ?
The text was updated successfully, but these errors were encountered:
This is related to #14
The fixes on the above issue fixed the problem with double splits happening in the open.
Still sometimes for an unknown reason after a split the balance in a wallet can turn negative. Luckily it is not affecting any real sats and as soon as the user logs in the balance within seconds jumps back into the positive.
After discussing this with @dni I thought the invoice listeners where the root cause, but since after all the big fixes the issue still persists, I think it must be something else.
Also the strange thing about this is that while the balance is negative no further transactions from this wallet are possible and simply getting the wallet balance via api doesn’t turn it positive.
So I am wondering:
What is different when logging in to a account than when using API calls?
And is there an API workaround to fix the balances until the root cause is identified ?
The text was updated successfully, but these errors were encountered: