No matching key. keychain error

[Lbqds]

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

SDK Version (if relevant)

• @walletconnect/core: "2.11.0"
• @walletconnect/sign-client: "2.11.0"

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]

no one solving it?

[clemente-xyz]

Any solution? Having the same error

[AJShahAgha]

How to solve??