No matching key in history

[HananINouman]

Describe the bug
Obol dv-launchpad integrated rainbowkit recently, and we are trying to support walletconnect but this error is blocking the user on sign messages and on doing transactions. Our application is a static site generated (SSG) nextjs application with client-side components.
I have checked some other platforms that support the same stack with no issues but they are SSR nextjs apps.
We tried passing an authenticated RPC URL to the http transport, deleting localStorage/indexedDB, different versions, also different OS but same issue.

Versions
Using "@rainbow-me/rainbowkit": "^2.1.3", which is using
@walletconnect/[email protected]
We tried downgrading to different versions as well as locking @walletconnect/core to v2.10.0 but same issue.

To Reproduce
We get it most of the times on sign message, or doing a tx. Most of the times its blocking.

Expected behavior
indexedDB history key to match the key passed by the wallet.

Screenshots

Additional context
Testing was done using Apple M1 with macOS 14.6.1, Iphone 14 with iOS 17.7 and also android 14. We tested on safe wallet browser/mobile app and on metamask mobile app.

[linear]

CR-556 No matching key in history