search

WalletConnect / walletconnect-monorepo

WalletConnect Monorepo
Apache License 2.0
1.38k stars 680 forks source link

`No matching key. keychain` error #4122

Open Lbqds opened 8 months ago

Lbqds commented 8 months ago

Describe the bug WalletConnect throws No matching key. keychain error when sending a request

SDK Version (if relevant)

To Reproduce The issue occurs with a relatively low probability, and I'm not sure if there are reliable steps to reproduce it.

Additional context When the user refreshes the dApp web page, we use the last session to automatically connect. It turns out that the session exists but the keychain does not exist, resulting in the No matching key. keychain error when sending the request. I suspect the problem is here(although I'm not entirely sure), where delete is a promise. Do we need to wait for the deletion session to complete before deleting the keychain?

Btw, since the keychain is very important for the session, does it make sense to check if both the session and keychain exist when initializing the SignClient?

1997roylee commented 6 months ago

no one solving it?

clemente-xyz commented 4 months ago

Any solution? Having the same error

AJShahAgha commented 3 months ago

How to solve??