Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No matching key in history error on refresh #5449

Open
HananINouman opened this issue Oct 17, 2024 · 1 comment
Open

No matching key in history error on refresh #5449

HananINouman opened this issue Oct 17, 2024 · 1 comment
Labels
type: bug Something isn't working

Comments

@HananINouman
Copy link

HananINouman commented Oct 17, 2024

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 after a refresh.
Our application is a static site generated (SSG) nextjs application with client-side components.

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
You can check/run this minimal code with an anchor (to refresh) https://github.com/HananINouman/reproduce-WC-bug

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

Screenshots
Screenshot 2024-10-17 at 5 32 57 PM

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.

@HananINouman HananINouman added the type: bug Something isn't working label Oct 17, 2024
Copy link

linear bot commented Oct 17, 2024

@HananINouman HananINouman changed the title No matching key in history No matching key in history error on refresh Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants
@HananINouman and others