dapps does not perform any action after scanning

[rahulnftically]

while trying the dapps and the demo productions behave similarly that is after scanning doesnot perform any action .

[xzilja]

Could you please expand on what you've tried and which apps you used?

I just tried full workflow on https://react-wallet.walletconnect.com / https://react-app.walletconnect.com and everything seems to work as expected. I tried via wallet on my phone and scanned qr code.

[ghost]

I have the same issue. All of these dapp repos do nothing when I scan the QR code. The sites you linked also do nothing unfortunately.

[penny-chang]

I have the same issue trying to connect MetaMask with https://react-app.walletconnect.com/ and nothing happen after scanning the QR code.

[xzilja]

Just to clarify, examples are for v2 of the protocol, I believe metamask uses v1 and that could be the issue. Below is my attempt at connecting and everything works as expected (using both of the example apps above).

Are you seeing any concrete errors on your end that could help to debug this?

https://user-images.githubusercontent.com/3154053/163125924-95095b53-275e-4872-a622-1b4ff5acbfcf.mov

[penny-chang]

So if I want to integrate with v2 version of walletconnect, I should build my own wallet, or if I want my dapps to connect to MetaMask, I should go back to use v1, is this understanding correct? Thanks for the information!

[xzilja]

@penny-chang As a dapp you would need to support v1 and v2 as well as build small ux around that (perhaps a toggle to switch between versions that your users can choose depending on their wallet supporting v1 or v2).

You can use https://react-wallet.walletconnect.com to test against your v2 implementation and any other wallet on the market right now to test for v1.

I know this is frustrating, but we are in this transitioning phase right now where majority of wallets and dapps are on v1 and v2 is already in beta. Once v2 is out we will be promoting everyone to start building on top of it.

Supporting both of these shouldn't be too hard however as a lot of logic of how you react to events and send messages remains the same. We also aim at simplifying v2 more and more with future releases and completely re-vamping docs to make them easier to understand and add sections around your exact usecase.

[bartosz-grabski]

@IljaDaderko

I'm having the same issue while scanning the QR from TrustWallet, there is no reaction in the dapp.

I've tested it both locally, by building and starting local server and on https://react-wallet.walletconnect.com/

I see no error messages in console, the QR is displayed, scanning from TrustWallet's WalletConnect has no effect. Am I missing something with config, or is the transition phase not completed for TrustWallet ? IMHO it would be good to at least get some error message, even if it's not supported.

[xzilja]

@bartosz-grabski I've just pulled everything locally and am unable to replicate issue using our example wallet and dapp, so this leads me to think that it is coming from outside, I'd verify that

1. You are using wallet and dapp that supports wallet connect v2 (ideally latest beta, which at the moment is beta-26)
2. In case you are using WalletConnect v1, you should have no issues testing against most wallets and dapps that are available on the market as majority is using v1

[FatNerdPeng]

Just to clarify, examples are for v2 of the protocol, I believe metamask uses v1 and that could be the issue. Below is my attempt at connecting and everything works as expected (using both of the example apps above).

Are you seeing any concrete errors on your end that could help to debug this?

Your answer is helpful to me. I did construct the QR code with the v2, and then scan it with the dapp of v1. There will be no response. I generated the QR code with the writing method of v1, and everything goes well

[iandjx]

+1 to this issue. I have tried connecting my Metamask wallet by scanning the wallet connect v2 QR code using the Metamask mobile app QR code scanner. After scanning, nothing happens.