Completely broken, blank page after connecting with metamask

[php4fan]

On an Android mobile phone with MetaMask installed:

When I try the live demo at http://example.walletconnect.org/ it works as expected

When, however, I build it and deploy it to my own server, it seems to suffer from a very similar issue as this vanilla-js version does:
WalletConnect/web3modal-vanilla-js-example#35

1. In Chrome, I go to where I've deployed the build: https:/opentarget.org/test/wc-example-b
2. I tap on Connect to WalletConnect
3. A modal shows up with two tabs: "Mobile" and "Qr Code". "Mobile" is selected by default, and there's a "Connect" button
4. I tap on Connect
5. Another modal, this one belonging to the Android OS, asks me to choose which app to use: Chrome or MetaMask. I choose MetaMask

(steps 6-8 may happen or not, randomly)

6. This gives focus to the MetaMask app, but MetaMask does nothing. It does not ask me to connect, or anything else. It just shows the main screen where I see my balance
7. I manually come back to Chrome, where I had the above url open. Now I find a blank page in a new tab, so I close it and go back to the tab where I have the above url open
8. I tap on the "Connect Wallet" button again. I repeat steps 3-5

(continue either from step 8 or from step 5)

10. MetaMask pops up, and this time does ask me to accept connecting to your webpage. I say yes
11. It automatically closes Metamask and redirects me back to chrome
12. again like in step 7, I find myself in a new blank tab, so I close it and go back to the main tab with the demo
13. The page is completely blank . I have no idea if there are error messages in the console, but there's definitely none in the page.

If I reload and retry, after step 2 I get a blank page and nothing happens (does not open MetaMask), and no matter how many times I retry, that's all I get.

If I clear the cookies, then I can repeat the process from the beginning, but I still get the same result as above (randomly with or without steps 6-8).

[kaitebell55]

Send your phase number ***@***.***> wrote:

…

On an Android mobile phone with MetaMask installed: When I try the live demo at http://example.walletconnect.org/ it works as expected When, however, I build it and deploy it to my own server, it seems to suffer from a very similar issue as this vanilla-js version does: WalletConnect/web3modal-vanilla-js-example#35 <WalletConnect/web3modal-vanilla-js-example#35> 1. In Chrome, I go to where I've deployed the build: https:/ opentarget.org/test/wc-example-b 2. I tap on *Connect to WalletConnect* 3. A modal shows up with two tabs: "Mobile" and "Qr Code". "Mobile" is selected by default, and there's a "Connect" button 4. I tap on Connect 5. Another modal, this one belonging to the Android OS, asks me to choose which app to use: Chrome or MetaMask. I choose MetaMask (steps 6-8 may happen or not, randomly) 1. This gives focus to the MetaMask app, but MetaMask does nothing. It does not ask me to connect, or anything else. It just shows the main screen where I see my balance 2. I manually come back to Chrome, where I had the above url open. Now I find a blank page in a new tab, so I close it and go back to the tab where I have the above url open 3. I tap on the "Connect Wallet" button again. I repeat steps 3-5 (continue either from step 8 or from step 5) 1. MetaMask pops up, and this time does ask me to accept connecting to your webpage. I say yes 2. It automatically closes Metamask and redirects me back to chrome 3. again like in step 7, I find myself in a new blank tab, so I close it and go back to the main tab with the demo 4. *The page is completely blank* . I have no idea if there are error messages in the console, but there's definitely none in the page. *If I reload and retry*, after step 2 I get a blank page and nothing happens (does not open MetaMask), and no matter how many times I retry, that's all I get. If I clear the cookies, then I can repeat the process from the beginning, but I still get the same result as above (randomly with or without steps 6-8). — Reply to this email directly, view it on GitHub <#93>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AX3KSDXB625MU5BGXNCXWGDVQRA5PANCNFSM5ZT6VBYA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>