Metamask connects the wrong wallet about web3-onboard HOT 5 CLOSED

@lososeg this sounds like a case of wallets fighting for the window.ethereum space- you can read more and access troubleshooting tips here

from web3-onboard.

@lososeg this sounds like a case of wallets fighting for the window.ethereum space- you can read more and access troubleshooting tips here

No, I have only metamask installed (with several addresses) and I tested it in a private tab in which I allowed only metamask

from web3-onboard.

This is video of the error
https://github.com/blocknative/web3-onboard/assets/29502537/5c3e8715-9107-4fd3-b704-939e8d93e4b4

from web3-onboard.

@lososeg Thank you for the video- it's very helpful. We'll add to the team's backlog and keep you updated as we look into it.

from web3-onboard.

@lososeg this is expected behavior as you only gave access to that one account that reconnected on the initial MetaMask connect accounts screen and also why we display this message in the connect modal about selecting all accounts you wish to grant access to.

If access is granted to the other wallet it will connect to that account. This is also something we dont have control over as the MetaMask provider doesnt emit events on which account is currently active but returns all accounts that are available for the provider.
Closing for now as this is not a bug we have control of. Please feel free to continue the conversation

from web3-onboard.