[Bug]: Switching to a new network on metamask mobile app does not prompt "Add Network" like it does on desktop

[dweng0]

Current Behavior

On Desktop

1. Go to blocknative react demo
2. Connect your meta mask wallet
3. Connect to a network from the list that you do not currently have added. You will be prompted to add the network

On Mobile (Metamask App)

1. Go to blocknative react demo
2. Connect your meta mask wallet
3. Connect to a network from the list that you do not currently have added. Nothing will happen.
   The following error shows in the console:
   

Expected Behavior

On Mobile Metamask App

1. Go to blocknative react demo
2. Connect your meta mask wallet
3. Connect to a network from the list that you do not currently have added.
4. Attempt to switch to that network.
5. If the unrecognised chain error occurs:
6. Attempt to Add that network instead

Steps To Reproduce

1. On metamask mobile browser
2. Go to block native react demo
3. try to change to a network that you have not added

What package is effected by this issue?

@web3-onboard/core

Is this a build or a runtime issue?

Runtime

Package Version

latest

Node Version

latest supported

What browsers are you seeing the problem on?

Chrome

Relevant log output

MetaMask - RPC Error: Unrecognized chain ID "..."

Anything else?

No response

Sanity Check

• If this is a build issue, I have included my build config. If this is a runtime issue, I have included reproduction steps and/or a Minimal, Reproducible Example.

[lnbc1QWFyb24]

Thanks we'll take a look in to this. I did some quick digging and this may have something to do with a different error code being returned on mobile for the switch chain method.

[dweng0]

As a temporary fix: If the wallet is metamask, we listen for the error code and then manually execute an "add chain" event (metamask native)

[Adamj1232]

@dweng0 thanks for the note on the temp fix! I will keep this issue open until we have a fix deployed to production for both community and eng team visibility

[Adamj1232]

The change for this is in PR here I will update this issue when an alpha package is available. Thanks again!

[Adamj1232]

Closing as issue is resolved with latest release. Thanks again!