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
Bug Description
User is navigated from gooddapp to the download page for metamask whenever doing any tx while using wallet-connectv2
Steps to Reproduce (taken from thread on onboard issue)
use onboard connect modal (latest)
click on wallet-connect (v2)
click on one of the shown deeplink-wallets
DONT CONNECT
click back, and use QR scanning or copy URI to connect an alternative wallet
nce connected, attempt to do a transaction
redirect happens on dapp
*. can verify here that the page that opens is the link set in storage on walletconnect_deeplink_choice
Expected Behavior
This should not happen
- remove all wallets from desktop list which don't have a desktop app
Additional context
As described in below 3rd party threads, the issue lies with the local storage item walletconnect_deeplink_choice
this never gets cleared properly and can be mismatched with an actual wallet being connected causing an incorrect redirect to a deeplink uri
The text was updated successfully, but these errors were encountered:
There are a couple of reasons why this could have been missed.
the most logical/easy one is that with my own testing of wallet-connect, I clear the cache pretty consistently so this particular issue does not come into existence.
Bug Description
User is navigated from gooddapp to the download page for metamask whenever doing any tx while using wallet-connectv2
Steps to Reproduce (taken from thread on onboard issue)
*. can verify here that the page that opens is the link set in storage on walletconnect_deeplink_choice
Expected Behavior
This should not happen
Additional context
As described in below 3rd party threads, the issue lies with the local storage item walletconnect_deeplink_choice
this never gets cleared properly and can be mismatched with an actual wallet being connected causing an incorrect redirect to a deeplink uri
The text was updated successfully, but these errors were encountered: