Closed klassare closed 3 months ago
Hi @klassare
retrieving the session through signClient.session.get(signClient.session.keys[lastIndex])
seems to help, but it doesn't completely fix the issue. From time to time I still get The "No matching key error" after a page refresh.
I tried also reproducing it through the WalletConnect's react-app but to no avail.
I'll try open a followup issue in the WalletConnect repo, in the meantime I'm actively looking into this issue.
Thanks for all the support.
Hi @klassare
The issue was caused by the following line in the constructor
https://github.com/airgap-it/beacon-sdk/blob/3026e3f03644ff75c31bd56eb939d87e0513aa11/packages/beacon-transport-walletconnect/src/communication-client/WalletConnectCommunicationClient.ts#L117 which caused signClient to be initialized two times
The "No matching key: history" fix has been addressed in v4.2.1
Describe the bug (current behavior) WC2 error in the console
To Reproduce Steps to reproduce the behavior:
Screenshots and/or logs![Skärmavbild 2024-03-26 kl 18 11 17](https://github.com/airgap-it/beacon-sdk/assets/31806893/2197766a-6c78-4f10-b87d-687734c78d54)