Replies: 5 comments 1 reply
-
When checking Uniswaps website, I can see that they are re-instantiating the WC2 connector each time the chain was changed. This seems to be the way forward I guess, so I am closing here. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thank you! Cool info |
Beta Was this translation helpful? Give feedback.
0 replies
-
I have the same question and I'm still can't fix it |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Our Dapp currently supports two chains: Polygon and Celo, which respectively have the following mainnet chain ids:
[137, 42220]
. I am instantiating the WalletConnect connector as per the example:Which works just fine. But when trying to connect a (Gnosis)SafeWallet on Celo via WalletConnect, it would not work but instead I am receiving the following error message:
When I only provide one chain in the chains property (
[42220]
) it works fine.Has anyone come across this before? I would be surprised whether it is really necessary to re-instantiate the connector with a single chain property only two have a new connector to work with SafeWallet.
Beta Was this translation helpful? Give feedback.
All reactions