Subject Trackers and the “Cannot Ship Broadcast” Bug

Subject Trackers and the “Cannot Ship Broadcast” Bug

There may be a bug, distinctive to Android 13, with this stack hint:

Deadly Exception:$CannotDeliverBroadcastException: cannot ship broadcast
       at android.os.Handler.dispatchMessage(
       at android.os.Looper.loopOnce(
       at android.os.Looper.loop(
       at java.lang.mirror.Technique.invoke(

Software code doesn’t seem within the stack hint, and it reveals up in apps
that don’t ship or obtain broadcasts on their very own. The perpetrator most likely is a few
library (probably Firebase Cloud Messaging).

So, the group did the appropriate factor and reported this bug, again on September 6. To
date, a bunch of name-brand firms have reported seeing the issue with Android 13
units, together with:

  • Atlassian
  • the BBC
  • Costco
  • RingCentral
  • Goal
  • Walmart

These are simply those identifiable by area identify. My present employer
is a part of a similarly-sized model, and we haven’t posted a “me too!” remark,
so my guess is that a number of others are simply watching this situation, hoping for a repair.

And it’s most likely going to take “anyone who is aware of anyone” for this situation to get a lot

Google’s situation tracker has a so-so monitor report
of getting conclusive outcomes. Personally, I’ve filed
19 points in that part,
solely 8 of which acquired to an actual finish standing (Mounted, WAI, or Infeasible). 3 are
nonetheless open, together with one from 2019. And eight are “Out of date”, which principally means
it was ignored after which closed. I’ve
an analogous monitor report total.

Compounding the issue is that this part is riddled with spam.
Solely 38 of the latest 250 tickets are actual. The remainder are spam.

The vibe that this offers off is that Google has largely given up on this situation
tracker. That’s Google’s proper, after all, as it’s their situation tracker.

However, then, how does Google need us to report issues just like the one cited above?

In fact, the viability of this situation tracker appears tied to the actual
part. Some Jetpack libraries do a stable job of constructing use of the problem tracker.
Different parts, like the one for
are the place points go to die, buried underneath but extra spam.

In case you work for Google, and also you need the group to report points, make it possible for
we all know the place that’s. Maybe it’s this situation tracker, in a better-maintained
part (or at the very least one the spammers aren’t utilizing).
Maybe it’s GitHub’s situation tracker for some related repo. Maybe
you discover the most effective strategy is by unofficial means, reminiscent of Kotlinlang Slack or
social media. As long as you inform us what we should always use, we are able to use it.

And, um, if anyone might take a look at that bug,
I’d actually admire it.