Let's say you have two wallet applications installed on your phone, both supporting WalletConnect. For example, MetaMask and U-Wallet.
Once you have connected to MetaMask, and even after you disconnect, there is no way to connect to U-Wallet.
- Open the demo in Chrome on Android.
- Click on "Connect"
- Select "WalletConnect"
- in WalletConnect's dialog choose the "mobile" tab and click on Connect
- When prompted by the OS, choose MetaMask
- in MetaMask, accept the connection
- Now back to the demo, click Disconnect
- restart from step 1.
Expected: should repeat all the steps as above, allowing me to choose U-Wallet at step 4 instead of MetaMask.
Observed: jumps from step 2 to 6. That is, when you choose WalletConnect in the KV dialog, it is already connected to MetaMask, and doesn't let you connect to anything else instead.
This does NOT happen with https://example.walletconnect.org/ so this must not be a bug in WalletConnect itself.
Let's say you have two wallet applications installed on your phone, both supporting WalletConnect. For example, MetaMask and U-Wallet.
Once you have connected to MetaMask, and even after you disconnect, there is no way to connect to U-Wallet.
Expected: should repeat all the steps as above, allowing me to choose U-Wallet at step 4 instead of MetaMask.
Observed: jumps from step 2 to 6. That is, when you choose WalletConnect in the KV dialog, it is already connected to MetaMask, and doesn't let you connect to anything else instead.
This does NOT happen with https://example.walletconnect.org/ so this must not be a bug in WalletConnect itself.