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

Error connecting to dapps via WCV2 if pairing already exists #5107

Closed
willyogo opened this issue Aug 18, 2023 · 2 comments
Closed

Error connecting to dapps via WCV2 if pairing already exists #5107

willyogo opened this issue Aug 18, 2023 · 2 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@willyogo
Copy link
Contributor

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

image

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):

  1. Connect to a dapp via WalletConnectv2
  2. from the same wallet in a different browser, attempt to connect to the same dapp
  3. experience dead click when clicking 'Connect'

Acceptance Criteria

AC:

  1. 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

@willyogo willyogo added the bug Something isn't working label Aug 18, 2023
@woodenfurniture woodenfurniture added this to the wc milestone Oct 9, 2023
@0xean 0xean self-assigned this Dec 6, 2023
@0xean
Copy link
Contributor

0xean commented Dec 6, 2023

@willyogo - can you double check this is still happening for me?

@willyogo
Copy link
Contributor Author

willyogo commented Dec 7, 2023

@0xean I can't reproduce this anymore, it appears to be fixed! 🎉
image

@willyogo willyogo closed this as completed Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
Development

No branches or pull requests

3 participants