Mismatched network configuration when using Albedo

[ElliotFriend]

What version are you using?

Appears to occur on master branch, as well as on the live Account Viewer site.

We stumbled upon this as we're working on a Stellar Quest bounty for the claiming of claimable balances in the account viewer: kalepail/stellar-quest-bounties#158

Also relevant is corresponding PR that's been started in this repo: #375

What did you do?

I added the ?testnet=true flag at the end of the account viewer URL, I see the red banner pop up with the warning that I'm using TESTNET in PRODUCTION.

Is there a more "proper" way to switch from public to testnet and vice versa?

What did you expect to see?

When the account is connected using Albedo, I would anticipate that any transactions generated using the account viewer would be using the testnet.

What did you see instead?

The Albedo authentication popup window displays that I'm using the public network. The transactions submitted using Albedo use mainnet as well. Transactions (naturally) fail using this setup.

When I enter the secret key directly into the account viewer, things appear to work normally. Transactions are submitted successfully to the testnet.

I hope that's enough info to get started. Please let me know if there's anything else you need. Thanks!!

[quietbits]

Thanks for opening this issue, @ElliotFriend ! You're doing everything correctly on the Account Viewer side (there is no other way to switch between networks). I don't see an option to define a network on the publicKey() method on Albedo. I've asked about it here.