`switchChainAsync` resolves inconsistently with MetaMask chain switch state

[matteocelani]

Check existing issues

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

Describe the bug

There is an inconsistency in the behavior of switchChainAsync when used with MetaMask. The function resolves before the actual chain switch is completed, leading to a mismatch between the Promise resolution and the actual chain state.

Key observations:

1. Timing:

   • switchChainAsync resolves immediately after sending the request to MetaMask
   • The actual chain switch in MetaMask happens several seconds later
   • This creates a gap between Promise resolution and chain switch completion

2. State Management:

   • UI updates show the new chain immediately
   • Hook values (useChainId, useAccount) maintain previous chain values
   • Console logs demonstrate the state mismatch during the switch process

Link to Minimal Reproducible Example

https://stackblitz.com/edit/new-wagmi-hrpyucft?file=src%2FApp.tsx

Steps To Reproduce

import { useState, useEffect } from 'react';
import { useChainId, useSwitchChain, useAccount } from 'wagmi';
import { arbitrum, base } from 'wagmi/chains';

export default function App() {
  const chainId = useChainId();
  const { chain: accountChain } = useAccount();
  const { switchChainAsync } = useSwitchChain();
  const [isLoading, setIsLoading] = useState(false);

  // Monitor chain changes
  useEffect(() => {
    console.log('Chain ID from useChainId:', chainId);
    console.log('Chain ID from useAccount:', accountChain?.id);
  }, [chainId, accountChain]);

  const testAsyncBehavior = async (targetChainId: number) => {
    console.log('=== Test Async Behavior Start ===');
    console.log('T0 - Initial state:');
    console.log('- ChainId from useChainId:', chainId);
    console.log('- ChainId from useAccount:', accountChain?.id);

    const switchPromise = switchChainAsync({ chainId: targetChainId });
    console.log('T1 - Switch request sent to wallet');

    const result = await switchPromise;
    console.log('T3 - switchChainAsync resolved with:', result);

    console.log('T4 - State after await:');
    console.log('- ChainId from useChainId:', chainId);
    console.log('- ChainId from useAccount:', accountChain?.id);

    return result;
  };

  const handleSwitchChain = async () => {
    try {
      setIsLoading(true);
      if (!chainId) return;

      const targetChainId = chainId === base.id ? arbitrum.id : base.id;
      await testAsyncBehavior(targetChainId);
    } catch (error) {
      console.error('Chain switch error:', error);
    } finally {
      setTimeout(() => {
        if (isLoading) setIsLoading(false);
      }, 5000);
    }
  };

  return (
    <div>
      <button onClick={handleSwitchChain} disabled={isLoading}>
        {isLoading
          ? 'Switching...'
          : `Switch to ${chainId === base.id ? 'Arbitrum' : 'Base'}`}
      </button>
      <div>
        <p>Current Chain (useChainId): {chainId === base.id ? 'Base' : 'Arbitrum'}</p>
        <p>Current Chain (useAccount): {accountChain?.id === base.id ? 'Base' : 'Arbitrum'}</p>
      </div>
    </div>
  );
}

Console output showing the issue:

=== Test Async Behavior Start ===
T0 - Initial state:
- ChainId from useChainId: 8453
- ChainId from useAccount: 8453
T1 - Switch request sent to wallet
T3 - switchChainAsync resolved with: {id: 42161, name: 'Arbitrum One', ...}
T4 - State after await:
- ChainId from useChainId: 8453    // Still showing old chain
- ChainId from useAccount: 8453    // Still showing old chain

What Wagmi package(s) are you using?

wagmi

Wagmi Package(s) Version(s)

wagmi@2.14.15

Viem Version

2.24.1

TypeScript Version

5.7.3

Anything else?

Using:

• MetaMask as wallet
• Testing performed with Base (8453) and Arbitrum (42161) networks

The issue affects the reliability of chain-switching logic in dApps, as developers cannot depend on the Promise resolution to accurately reflect the actual chain state.

[tmm]

What connector are you using? MetaMask, Injected, EIP-6963, etc.

[matteocelani]

As specified in the description and code, we are using MetaMask as the connector.
The issue has been verified in two scenarios:

1. Direct MetaMask integration (as shown in the reproduction)
2. Using RainbowKit with MetaMask as connector

The behavior is consistent in both cases: switchChainAsync resolves before MetaMask completes the actual chain switch.

[Chris0150]

This is an ongoing critical bug, why has this issue been closed?

[tmm]

Nothing has changed with the metaMask connector code recently so this is likely an upstream wallet issue. Some questions:

• What browser are you using?
• What MetaMask version? Mobile or browser extension?

This is an ongoing critical bug, why has this issue been closed?

Not reproducible. (It's also not a security issue so not a critical bug as far as we are concerned.)

[matteocelani]

Hello @tmm

I see the issue was closed as "not reproducible," but the problem is easily observable using the provided example.

To clarify further:

• Connector used: MetaMask (desktop browser extension version 12.13.1)
• Browsers used: Mainly Arc (a Chromium-based browser), but the issue is identical on other Chromium-based browsers such as Chrome.

Please directly verify the problematic behavior using the reproducible example provided at this link:

https://stackblitz.com/edit/new-wagmi-hrpyucft?file=src%2FApp.tsx

When you open the browser console after running this example, the problematic behavior becomes evident. Here's exactly what happens during the chain switch:

Detailed console log example during the switch from Base (chainId 8453) to Arbitrum (chainId 42161):

=== Test Async Behavior Start ===
T0 - Initial state:
- ChainId from useChainId: 8453
- ChainId from useAccount: 8453
T1 - Switch request sent to wallet
T2 - State immediately after request:
- ChainId from useChainId: 8453
- ChainId from useAccount: 8453
Chain ID from useChainId: 42161
Chain ID from useAccount: 42161
T3 - switchChainAsync resolved with: { id: 42161, name: 'Arbitrum One', … }
T4 - State after await:
- ChainId from useChainId: 8453  // still showing the previous value
- ChainId from useAccount: 8453  // still showing the previous value
=== Test Async Behavior End ===
T5 - State after 1 second:
- ChainId from useChainId: 8453
- ChainId from useAccount: 8453
T6 - State after 3 seconds:
- ChainId from useChainId: 8453
- ChainId from useAccount: 8453

The promise (switchChainAsync) resolves immediately, suggesting the chain switch is complete, but the actual chain state in wagmi remains unchanged for several more seconds, causing a significant inconsistency in our application's state management.

I'm available for further clarification or additional testing if needed.

Thank you.

[soloviovqqq]

Any updates how you manage it? @matteocelani

[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.