WalletConnect Error: No matching key. session topic doesn't exist

[serenae-fansubs]

I'm having trouble using Rainbowkit 2.0.0 to connect via WalletConnect from Safe App.

Using:

• Rainbowkit 2.0.0
• Wagmi 2.5.7
• Viem 2.7.8
• Next.js 14.0.4
• React 18.2.0

I see that Rainbowkit 2.0.0 is only days old. Is it perhaps currently not yet able to handle connecting via WalletConnect v2? Is anyone else running into this issue?

Unhandled Runtime Error
Error: No matching key. session topic doesn't exist: 464e813cba28bdd9f02ac6725a91e930778fcab70931a5e758aa13008255d188

Call Stack
ds.isValidSessionTopic
node_modules/@walletconnect/sign-client/dist/index.es.js (1:30438)
ds.isValidEmit
node_modules/@walletconnect/sign-client/dist/index.es.js (1:27204)
ds.onSessionEventRequest
node_modules/@walletconnect/sign-client/dist/index.es.js (1:21682)
ds.processRequest
node_modules/@walletconnect/sign-client/dist/index.es.js (1:15394)
ds.processRequestsQueue
node_modules/@walletconnect/sign-client/dist/index.es.js (1:14756)
ds.onRelayEventRequest
node_modules/@walletconnect/sign-client/dist/index.es.js (1:14319)
EventEmitter.eval
node_modules/@walletconnect/sign-client/dist/index.es.js (1:28885)

Sometimes when connecting, I also get this additional error:

Unhandled Runtime Error
Error: Please call connect() before request()

Call Stack
lr.request
node_modules/@walletconnect/universal-provider/dist/index.es.js (27:27672)
v.request
node_modules/@walletconnect/ethereum-provider/dist/index.es.js (1:2509)
v.switchEthereumChain
node_modules/@walletconnect/ethereum-provider/dist/index.es.js (1:4941)
v.setChainId
node_modules/@walletconnect/ethereum-provider/dist/index.es.js (1:5471)
EventEmitter.eval
node_modules/@walletconnect/ethereum-provider/dist/index.es.js (1:4078)
EventEmitter.emit
node_modules/events/events.js (153:0)
EventEmitter.eval
node_modules/@walletconnect/universal-provider/dist/index.es.js (27:32454)
EventEmitter.emit
node_modules/events/events.js (153:0)
ds.onSessionEventRequest
node_modules/@walletconnect/sign-client/dist/index.es.js (1:21710)
ds.processRequest
node_modules/@walletconnect/sign-client/dist/index.es.js (1:15394)
ds.processRequestsQueue
node_modules/@walletconnect/sign-client/dist/index.es.js (1:14756)
ds.onRelayEventRequest
node_modules/@walletconnect/sign-client/dist/index.es.js (1:14319)
EventEmitter.eval
node_modules/@walletconnect/sign-client/dist/index.es.js (1:28885)

I am initializing Rainbowkit in a pretty normal manner I think:

const config = getDefaultConfig({
  appName: '...',
  projectId: '...',
  ssr: true,
  chains: [mainnet, goerli, sepolia],
  transports: {
    [mainnet.id]: http(),
    [goerli.id]: http(),
    [sepolia.id]: http(),
  },
})

const queryClient = new QueryClient()

function App({ Component, pageProps }) {
  return (
    <WagmiProvider config={config}>
      <QueryClientProvider client={queryClient}>
        <RainbowKitProvider>
          <Component {...pageProps} />
        </RainbowKitProvider>
      </QueryClientProvider>
    </WagmiProvider>
  )
}

export default App

[magiziz]

@serenae-fansubs Are you using VPN when testing this ? Can you check your WalletConnect dashboard and make sure the allowlist domains are correctly set ?

[serenae-fansubs]

Looking a bit closer actually at https://lab.web3modal.com/library/wagmi/, the wallet appears to connect fine, but I can see the same error in the browser console:

The same goes for https://web3modal.com/

Why is Gnosis the right chain? This is a safe multisig wallet on Ethereum Mainnet, it's not on or using Gnosis Chain whatsoever. Ethereum Mainnet should still be the correct chain here, and my app will only support mainnet (and testnets).

Anyway, I can try creating a new Safe multisig on Gnosis Chain and see if that works! Might take me a bit because I guess I'll need to get some xDAI or whatever to do it... But in any case, Safe App definitely does support Ethereum Mainnet, as it's the app that Safe multisig owners use to interact with web3 dapps on Mainnet.

[serenae-fansubs]

But yeah... since I see that same error on WC's very own Web3Modal pages, then it sounds like it's not a RainbowKit issue per se. Maybe either a WC issue or a Safe App issue.

[glitch-txs]

Sorry I thought it was on Gnosis. I'll bring this up to the engineering team at WalletConnect next week and work on a solution. Feel free to open an issue in our monorepo for tracking purposes. Thanks!

[serenae-fansubs]

Okay, done!

WalletConnect/walletconnect-monorepo#4240