microg / microg/GmsCore

Blank permission request dialog shown (GmsGcmRegister java.lang.RuntimeException: Push permission not granted to app)

Open
#1,240 4 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

Since upgrading UnifiedNlp yesterday I've gotten a few weird permission popups:

signal-2020-10-20-162453

Looking at Logcat they seem to be associated with this error:

java.lang.RuntimeException: Push permission not granted to app
	at org.microg.gms.gcm.PushRegisterServiceKt.ensureAppRegistrationAllowed(PushRegisterService.kt:73)
	at org.microg.gms.gcm.PushRegisterServiceKt$ensureAppRegistrationAllowed$1.invokeSuspend(Unknown Source:10)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:56)
	at androidx.lifecycle.DispatchQueue.drainQueue(DispatchQueue.kt:76)
	at androidx.lifecycle.DispatchQueue.enqueue(DispatchQueue.kt:106)
	at androidx.lifecycle.DispatchQueue.access$enqueue(DispatchQueue.kt:32)
	at androidx.lifecycle.DispatchQueue$runOrEnqueue$$inlined$with$lambda$1.run(DispatchQueue.kt:93)
	at android.os.Handler.handleCallback(Handler.java:873)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loop(Looper.java:193)
	at android.app.ActivityThread.main(ActivityThread.java:6718)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

I haven't found a pattern in when the popup is shown yet. If I dismiss it it seems to come back at random, sometimes within a few seconds and sometimes after some hours.

Please let me know if I can assist in debugging -- and thank you for your work on microg!

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 org.microg.gms.gcm.PushRegisterService.kt at ensureAppRegistrationAllowed, using the supplied Logcat trace and the reported blank permission dialog as the entry points. Reproduce the intermittent popup if possible and trace the permission-request path; done means the reported blank dialog and recurring Push permission not granted error are addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java, kotlin
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.