microg / microg/GmsCore

Cloud Messaging registration fails on Android 14/15/16

Open
#3,414 2 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Java
Stars
14.6k
Forks
3.2k
PR merge metrics
PR metrics pending

Description

After a clean installation of GmsCore (version v0.3.x or newer), the device fails to register for Google Cloud Messaging (GCM). While the "Check-in" service appears to be working correctly, apps that rely on push notifications (e.g., Signal, WhatsApp, YouTube) do not appear in the Cloud Messaging list, or stay in a "Connecting" state indefinitely.

Steps to Reproduce
Install microG GmsCore and GsfProxy.

Enable "Google Check-in" and "Google Cloud Messaging" in microG Settings.

Restart the device.

Open an app that requires push notifications.

Check microG Settings -> Cloud Messaging. The app is either missing or status is "Disconnected".

Expected Behavior
Apps should register automatically with GCM, and notifications should be delivered promptly.

Environment
microG GmsCore version: [0.3.1.240913]

Android version: [14]

ROM: [Es. LineageOS 22l]

Device: [Galaxy Note 8]

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the failure with GmsCore v0.3.1.240913 and GsfProxy on Android 14, following the listed Check-in and Cloud Messaging steps. Investigate why apps are missing from the Cloud Messaging list or remain disconnected; done means apps register automatically and notifications are delivered promptly.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.