Account selection pops up even when no account exists for given blockchain

[tbone-bts]

dApp detects presence of Beet. User initiates action via dApp UI. dApp makes transaction request. But Beet wallet has no account associated with the blockchain in question.

In such cases, I think the account selection dropdown list should not be displayed. Instead, display an error and perhaps a link to add an account for that blockchain.

[sschiessl-bcp]

This case could trigger a popup with a button "add account".
'
Question is on the reponse: Should the requesting app be notified immediately (aka user declined message), or should we simply wait in the hopes that user adds an account?

[clockworkgr]

This case could trigger a popup with a button "add account".
'
Question is on the reponse: Should the requesting app be notified immediately (aka user declined message), or should we simply wait in the hopes that user adds an account?

would require an extremely large timeout...I say notify user and decline

[tbone-bts]

would require an extremely large timeout...I say notify user and decline

I think that is perfectly reasonable user experience.

[grctest]

The UX now is that an unlocked Beet wallet will create a prompt window, however if no blockchain related account is present the user will be alerted of this limitation & the only option is to deny the request.

The user should manually add the blockchain account before re-attempting the blockchain interaction via beet.

[grctest]

This issue can now be closed.