Closed Bug 1815976 Opened 2 years ago Closed 1 year ago

Push notification is crashing the browser: Crash in [@ java.lang.IllegalStateException: at mozilla.components.lib.push.firebase.AbstractFirebasePushService.onMessageReceived(AbstractFirebasePushService.kt:145)]

Categories

(Fenix :: Push, defect, P3)

Firefox 111
All
Android
defect

Tracking

(firefox114 ?, firefox115 ?, firefox116 ?)

RESOLVED WORKSFORME
Tracking Status
firefox114 --- ?
firefox115 --- ?
firefox116 --- ?

People

(Reporter: ale82ale, Unassigned)

References

Details

Crash Data

Steps to reproduce:

Evry time i receive a push notification (not a normal notification)
Just to avoid confusion (even if such an explaination is not supposed to be need for a developer) with push notification i mean:
Browser tab closed(eg twitter)-----> notication arrives-----> browser crashes
heres the log
8b52e29-3a27-425d-9e49-cfbe2010b2a5java.lang.IllegalStateException: You need to call PushProcessor.install() on your Push instance from Application.onCreate().----java.lang.IllegalStateException: You need to call PushProcessor.install() on your Push instance from Application.onCreate().at mozilla.components.lib.push.firebase.AbstractFirebasePushService.onMessageReceived(AbstractFirebasePushService.kt:156)at com.google.firebase.messaging.FirebaseMessagingService.handleIntent(FirebaseMessagingService.java:786)at com.google.firebase.messaging.EnhancedIntentService$$ExternalSyntheticLambda1.run(R8$$SyntheticClass:11)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)at com.google.android.gms.common.util.concurrent.zza.run(com.google.android.gms:play-services-basement@@18.1.0:7)at java.lang.Thread.run(Thread.java:920).
bug affect nighlty from 8 feb.

Actual results:

Push notifications should be received without crashing the browser

Expected results:

Fenix nighlty crash

The severity field is not set for this bug.
:cpeterson, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(cpeterson)
Duplicate of this bug: 1822442
Flags: needinfo?(cpeterson)

Thanks for filing this bug report, Alessandro. I found a crash report that matches the crash you describe:

https://crash-stats.mozilla.org/report/index/963d7a5e-0995-499e-8c5f-4c5270230603

The crash volume is pretty low. I only see 4 crash reports from Firefox 113 and none since then.

java.lang.IllegalStateException: You need to call PushProcessor.install() on your Push instance from Application.onCreate().
	at mozilla.components.lib.push.firebase.AbstractFirebasePushService.onMessageReceived(AbstractFirebasePushService.kt:145)
	at com.google.firebase.messaging.FirebaseMessagingService.handleIntent(FirebaseMessagingService.java:789)
	at com.google.firebase.messaging.EnhancedIntentService$$ExternalSyntheticLambda1.run(R8$$SyntheticClass:11)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
	at com.google.android.gms.common.util.concurrent.zza.run(com.google.android.gms:play-services-basement@@18.1.0:7)
	at java.lang.Thread.run(Thread.java:784)
Severity: -- → S2
Status: UNCONFIRMED → NEW
Crash Signature: [@ java.lang.IllegalStateException: at mozilla.components.lib.push.firebase.AbstractFirebasePushService.onMessageReceived(AbstractFirebasePushService.kt:13)] [@ java.lang.IllegalStateException: at mozilla.components.lib.push.firebase.AbstractFirebasePush…
Ever confirmed: true
Priority: -- → P3
Summary: Push notification is crashing the browser → Push notification is crashing the browser: Crash in [@ java.lang.IllegalStateException: at mozilla.components.lib.push.firebase.AbstractFirebasePushService.onMessageReceived(AbstractFirebasePushService.kt:145)]

Since the crash volume is low (less than 15 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.

For more information, please visit BugBot documentation.

Severity: S2 → S3

No more crashes have shown up in the last 6 months.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.