autoConnectLastWallet causes blank account modal

[clement4saunier]

Current Behavior

When using autoConnectLastWallet and switching wallets (Rabby/Metamask) or disconnecting, a user triggering connectWallet is prompted with a blank account center modal with 0 available wallets and message: 'XXX only supports MetaMask on this platform. Please use or install one of the supported wallets to continue'.

Triggering connectWallet again seems to reset and work as expected.

Expected Behavior

If previously connected wallet fails to auto connect, calling connectWallet should display every wallet defined in the onboard configuration.

Steps To Reproduce

1. Connect to a dApp configured with {connect: {autoConnectLastWallet: true}} using MetaMask or Rabby .
2. Replace onboard.js:last_connected_wallet in local storage with the other wallet (['MetaMask'] => ['Rabby'] or ['Rabby'] => ['MetaMask'].
3. Refresh the app and try to connect again.

What package is effected by this issue?

@web3-onboard/core

Is this a build or a runtime issue?

Runtime

Package Version

2.21.2

Node Version

v20.8.1

What browsers are you seeing the problem on?

Chrome, Safari

Relevant log output

No response

Anything else?

No response

Sanity Check

• If this is a build issue, I have included my build config. If this is a runtime issue, I have included reproduction steps and/or a Minimal, Reproducible Example.

[clement4saunier]

Hi any new on this ? This issue is confusing our users and seems like the only solution at our disposal is to use another provider entirely.

[Adamj1232]

Hi @clement4saunier thanks for raising this issue.
Which version of the web3-onboard/injected-wallets package are you using?
This may be due to a namespace collision on the provider where Rabby sets the isMetaMask flag as true, and if so this should be solved with the latest version of the injected-wallets package.