Fix the switchChain error encountered when using the "metaMask" connector

[xianchenxc]

fix #4223

[changeset-bot]

🦋 Changeset detected

Latest commit: 8a0e3b1

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
@wagmi/connectors	Patch
wagmi	Patch
@wagmi/vue	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
wagmi	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 16, 2024 5:18pm

[DNR500]

Should this also have the additional then block to fire the change event if its needed?

wagmi/packages/connectors/src/metaMask.ts

Lines 230 to 239 in ceadbbe

	// During `'wallet_switchEthereumChain'`, MetaMask makes a `'net_version'` RPC call to the target chain.
	// If this request fails, MetaMask does not emit the `'chainChanged'` event, but will still switch the chain.
	// To counter this behavior, we request and emit the current chain ID to confirm the chain switch either via
	// this callback or an externally emitted `'chainChanged'` event.
	// https://github.com/MetaMask/metamask-extension/issues/24247
	.then(async () => {
	const currentChainId = await this.getChainId()
	if (currentChainId === chainId)
	config.emitter.emit('change', { chainId })
	}),

[tmm]

Calling 'eth_chainId' directly solves it. It seems provider.getChainId does not always update this.state.chainId immediately.