Allow FCM to bypass VPN for connections under a bypassable VPN
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
When running a VPN application, if it is a GMS, it will try to bypass the FCM connection in a bypassable VPN, but there seems to be no similar processing in microG. For FCM connections, the connections are still transmitted through VPN, which will cause the FCM reliability to decrease, so here request microG to let the FCM connection bypass the VPN on the bypassable VPN connection for better reliability.
Here is the link to how GMS is handled.
https://firebase.google.com/docs/cloud-messaging/network-configuration?hl=en-us#vpns
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue provides no file or test path; start by locating microG's FCM connection setup and comparing it with the linked GMS VPN handling guidance. Trace how bypassable VPN connections are represented and identify the existing FCM networking entry point. Done means FCM connections can bypass a bypassable VPN while other connections retain their normal routing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, firebase, java
- Domain
- mobile, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100