MetaMask / MetaMask/metamask-mobile

Deeplinks don't work with a VPN (Wireguard)

Open
#4,048 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
3k
Forks
1.7k
Avg merge
1d 14h
Merged PRs (30d)
669

Description

**Describe the bug**
If I turn on wireguard VPN with a kernel module metamask's browser sign in stops working
So if I try to login to opensea it will ask me to choose a browser

**Screenshots**
Just imagine android is asking you to choose an app to open a link

**To Reproduce**
_Steps to reproduce the behavior_
1. Turn on the vpn
2. Kill the metamask app
3. Go to opensea, try to login
4. It asks to choose a browser, but won't do anything after that

**Expected behavior**
Sign in with metamask working

**Smartphone (please complete the following information):**
- Device: Xiaomi Mi 9
- OS: Lineage OS (a10)
- App Version 4.3.1 (859)

-------------------------------------------------------------
_to be added after bug submission by internal support / PM_
**Severity**

- How critical is the impact of this bug on a user?
- Add stats if available on % of customers impacted
- Is this visible to all users?
- Is this tech debt?

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the Android deep-link sign-in flow with WireGuard enabled on the stated Xiaomi Mi 9 and Lineage OS setup, then trace the browser selection and return-to-MetaMask path. Done means signing in to OpenSea with MetaMask works after the app is killed and the VPN is enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, react-native, typescript
Domain
authentication, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.