wallet_switchEthereumChain not working from outside of metamask browser.

[frndxyz]

Description

"wallet_switchEthereumChain" , "wallet_addEthereumChain" call not switching/adding chains when calling by wallet connect from native mobile browsers.

but it works when using metamask browser interface.

[gantunesr]

Hi @frndxyz, we're working on supporting both RPC methods for WalletConnect, can you indicate the dapp where the issue is presented?

[mickeymond]

@gantunesr I am adding this here because I thought it is an observation I made that will be useful to resolve this issue but if it is not prompt me or remove it.

I am using Metamask Mobile v4.0.1(814) at the moment.

• Following a Deep Link for other RPC Networks that I manually added automatically switches the network if even the network specified in the Deep Link is not the one already selected.
• However, following Deep Links for RPC that a built-in to the Metamask by default like (Ethereum Mainnet & It Test Networks) does not do the automatic switching.

@frndxyz I was looking for an issue that covered my observation above and yours was the quite closest one. Please let me know if we are both heading in the same direction.

[tommasini]

Thanks for reporting! Could you check if this is still happening on the last version, please?

[mhm13dev]

wallet_switchEthereumChain is not working anymore when using with Wallet Connect V2

[mhm13dev]

Here is an example with Wallet Connect V2 which does not switch the chain

https://github.com/mhm13dev/wagmi-wallet-connect-v2/tree/switch-eth-chain-wc-v2-metamask

[mickeymond]

@mhm13dev If you are trying to communicate that MetaMask Mobile does not support Wallet Connect V2 then I agree with you. I just tried connecting to an old project (https://nsfw.app) that I worked on some time ago that I am sure still uses Wallet Connect V1 and it was all good. However, connecting to something like https://app.ens.domains does not even give any prompt for a connection to be established.

I am using MetaMask Mobile v6.6.0(1114)

[mhm13dev]

@mickeymond Metamask Android v7 now supports Wallet Connect V2. I used it today.

Now the problem is that if I want to switch the chain while using Wallet Connect V2, the Metamask doesn't prompt me for changing the chain.

That's what I am reporting here.

[mickeymond]

@mickeymond Metamask Android v7 now supports Wallet Connect V2. I used it today.

Now the problem is that if I want to switch the chain while using Wallet Connect V2, the Metamask doesn't prompt me for changing the chain.

That's what I am reporting here.

@mhm13dev That is very interesting because I have been checking updates on the Google Play store and I see no updates for V7. I am in Ghana. Should I expect some delays?

[mhm13dev]

@mickeymond I am not sure how google play store schedule the releases.

I just updated today but google play store says it was updated on June 7.

[Holybasil]

IOS 16.5 + MetaMask v7.0.1(1126) + ConnectWallet V2

the Metamask doesn't prompt a "switch network" modal and doesn't throw error as well.

try{
    provider.request({
        method: "wallet_switchEthereumChain",
        params: [
          {
            chainId: numberToHex(id),
          },
        ],
    })
}catch(error){
    console.log(error) // nothing output
}

In the meanwhile, "wallet_addEthereumChain" works well. I hope that "wallet_switchEthereumChain" performs as well as it does in the MetaMask extension.

[jurosh]

Same issue here - WalletConnect on MM Android connecting to dApp on Desktop Browser. Using Ethers & Ethereum WalletConnect provider.

There is just no error after wallet_switchEthereumChain - it just returns null as success promise resolve which is incorrect when there is no chain. We don't know that we should call to add new chain - add call itself works.

In this issues seems to be also reported similar bug https://github.com/MetaMask/metamask-mobile/issues/6655

Edit: Adding chain is also not reliable at all. Needed to restart android app to make it pop-up.

[calummoore]

experiencing the same thing, the first wallet_switchEthereumChain works, but any further switches to new chains are just ignored by metamask.

Switching back to an existing chain, does switch the network (via walletconnect wc), but then metamask ignores any signatures sent to the "switched" network.