microg / microg/GmsCore

companion is crashing

Open
#3,218 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Java
Stars
14.6k
Forks
3.2k
Avg merge
12d 11h
Merged PRs (30d)
4

Description

Describe the bug
Got constant pop up about microg companion crashing (while using other apps or even the launcher)
EDIT : Crash related to : version 0.3.10.250932
com.google.android.gms
RE-EDIT : update microg to version 0.3.11.250932 and it still happens

To Reproduce
It happens randomly, while not using the app.

time: 1767430190650
msg: java.lang.NullPointerException: <get-second>(...) must not be null
stacktrace: java.lang.NullPointerException: <get-second>(...) must not be null
	at org.microg.gms.gcm.registeration.ChimeGmsRegistrationHelper$handleRegistration$response$1.invokeSuspend(ChimeGmsRegistrationHelper.kt:74)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:108)
	at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:115)
	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:103)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:584)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:793)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:697)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:684)
	Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@1a7652, Dispatchers.Main.immediate]

Expected behavior
No crashes

Screenshots
Config in companion :
Google account : all checked except the first one (trust Google...)
Terminal registration : on with native profile
Cloud messaging : on
Terminal attestation : on

System
Android Version: 16
Custom ROM: crDroid 12.4 (derived from LineageOS 23)

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 by inspecting ChimeGmsRegistrationHelper.kt at line 74, where the reported NullPointerException occurs during GCM registration. Reproduce the crash with the reported microG configuration and Android 16 environment if possible; done means registration no longer produces this crash and the reported scenario remains stable.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.