WalletConnect v2 implementation does not support Optional Namespaces.

[jxom]

Describe the bug

MetaMask Mobile's WalletConnect v2 implementation does not support Optional Namespaces, thus breaking multichain DApps - users cannot switch network. This was previously working in MM Mobile + WalletConnect v1.

To Reproduce

1. Head to https://stackblitz.com/edit/vitejs-vite-bhhzgv
2. Connect
3. Try switch to Polygon
4. Error.

Expected behavior

You are able to switch chains.

[0xWhiteleaf]

I would like to add more precision.
This bug is due to the fact that Metamask ignores (or misshandle) the optionalChains parameter and therefore does not include these chains in the "allowed" chains of the session.

This is resulting in an error when we try to request chain switch:

error={ "message": "Chain 'eip155:137' not approved. Please use one of the following: eip155:1"}

How the connection is initiated client-side:

await EthereumProvider.init({
  projectId: process.env.TEST_PROJECT_ID,
  chains: [1], // chains added to required namespaces
  optionalChains: [77, 99, 137] // chains added to optional namespaces
  ...
})

[iketw]

Any updates on this?

[mohandesjiri]

Any update?
Too many dApps are already broken.

[mccabe-david]

I'm still having issues with this. It seems MetaMask is indifferent whether Optional Namespaces are sent in the Proposal Namespace. Further, when the Required Namespace "chains" array length is greater than 1, MetaMask won't even connect...

[mccabe-david]

Am I crazy or does setting chains undefined when the array length is not 1 make no sense? Like at least fall back on defaultChain if it exists. https://github.com/ElvisKrop/wagmi-dev-references/blob/020fc97e276e8d7fbbb918e840029593fa05e7e9/packages/connectors/src/walletConnect.ts#L304

[mthinh]

Im also facing this issue

[siosio34]

Any updates on this?

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 7 days. Thank you for your contributions.

[github-actions]

This issue was closed because there has been no follow activity in 7 days. If you feel this was closed in error please provide evidence on the current production app in a new issue or comment in the existing issue to a maintainer. Thank you for your contributions.

[microHoffman]

I believe this is closed by accident, the issue is still present @gauthierpetetin

[gauthierpetetin]

Thanks for flagging @microHoffman , I'll re-open it.