vjgee
August 21, 2023, 7:43am
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.
vjgee
August 21, 2023, 8:35am
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.
Thank you for your quick response. we already doing this
chains[0].id is the only chain we supported.
vjgee
August 21, 2023, 9:32pm
5
I’ve reported the issue to our Dev team and will keep you updated on the progress for a fix.
Hi @vjgee , do you have any updates on the issue?. We have updated it to v7 but the error still exist.
vjgee
September 18, 2023, 9:05am
7
I’ve already flagged this to our team and waiting for a response from them.
1 Like
There’s an issue with walletconnect where only mainnet chains can be configured in the array that we send while setting up walletconnectV2Adapter
2 Likes
Thanks @maharshi for your response. I’ve also tried to set chain id to mainnet (1) but encounter the same error.