microg / microg/GmsCore

Chrome does not register to gcm anymore

Open
#676 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

☁️ Cloud / Push Messaging
Dominant language
Java
Stars
14.6k
Forks
3.2k
Avg merge
12d 11h
Merged PRs (30d)
4

Description

Hey,

I am facing the issue that Chrome does not register to gcm for some time now, although it did before.

It seems to be related to an issue with the sender id.

Here is the related logcat output:

**GmsGcmRegisterSvc** 
onBind: Intent { act=com.google.android.c2dm.intent.REGISTER pkg=com.google.android.gms }
**GmsHttpFormClient** 
-- Request --
X-GOOG.USER_AID=3557875368816913745&device=3557875368816913745&app=com.android.chrome&appid=d-fambNGVew&cert=38918a453d07199354f8b19af05ec6562ced5788&app_ver=353811002&app_ver_name=70.0.3538.110&gmsv=13280000&scope=*&osv=27&sender=BDd3_hVL9fZi9Ybo2UUzA284WG5FZR30_95YeZJsiApwXKpNcF1rRPF3foIiBHXRdJI2Qhumhf6_LFTeZaNndIo&subtype=BDd3_hVL9fZi9Ybo2UUzA284WG5FZR30_95YeZJsiApwXKpNcF1rRPF3foIiBHXRdJI2Qhumhf6_LFTeZaNndIo
**GmsGcmRegisterMgr** 
java.io.IOException: Error=INVALID_SENDER
	at org.microg.gms.common.HttpFormClient.request(HttpFormClient.java:90)
	at org.microg.gms.common.HttpFormClient$1.run(HttpFormClient.java:187)
	at java.lang.Thread.run(Thread.java:764)

I get this result in all apps that try to register for web push notification, e.g.

https://gauntface.github.io/simple-push-demo/

This however works with Firefox, but sadly ff still misses several other features of web push...

Kind regards

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the logcat trace and inspect org.microg.gms.common.HttpFormClient.java, especially the request path around lines 90 and 187, then follow how GmsGcmRegisterMgr handles INVALID_SENDER. Reproduce the registration failure with the linked simple push demo and compare the sender data in the request; done means Chrome and other web-push apps register successfully.

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
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.