Walletconnect not working with Metamask mobile app about web3-onboard HOT 6 CLOSED

Confirming @0xhashmap - @chouandy @anuj0361 - Please add an explore URL to the onboard initialization's appMetaData object.
MetaMask added a requirement that a URL is passed with WalletConnect support and the appMetaData.explorer is passed into walletConnect v2 initialization.
I will get a PR together to add the requirement to the TS object and all docs.
Thank you for the feedback and community support!

from web3-onboard.

There is a PR open - #1822 to add a WC init prop to define this more clearly as well as enhanced validation and documentation around this.
To resolve this issue in the short term please pass in the dapp URL into web3OnboardInit.appMetaData.explorer or you can wait until the noted PR is in alpha to test with the walletconnect init prop dappUrl

from web3-onboard.

@anuj0361 we are aware of the issue and working closely with the walletconnect and MetaMask teams to try and resolve this issue. We will report here as progress is made.

from web3-onboard.

If there's an ETA please share. @Adamj1232

from web3-onboard.

Hi @Adamj1232,
I found that the possible problem is when appMetadata doesn't set explore or gettingStartedGuide url.
This url has an empty string.
The MetaMask mobile wallet should have verified that this url is not empty, resulting in an error.
After setting the explorer url everything works fine.

from web3-onboard.

I can confirm that the problem is not present after adding an explore url string in the appMetadata object.

from web3-onboard.