[Archive] Wallet connect on metamask cannot connect if user are on the same chain as setup

Embedded Wallets (Web3Auth)
1

:classical_building: Archived Content from Web3Auth Community

This topic was originally posted by richard.lee1 on 8/21/2023.
This content has been migrated from our previous community forum to preserve valuable discussions.

For example:

  • In the code we setup the chain as polygon mumbai
  • User try to login through walletconnect with metamask, if they are on sepolia it will throw an error
  • If they setup to polygon mumbai then they can login
2

@richard.lee1 Thanks for reaching out.

Your issue has been forwarded to our team and we will get back with further updates once more information becomes available.

3

Are you using the latest version of WalletConnect V2? Are you adding the chainId as hexadecimal or decimal format inside the getWalletConnectV2Settings ? I’ll link the example here for your reference.

4

Thank you for your quick response. we already doing this
chains[0].id is the only chain we supported.

unnamed
unnamed512×132 23.5 KB

5

I’ve reported the issue to our Dev team and will keep you updated on the progress for a fix.

6

Hi @vjgee, do you have any updates on the issue?. We have updated it to v7 but the error still exist.

7

I’ve already flagged this to our team and waiting for a response from them.

8

There’s an issue with walletconnect where only mainnet chains can be configured in the array that we send while setting up walletconnectV2Adapter

9

Thanks @maharshi for your response. I’ve also tried to set chain id to mainnet (1) but encounter the same error.