1921866 - Crash in [@ mozilla.components.support.base.android.UnboundHandlerException: at mozilla.components.support.base.android.NotificationsDelegate.requestNotificationPermission(NotificationsDelegate.kt)]

Status: RESOLVED WORKSFORME

(Firefox for Android :: Push, defect)

Description

[Chris Peterson [:cpeterson]]

Crash report: https://crash-stats.mozilla.org/report/index/477023fa-f6ac-472d-805b-f9abc0240930

This crash is a regression in 132. The earliest crashing build ID is 20240912092307. The most recent crashing build ID is 20240913100931 (2024-09-13), so maybe this crash has already been fixed.

Exception: mozilla.components.support.base.android.UnboundHandlerException
Message: You must bind the NotificationPermissionHandler to an activity

Top 8 frames:

0  mozilla.components.support.base.android.NotificationsDelegate  requestNotificationPermission  NotificationsDelegate.kt:125
1  mozilla.components.support.base.android.NotificationsDelegate  notify$default  NotificationsDelegate.kt:68
2  mozilla.components.feature.webnotifications.WebNotificationFeature$onShowNoti...  invokeSuspend  WebNotificationFeature.kt:173
3  kotlin.coroutines.jvm.internal.BaseContinuationImpl  resumeWith  ContinuationImpl.kt:9
4  kotlinx.coroutines.DispatchedTask  run  DispatchedTask.kt:111
5  kotlinx.coroutines.internal.LimitedDispatcher$Worker  run  LimitedDispatcher.kt:4
6  kotlinx.coroutines.scheduling.TaskImpl  run  Tasks.kt:3
7  kotlinx.coroutines.scheduling.CoroutineScheduler$Worker  run  CoroutineScheduler.kt:98

Comment 1

[Chris Peterson [:cpeterson]]

All of the crash reports are from Android 33+. Was there was a change in Android 33's notification permissions? Or maybe this is just a coincidence, assuming Nightly users are probably more likely to run recent Android OS versions?

Comment 2

[Chris Peterson [:cpeterson]]

Correction: looks like there was one crash report from Nightly 130, but then a big increase in Nightly 132.

https://crash-stats.mozilla.org/report/index/e2711b11-a6ef-4f08-8dcf-12c920240728

Comment 3

[Ryan VanderMeulen [:RyanVM]]

Mihai, is this spike possibly related to any of the recent work you've been landing?

Comment 4

[Mihai Adrian Carare [:mcarare]]

I see this crash is for a single device, maybe even a single user (the same install time for all reports) ?!

Comment 5

[Ryan VanderMeulen [:RyanVM]]

Whoops, you're right. And an older build at that.

Comment 6

[Chris Peterson [:cpeterson]]

Reopening because this crash spiked in Nightly 135 starting 2024-12-16. I suspect the automatic crash reporting setting (bug 1812770) that landed on 2024-12-14 is causing a lot of reports to be submitted that might have been backlogged or not caught before. For example, the 2952 crash reports received this week were from just 73 installs.

Comment 7

[BugBot [:suhaib / :marco/ :calixte]]

Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.