The wallet cannot switch to the swap network

A failed network-switch request is a wallet/application coordination problem until evidence shows otherwise. Adding a network manually does not move tokens, and changing its display name does not change the chain it connects to.

Check support and permissions

Confirm that both the aggregator and wallet support the intended network and account type. Review any network permissions granted to the application. MetaMask documents network selection as part of connection permissions.

If the wallet says the chain is unknown or invalid, obtain its chain identifier and RPC details from official network documentation. MetaMask’s error guide treats missing or invalid chain identifiers as configuration issues. Do not copy values from an unsolicited support message.

Verify the result of a successful switch

Check the network in the wallet’s actual signing prompt, then recheck token contracts and available balances. Identical account addresses can hold different assets on different chains.

Cancel a pending prompt that still points to the old network and request a fresh quote. A stale application tab may continue presenting its earlier selection even after the wallet changes.

If a transaction was already signed before the switch error, inspect that original chain’s history before retrying. A network-switch failure does not cancel an earlier transaction. For persistent failures, report wallet version, intended chain identifier, connection method and exact message to official support without sharing secrets.