You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm attempting to connect shapeshift native wallet to etherscan, and experiencing a dead click on 'Connect' after pasting in the WalletConnect code. Error in the console says
Uncaught (in promise) Error: Pairing already exists: 27e3526a00cd5d9ae82e6a8596f1b8b26d32265e3de3cfb39c2c5a283ee4b9e5
One way to reproduce (when I first experienced i was just trying to connect to etherscan for the first time in weeks):
Connect to a dapp via WalletConnectv2
from the same wallet in a different browser, attempt to connect to the same dapp
experience dead click when clicking 'Connect'
Acceptance Criteria
AC:
Users can connect to dapps via WCV2 that they've connected to in the past
(maybe we can automatically disconnect all active WC sessions like this wallet does when this error is triggered, and then retry? or maybe we need to implement the ability to have multiple active sessions at once, see active sessions, and enable users to disconnect from any/all of their active sessions manually - more details in the minispec)
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response
The text was updated successfully, but these errors were encountered:
Overview
I'm attempting to connect shapeshift native wallet to etherscan, and experiencing a dead click on 'Connect' after pasting in the WalletConnect code. Error in the console says
Uncaught (in promise) Error: Pairing already exists: 27e3526a00cd5d9ae82e6a8596f1b8b26d32265e3de3cfb39c2c5a283ee4b9e5
References and additional details
wc docs: https://docs.walletconnect.com/2.0/web3wallet/wallet-usage
resolving known WC issues like this: https://support.perawallet.app/en/article/resolving-walletconnect-issues-1tolptm/
One way to reproduce (when I first experienced i was just trying to connect to etherscan for the first time in weeks):
Acceptance Criteria
AC:
(maybe we can automatically disconnect all active WC sessions like this wallet does when this error is triggered, and then retry? or maybe we need to implement the ability to have multiple active sessions at once, see active sessions, and enable users to disconnect from any/all of their active sessions manually - more details in the minispec)
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response
The text was updated successfully, but these errors were encountered: