Connector fails to update chain after wallet chain switch and page refresh

[chybisov]

Check existing issues

• I checked there isn't already an issue for the bug I encountered.

Describe the bug

After establishing the connection and changing the chain in the wallet, the new chain doesn't get picked up after the page refresh, and the connector shows the initially connected chain.

Link to Minimal Reproducible Example

https://stackblitz.com/edit/vitejs-vite-wdirrm

Steps To Reproduce

1. Connect wallet to MetaMask connector (let's say the initial chain is Optimism - 10)
2. Switch chain inside MetaMask (e.g., switch to Polygon - 137) - this gets reflected correctly and shows a new chain
3. Refresh the page
4. After reconnection, the connector shows that the chainId is 10, while it should be 137

What Wagmi package(s) are you using?

wagmi, @wagmi/connectors

Wagmi Version

2.9.6

Viem Version

2.12.1

TypeScript Version

No response

Anything else?

This also affects all hooks returning current chain information like useAccount

[tmm]

Looks like a MetaMask Chrome extension issue. You can reproduce by running RPC requests in the browser console directly.

// start with extension on mainnet, then request accounts:
> await window.ethereum.request({ method: 'eth_requestAccounts' })
[...]
> await window.ethereum.request({ method: 'eth_chainId' })
'0x1'
> await window.ethereum.request({ method: 'wallet_switchEthereumChain', params: [{ chainId: '0x89' }] })
> await window.ethereum.request({ method: 'eth_chainId' })
'0x89'
// switch in mm extension ui, then run the following:
> await window.ethereum.request({ method: 'eth_chainId' })
'0x89' // should be 0x1

In the video, you can see that the listener is fired for when the chain switches back to Mainnet via the MetaMask extension UI, but when you call 'eth_chainId' again, the response is not updated.

000930_Google.Chrome_2024-06-06-16.48.44.mp4

Confirmed that this is not an issue with the MetaMask Firefox Add-on or Rainbow Chrome extension.

[tmm]

Linking up MetaMask/metamask-extension#25097

[tmm]

Small patch if anyone wants to apply while MM fixes the issue

71b49b1

[chybisov]

@tmm thank you for taking a look! I'll track MM issue 🙂

[github-actions]

This issue has been locked since it has been closed for more than 14 days.

If you found a concrete bug or regression related to it, please open a new bug report with a reproduction against the latest Wagmi version. If you have any questions or comments you can create a new discussion thread.