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
When you first open the wallet you'll be shown the dashboard for one chain, if you quickly switch to another chain it'll fail a couple times then get a working node.
To Reproduce
Launch in development mode to monitor terminal logs (as opposed to web dev console logs)
Have 2 accounts in your wallet, with different chains.
Launch the app, login, switch between the two chains, click refresh a few times till your balances show.
Expected behavior
When I change chain I want to immediately close the old chain's WSS connection.
When I change chain I want a new working connection, without having to manually click 'refresh balance' till it gets the right node connection.
Additional context
Additional node URLs in the config could potentially alleviate the issue, however this is somewhat of a known issue in bitsharesjs: bitshares/bitsharesjs-ws#21
The text was updated successfully, but these errors were encountered:
Describe the bug
When you first open the wallet you'll be shown the dashboard for one chain, if you quickly switch to another chain it'll fail a couple times then get a working node.
To Reproduce
Launch in development mode to monitor terminal logs (as opposed to web dev console logs)
Have 2 accounts in your wallet, with different chains.
Launch the app, login, switch between the two chains, click refresh a few times till your balances show.
Expected behavior
When I change chain I want to immediately close the old chain's WSS connection.
When I change chain I want a new working connection, without having to manually click 'refresh balance' till it gets the right node connection.
Additional context
Additional node URLs in the config could potentially alleviate the issue, however this is somewhat of a known issue in bitsharesjs: bitshares/bitsharesjs-ws#21
The text was updated successfully, but these errors were encountered: