I've finally got the demo to work but there is one thing that is definitely wrong - except I'm not sure if that may be a design flaw in WalletConnect itself that cannot be avoided on your side? Hopefully not.
Here's the thing:
The connecting workflow goes like this:
(on an Android mobile phone)
- I click on the Connect button
- under "Select your wallet" I click "WalletConnect"
- in WalletConnect's popup I click "Connect"
- in Android's activity selector I choose MetaMask (the app)
- this opens the MetaMask app which prompts me to connect. I confirm
- this goes back to Chrome, but not to the original tab where I had the demo open, but rather a new tab, with a blank page, with a shitty long url.
At this point a user would have the right to feel completely lost and conclude that nothing is working.
However, if I manually close the stupid blank new tab and go back to the original tab, the contents of the page get updated and the button says "Disconnect", which means I'm connected as expected.
Isn't it possible to avoid opening a useless blank new tab? Or to force it to close automatically when you get back to it?
I've finally got the demo to work but there is one thing that is definitely wrong - except I'm not sure if that may be a design flaw in WalletConnect itself that cannot be avoided on your side? Hopefully not.
Here's the thing:
The connecting workflow goes like this:
(on an Android mobile phone)
At this point a user would have the right to feel completely lost and conclude that nothing is working.
However, if I manually close the stupid blank new tab and go back to the original tab, the contents of the page get updated and the button says "Disconnect", which means I'm connected as expected.
Isn't it possible to avoid opening a useless blank new tab? Or to force it to close automatically when you get back to it?