Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

RuntimeException: WakeLock under-locked wake:com.google.firebase.messaging

See original GitHub issue

This bug is closed #1484, saying it was solved in 20.1.6, but I get the same crash with cloud messaging 20.2.0 (using Firebase BoM 25.4.1)

Fatal Exception: java.lang.RuntimeException: WakeLock under-locked wake:com.google.firebase.messaging
       at android.os.PowerManager$WakeLock.release(PowerManager.java:1619)
       at android.os.PowerManager$WakeLock.release(PowerManager.java:1589)
       at android.os.PowerManager$WakeLock$1.run(PowerManager.java:1484)
       at android.os.Handler.handleCallback(Handler.java:808)
       at android.os.Handler.dispatchMessage(Handler.java:101)
       at android.os.Looper.loop(Looper.java:166)
       at android.app.ActivityThread.main(ActivityThread.java:7529)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:245)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:921)

Same device, same version as reported in #1484. I couldn’t add this info to that issue, as it prevents to add any new comments. So submitting as new issue.

Issue Analytics

State:
Created 3 years ago
Comments:8 (5 by maintainers)

Top GitHub Comments

1reaction

rpattabicommented, Jun 23, 2020

@ashwinraghav I understand it is easy to get confused about actual version numbers in a complex setup. In this case, I’m pretty sure that this issue results in our production app using firebase cloud messaging 20.2.0 (through Firebase BoM 25.4.1). The dependency tree I shared corresponds to the commit we pushed to production.

As you mentioned, I looked into our app bundle (aab) published to Google Play. It has base/root/firebase-messaging.properties with the following contents:

version=20.2.0
client=firebase-messaging
firebase-messaging_client=20.2.0

Additionally, if it is accessible to you, here is the crash report in crashlytics.

0reactions

google-oss-botcommented, Oct 28, 2021

Since there haven’t been any recent updates here, I am going to close this issue.

@rpattabi if you’re still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.

Top Results From Across the Web

WakeLock under-locked wake:com.google.firebase ...

I recently see rare occurrences of this bug / crash. Full log: Fatal Exception: java.lang.RuntimeException: WakeLock under-locked wake:com.

Wakelock Underlocked Exception Using Cwaclocpoll - ADocLib

RuntimeException : WakeLock underlocked wake:com.google.firebase.messaging.1128.android. wake lockwakelock.release Intent service new Intentcontext ...

WakeLock Timeout causes WakeLock under-locked on ...

If you aquire a WakeLock with a Timeout, but then manually call release before the timeout, a RuntimeException is thrown at the end...

Android – java.lang.RuntimeException: WakeLock under ...

I have uploaded my application on google play but users have reported the following exception. java.lang.RuntimeException: WakeLock under-locked C2DM_LIB.

java.lang.RuntimeException.WakeLock under-locked wake:com ...

完整的日志。 Fatal Exception: java.lang.RuntimeException: WakeLock under-locked wake:com.google.firebase.messaging at android.os.