Trying to add a testnet account via private active/memo key fails as it tries to use a production node URL instead of a testnet node URL.
To Reproduce
Try to add a BTS testnet account via private keys, check console logs for error.
Expected behavior
Uses a testnet node URL instead of a production node URL.
Additional context
testnet node url selection works elsewhere
If you don't log into a beet account with a bts wallet added to it, but rather immediately try to create a new wallet with a bts_test account it will use a testnet node correctly. If however you log into an account with a bts account added to it, then try to add a testnet account to that, or logout and create a new wallet with a bts_test account it'll try to use the production bts connection incorrectly.
Problem must lie in erasure of existing blockchain connections on blockchain switch & on logout.
Describe the bug
Trying to add a testnet account via private active/memo key fails as it tries to use a production node URL instead of a testnet node URL.
To Reproduce
Try to add a BTS testnet account via private keys, check console logs for error.
Expected behavior
Uses a testnet node URL instead of a production node URL.
Additional context
testnet node url selection works elsewhere
If you don't log into a beet account with a bts wallet added to it, but rather immediately try to create a new wallet with a bts_test account it will use a testnet node correctly. If however you log into an account with a bts account added to it, then try to add a testnet account to that, or logout and create a new wallet with a bts_test account it'll try to use the production bts connection incorrectly.
Problem must lie in erasure of existing blockchain connections on blockchain switch & on logout.