Problem Trackers and the “Can not Provide Broadcast” Bug
There is a bug, special to Android 13, with this stack trace:
Lethal Exception: android.application.RemoteServiceException$CannotDeliverBroadcastException: cannot deliver broadcast
at android.application.ActivityThread.throwRemoteServiceException(ActivityThread.java:1980)
at android.app.ActivityThread.-$$Nest$mthrowRemoteServiceException()
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2242)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:201)
at android.os.Looper.loop(Looper.java:288)
at android.app.ActivityThread.principal(ActivityThread.java:7898)
at java.lang.replicate.Process.invoke(Strategy.java)
at com.android.interior.os.RuntimeInit$MethodAndArgsCaller.operate(RuntimeInit.java:548)
at com.android.inside.os.ZygoteInit.main(ZygoteInit.java:936)
Application code does not seem in the stack trace, and it reveals up in applications
that do not ship or obtain broadcasts on their individual. The culprit in all probability is some
library (maybe Firebase Cloud Messaging).
So, the neighborhood did the right issue and claimed this bug, back again on September 6. To
day, a bunch of title-brand companies have claimed seeing the dilemma with Android 13
gadgets, including:
- Atlassian
- the BBC
- Costco
- RingCentral
- Target
- Walmart
All those are just the types identifiable by area identify. My present-day employer
is aspect of a similarly-sized brand name, and we have not posted a “me also!” comment,
so my guess is that a lot of other individuals are just looking at this challenge, hoping for a take care of.
And it is almost certainly going to get “somebody who appreciates somebody” for this situation to get substantially
consideration.
Google’s difficulty tracker has a so-so keep track of report
of receiving conclusive results. Personally, I have filed
19 issues in that part,
only 8 of which obtained to a authentic finish position (Fixed, WAI, or Infeasible). 3 are
nevertheless open up, including just one from 2019. And 8 are “Obsolete”, which essentially implies
it was disregarded and then shut. I have
a very similar keep track of file general.
Compounding the difficulty is that this ingredient is riddled with spam.
Only 38 of the most the latest 250 tickets are true. The relaxation are spam.
The vibe that this provides off is that Google has mostly supplied up on this problem
tracker. Which is Google’s suitable, of course, as it is their difficulty tracker.
But, then, how does Google want us to report complications like the a single cited above?
In truth of the matter, the viability of this concern tracker appears to be tied to the certain
ingredient. Some Jetpack libraries do a good work of making use of the situation tracker.
Other factors, like the one for developer.android.com
are in which problems go to die, buried beneath still more spam.
If you function for Google, and you want the group to report problems, make guaranteed that
we know where by that is. Perhaps it is this challenge tracker, in a far better-preserved
element (or at least a single the spammers are not making use of).
Probably it is GitHub’s problem tracker for some appropriate repo. Maybe
you come across the very best solution is by unofficial implies, this kind of as Kotlinlang Slack or
social media. So extended as you notify us what we should use, we can use it.
And, um, if any individual could glimpse at that bug,
I’d truly enjoy it.
