2293174c-35ef-4e74-b1cc-041d3970a084 mozilla.components.support.base.android.UnboundHandlerException: You must bind the NotificationPermissionHandler to an activity
Categories
(Firefox for Android :: Crash Reporting, defect)
Tracking
()
People
(Reporter: Webworkr, Unassigned)
Details
(Keywords: crash)
Steps to reproduce:
Since this is an older crash from May 23, previous steps can no longer be traced.
Actual results:
2293174c-35ef-4e74-b1cc-041d3970a084
mozilla.components.support.base.android.UnboundHandlerException: You must bind the NotificationPermissionHandler to an activity
mozilla.components.support.base.android.UnboundHandlerException: You must bind the NotificationPermissionHandler to an activity
at mozilla.components.support.base.android.NotificationsDelegate.requestNotificationPermission(NotificationsDelegate.kt:112)
at mozilla.components.support.base.android.NotificationsDelegate.notify$default(NotificationsDelegate.kt:66)
at mozilla.components.lib.crash.CrashReporter.onCrash$lib_crash_release(CrashReporter.kt:468)
at mozilla.components.lib.crash.handler.CrashHandlerService$handleCrashIntent$1.invokeSuspend(CrashHandlerService.kt:25)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:9)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:111)
at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:4)
at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:3)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:98)
Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@321cbd8, Dispatchers.IO]
Expected results:
No crash
| Reporter | ||
Comment 1•1 year ago
|
||
"Settings" menu > "About Firefox Nightly" > "Crashes":
There are no existing crash reports linked so far.
Comment 2•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Fenix::Crash Reporting' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 3•1 year ago
|
||
The severity field is not set for this bug.
:royang, could you have a look please?
For more information, please visit BugBot documentation.
Comment 4•1 year ago
|
||
Wrong component. Not a crash. Moving to General.
Updated•1 year ago
|
Comment 5•1 year ago
|
||
I'm not seeing any matching crashes in socorro matching this signature. But it looks like it is around submitting crash reports using a notification. This should be fixed in 133, going to monitor this until then.
Comment 6•1 year ago
|
||
The severity field is not set for this bug.
:royang, could you have a look please?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
Updated•1 year ago
|
Description
•