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
I don't really know yet how this is connected to the similar issue I opened yesterday, but today, while trying to send two transactions one after the other, I have experienced the following bug, once again, with available ATOMs.
It goes as follows:
I send a transaction and see that the transaction successfully completes, I go to Activity and see it there... but I don't see it updating in "Available ATOMs". There I have the same amount than before sending.
If I try to send again the same amount, I get the following error:
And if I play around and change the amount (no matter if the amount exceeds or not my real balance), I get this other one (it doesn't matter if I reopen the tab, refresh, reopen even in another browser):
If I check in out API playground and query for balances (where liquidStake/ Available ATOMs is coming from) I see the wrong/old amount:
But if I go and ask the node through a REST call, I get the real balance:
In order for it to finally display the correct balance, you need to go and restart the API and only then you can continue sending transactions.
To Reproduce
Try to make two send transactions one after the other, doesn't matter whether with Ledger or the Lunie Extension.
Solution
I think we should use the REST call for balances for now...
EDIT: OK, I just saw this is what we are already doing. Really weird that when you query for balance directly on the browser it does show the real amount and querying it from the API shows the old one... Maybe it is an issue with cache? I don't know 🤷♀️
Desktop (please complete the following information):
OS:
Browser:
Version:
Smartphone (please complete the following information):
Device:
OS:
Browser
Version
Additional context
The text was updated successfully, but these errors were encountered:
Bitcoinera
changed the title
Balances/ Available ATOMs once again. Another bug
Balances/ Available ATOMs once again. Cannot make 2 consecutive send transactions
Jan 4, 2020
I have also recorded a really long GIF about this error.
There is a bit where I really look very clumsy. But that is because I cannot see the tabs when I am recording GIFs. It is overlapped by the program's window.
faboweb
added
the
bug 🐛
issues related to unhandled errors in the code that need to be fixed
label
Jan 6, 2020
Bitcoinera
changed the title
Balances/ Available ATOMs once again. Cannot make 2 consecutive send transactions
Balances/ Available ATOMs not updating (in GQL query): Cannot make 2 consecutive sends, cannot add funds
Jan 7, 2020
Describe the bug
I don't really know yet how this is connected to the similar issue I opened yesterday, but today, while trying to send two transactions one after the other, I have experienced the following bug, once again, with available ATOMs.
It goes as follows:
I send a transaction and see that the transaction successfully completes, I go to Activity and see it there... but I don't see it updating in "Available ATOMs". There I have the same amount than before sending.
If I try to send again the same amount, I get the following error:
And if I play around and change the amount (no matter if the amount exceeds or not my real balance), I get this other one (it doesn't matter if I reopen the tab, refresh, reopen even in another browser):
If I check in out API playground and query for
balances
(whereliquidStake
/ Available ATOMs is coming from) I see the wrong/old amount:But if I go and ask the node through a REST call, I get the real balance:
In order for it to finally display the correct balance, you need to go and restart the API and only then you can continue sending transactions.
To Reproduce
Try to make two send transactions one after the other, doesn't matter whether with Ledger or the Lunie Extension.
Solution
I think we should use the REST call for
balances
for now...EDIT: OK, I just saw this is what we are already doing. Really weird that when you query for balance directly on the browser it does show the real amount and querying it from the API shows the old one... Maybe it is an issue with cache? I don't know 🤷♀️
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: