Bug: wallet connect error on mobile

[TorstenStueber]

This is an error that occurs when using Vortex on Safari iOS with the Metamask app.

The error occurred directly when signing the approval transaction in the Metamask app. The error occurs in the wallet connect source code and I could this issue.

When this error occurs, the app never continues to proceed to the second signature.

Once this error happens, it happens again every single time at exactly the same moment.

Then error disappears when I reconnected the wallet. However, after starting/aborting/executing one flow, it will happen again on every subsequent flow. Until I reconnect again.

Once this error shows up for signing requests, the same error is also reported when pressing the disconnect button in order to reconnect the wallet.

[ebma]

I can reproduce this issue with Metamask as well as Zerion wallet on my phone (connected with walletconnect in the system browser and not using an in-app browser). The transaction is signed and executed on the network but the app shows

Error: No matching key. history: 1731002864136426
    at qt2.getRecord (index.es-XIXAFQQV.js?v=07c245af:47181:13)
    at qt2.get (index.es-XIXAFQQV.js?v=07c245af:47130:181)
    at Zt2.onRelayEventResponse (index.es-XIXAFQQV.js?v=07c245af:47880:81)
    at EventEmitter.<anonymous> (index.es-XIXAFQQV.js?v=07c245af:48278:205)

each time.

Seems like this happens a bit arbitrarily though. The best chance is to have a fresh walletconnect connection established. From my testing, I feel like a page refresh after having connected to an account increases the likelihood of the 'No matching key' error to appear.

I found a selection of relevant tickets

• [bug] Got "No matching key, history: 1662323434234" while disconnecting after refresh the page using wallet connect rainbow-me/rainbowkit#1382 this confirms that it happens after a page refresh
• [@walletconnect/ethereum-provider V2] Intermittent Error: No matching key. on eth_sendTransaction requests WalletConnect/walletconnect-monorepo#2326 (comment) this claims that it's an issue on the wallet side though it's unlikely that MetaMask and Zerion are facing the same issues
• https://github.com/orgs/WalletConnect/discussions/3291 this mentions a problem about deeplinks but doesn't seem relevant to our case

At least to me, it seems like the WalletConnect connection is quite brittle. We might be better off by re-initializing the wallet connection on each page refresh if we are on mobile. I think walletconnect sessions are stored with the WALLETCONNECT_DEEPLINK_CHOICE local storage item so on app start, we can check if it exists, remove it and make sure that the wallet appears disconnected.

Preliminary conclusion

It seems like the problem is that something is off with the WalletConnect session after reloading the page. Thus, the easiest fix is to re-establish the connection, every time the page is refreshed. Since this is mainly a problem with WalletConnect and the wallet connection in general (e.g. on Desktop) is unaffected, we should only re-initialize the wallet connection on mobile after a page refresh.

[TorstenStueber]

It's almost good that this error occurs so widely. This indicates that there is some good work around, such as the one you propose here. Let's see whether it works.