Push notifications (FCM) stop working while the VPN is connected
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 72/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 领域
- mobile, networking
调研方向
Start by reading NetworkSettingsPoller.applySettingsToBuilder, the location named in the report, and review the proposed exclusion of Google Play Services from the VPN tunnel. Reproduce the failure with the reported ADB dumpsys command, then verify FCM reconnects after Wi-Fi and mobile network changes while private resources remain reachable.
由索引模型根据 Issue 内容生成。
描述
Describe the Bug
With the Pangolin VPN connected, Google push notifications (FCM) stop arriving after a while. This affects every app (messaging, Home Assistant, etc.) and happens on Wi-Fi and mobile data alike. As soon as the VPN is disconnected, FCM reconnects within seconds and delivers the queued messages.
I tested with adb:
adb shell dumpsys activity service com.google.android.gms/.gcm.GcmService
With the VPN connected:
not connected:
Next backoff interval per network:
GcmNetwork{215 VPN(17) [WiFi(1)]}, PT4H
...
Connecting using McsConnection{GcmNetwork{215 VPN(17) [WiFi(1)]}, type=1, isVpnConnected=true}
Failed connection err:3
Connecting using McsConnection{GcmNetwork{215 VPN(17) [Cell(0)]}, type=0, isVpnConnected=true}
Failed connection err:3
Every attempt on the VPN network failed usually within 15–50 ms, and the backoff grows to 4 hours. An FCM connection opened before the VPN came up keeps working until it drops, which is why it looks like "after a while".
When the VPN is disconnected, the same dumpsys immediately shows Is client connected: true followed by Successful broadcast to ... for the queued messages.****
Here some pointers:
- dumpsys connectivity shows the VPN as VpnTransportInfo{type=1, sessionId=pangolin, bypassable=false ...} covering all UIDs. FCM uses a bypass for its push channel only on VPNs that allow it (Firebase docs); here it has to connect through the VPN network, and that fails.
- Ordinary sockets through the same VPN work: from adb shell, nc -4 mtalk.google.com 5228 succeeds and DNS resolves normally (the client's DNS proxy forwards to the upstream). So the tunnel itself passes traffic; only the GMS push connection on the VPN network fails.
- Not related to battery: Pangolin is in the user doze whitelist (unrestricted). Not related to the DNS upstream setting. The test networks have no global IPv6, so IPv6 isn't involved.
I did a small patch, by excluding Google Play Services from the tunnel inside NetworkSettingsPoller.applySettingsToBuilder.
Tested on a 0.8.2 debug build (arm64): the VPN stays bypassable=false, its UID ranges skip the GMS UID, FCM connects on the underlying network and reconnects after Wi-Fi off/on and Wi-Fi / mobile switches, and private resources keep working (But, on another note, a "per app" VPN would be even better.).
Environment
- OS Type & Version: Debian 13 (trixie) x86_64,Android 17 (Pixel 9)
- Pangolin Version: 1.25.3
- Edition (Community or Enterprise): Community
- Gerbil Version: 1.5.2
- Traefik Version: v3.7
- Newt Version: 1.16.0
- Client Version: 0.8.2 (Play Store)
To Reproduce
Steps to reproduce
Connect the Pangolin VPN on Android.
Leave the phone idle until the existing FCM connection drops (or toggle Wi-Fi off/on).
Run adb shell dumpsys activity service com.google.android.gms/.gcm.GcmService: you'll see Not connected and repeated Failed connection err:3.
Disconnect the VPN: FCM connects immediately.
AI Disclosure
Ai assisted formatting.
Expected Behavior
With the VPN connected, Google push notifications (FCM) should keep arriving as they do without the VPN.
Google Play Services should be able to reconnect its push channel at any time: after the phone has been idle, after Wi-Fi goes off and on, and when switching between Wi-Fi and mobile data.
A split-tunnel VPN that only carries private resources shouldn't block notifications for every other app on the phone.
- 主要语言
- Kotlin
- 星标
- 46
- 派生
- 15
- 平均合并
- 1 分钟
- 30 天内合并 PR
- 3
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
fosrl/android 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 55/100
-
bug needs investigating
难度 4/5 3-5 天 新手友好度 45/100
-
Possible client registration regression on version 0.7.0可能已有人在做 @oschwartz10612 于 26 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 45/100
-
难度 4/5 3-5 天 新手友好度 48/100
-
Switching organizations breaks Olm hole punching for the same client installation可能重新可做 @oschwartz10612 于 58 天前认领,目前没有进行中的 PR。 未关闭needs investigating
难度 4/5 3-5 天 新手友好度 48/100
相似的 Issue
-
bug desktop
难度 2/5 1-3 小时 新手友好度 85/100
simplex-chat/simplex-chat#8291 ·
维护者通常 1 天内回复
-
help wanted needs investigation priority: low
难度 2/5 1-3 小时 新手友好度 62/100
-
bug
难度 2/5 1-3 小时 新手友好度 62/100
LeanBitLab/LeanType#883 ·
维护者通常 1 天内回复
-
Heavy legs 1.12–1.17: compiler corpus goldens not regenerated for #4770可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 74/100
intellij-elixir/intellij-elixir#4782 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
komikku-app/komikku#1983 ·
维护者通常 1 天内回复