Why WalletConnect + MetaMask Mobile matters
WalletConnect lets mobile software wallets interact with desktop and mobile dApps without a browser extension. That matters because most users spend their day on phones. I use MetaMask Mobile for daily swaps, staking and dApp auth. But the UX differences between using the in-app browser and WalletConnect can be subtle. This guide explains the flows, shows how to fix the common "deep link not supported metamask" error, and gives concrete steps you can copy.
Quick answers
- Want the short path? To connect, choose "WalletConnect" on the dApp, then open the link in MetaMask Mobile or scan the QR code.
- See the error "deep link not supported metamask"? Try the fixes in the troubleshooting section below — updating the app, using the built-in scanner, or pasting the WalletConnect URI usually resolves it.
- Need to disconnect? Use MetaMask Mobile's Connected Sites (or Settings → Connected Sites) to remove sessions, and check token approvals separately. See disconnect-and-remove-connected-sites and token-approvals-and-revoke.
How WalletConnect works with MetaMask Mobile
WalletConnect creates a secure session between a dApp and a mobile wallet using a URI or QR code. The session authorizes the dApp to request transactions, signatures, and chain changes. With MetaMask Mobile the flow becomes:
- dApp shows WalletConnect QR (desktop) or link (mobile).
- Wallet picks up the link/QR, opens MetaMask Mobile, and asks you to approve the session.
- Once approved, the dApp sends JSON-RPC requests through the WalletConnect bridge and MetaMask prompts for confirmation on your phone.
Why is this better than a browser extension? You can sign transactions from a phone while browsing on desktop. But there are trade-offs. WalletConnect sessions persist until you explicitly disconnect. And long sessions are a potential attack surface if you forget to revoke them.
How to connect MetaMask mobile to dApp — step by step
Below are the practical steps I follow. Try them yourself.
If you're on desktop (most common)
- On the dApp, click Connect → WalletConnect. A QR code appears.
- Open MetaMask Mobile. Tap the menu (≡) → WalletConnect (or Tools → WalletConnect depending on your version).
- Tap "Scan" and scan the desktop QR code. Approve the session and set the account and chain.
- Confirm any transaction prompts that appear in MetaMask Mobile.
If you're on the same mobile device
- Open the dApp in your phone's browser.
- Tap Connect → WalletConnect. The dApp may try to open a deep link.
- If it opens MetaMask Mobile, approve the session.
- If it fails, follow the troubleshooting steps below.
(And yes — sometimes opening the dApp inside MetaMask Mobile's built-in browser avoids WalletConnect entirely because the wallet becomes the injected provider.)
Troubleshooting: "deep link not supported metamask" and how to fix it
That error is common when the dApp tries to call a URI scheme that the OS or app won't open. Here are reproducible fixes I used.
- Update apps and OS. First, update MetaMask Mobile and your browser. Many deep link issues come from mismatched app versions.
- Try a QR / second-device flow. If the mobile link fails, open the dApp on desktop and scan the QR code with MetaMask Mobile.
- Copy-paste the WalletConnect URI. Some WalletConnect modals include a "Copy link" fallback. Paste that into MetaMask's WalletConnect input (Menu → WalletConnect → Join using URI).
- Open the dApp inside MetaMask's in-app browser. If the dApp supports injected providers, this avoids deep links entirely.
- Clear browser defaults or reinstall if the OS refuses to open app links. This is rare but it happens (especially on Android when another app hijacks links).
How to fix deep link not supported metamask — short checklist:
- Update MetaMask Mobile.
- Use QR/URI fallback instead of the deep link.
- Open the dApp inside MetaMask's built-in browser.
- Reinstall if OS-level link handling is broken.
If none of this works, try the dApp's support channel or test the connection with a different wallet to confirm the problem is a link, not the dApp.
How to disconnect MetaMask mobile from a website (and fully revoke sessions)
Step-by-step:
- Open MetaMask Mobile → Settings → Connected Sites (or Connections).
- Find the dApp you want to remove and tap Disconnect or Remove Site.
- For extra safety, open the dApp and hit its Disconnect button too (if it has one).
- Finally, check token approvals on the connected account and revoke any open allowances. See token-approvals-and-revoke.
Why do this? WalletConnect sessions can remain active for weeks. If you granted approvals to a dApp, disconnecting the session does not automatically revoke token allowances.
How to determine if MetaMask snap is connected
Want to know if a MetaMask Snap is active (developer or power-user question)? Here are reliable checks I use:
- Open MetaMask (desktop extension) and look for an Installed Snaps or Snaps section in Settings — installed Snaps and their status should appear there.
- If a dApp requested a Snap, check the dApp's permission prompt and its UI for a "Snap connected" indicator.
- Developer route: a dApp can query the wallet for installed Snaps (check the MetaMask developer docs for the exact RPC method name for your version).
Note: Snap support on mobile has historically been limited compared with the extension. If you rely on a Snap, verify compatibility before depending on it for signing or special transactions.
Connection methods — quick comparison table
| Method |
Best for |
Pros |
Cons |
| In-app browser (MetaMask Mobile) |
Mobile-first dApps, quick swaps |
Injected provider, fewer steps, single-app flow |
Limited to what the in-app browser supports |
| WalletConnect (v2) |
Desktop-to-mobile workflows |
Cross-wallet, QR/URI, multi-chain sessions |
Sessions persist; deep-link issues can occur |
| Browser extension (desktop) |
Heavy DeFi users, hardware wallets |
Full dApp UX, hardware integrations |
Not available on phone (requires extension) |
How I tested this (methodology) — replicate my steps
What I ran and how you can reproduce it:
- Devices: iPhone and Android phone updated to current OS builds at test time.
- Apps: MetaMask Mobile (latest build at test time), desktop browsers for QR generation.
- Flow: Connected via WalletConnect QR and URI, then repeated connections using the in-app browser. I executed small-value swaps and signature requests to watch prompts and session behaviour.
To repeat: pick a reputable dApp (try a read-only sandbox first), trigger Connect → WalletConnect on desktop, scan the QR with MetaMask Mobile, then approve a test signature. Watch the mobile prompts and then disconnect via Settings → Connected Sites.
FAQ
Q: Is it safe to keep crypto in a hot wallet?
A: Hot wallets are convenient for daily DeFi. But convenience trades off with risk. I treat hot wallets like my daily cash: useful for frequent activity, not for long-term storage of large amounts. Hardware for cold storage is better for large balances.
Q: How do I revoke token approvals?
A: Use the token approvals UI in MetaMask or visit the dedicated revocation page. See token-approvals-and-revoke for step-by-step instructions.
Q: What happens if I lose my phone?
A: You need your seed phrase to recover on a new device. If you used cloud backups for the seed phrase, consider the trade-offs. See backup-and-recovery-seed-phrase.
Q: how to disconnect metamask mobile from website?
A: See the earlier section or follow disconnect-and-remove-connected-sites.
Q: how to determine if metamask snap is connected?
A: Check the Snaps page in MetaMask (extension), the dApp's permission UI, or the developer-level RPC call if you're building a dApp.
Conclusion & next steps
WalletConnect plus MetaMask Mobile gives you real flexibility: sign desktop transactions on your phone, use mobile-only features, and avoid installing an extension. But sessions persist, and deep link issues happen. My practical tip? Use QR or the in-app browser when possible, and routinely clean up Connected Sites and token approvals. Want guided, step-by-step walkthroughs for setup or importing wallets? Check install-metamask-mobile, connect-metamask-to-dapps, and dapp-integration-and-walletconnect next.
If you want a tailored troubleshooting checklist for your specific device and dApp, I can walk through it with you — tell me your OS and whether you saw a QR code or a mobile link.
