Issue trackers and the “Unable to deliver stream” error

Difficulty trackers and the “Unable to ship stream” error

There are an insectunique to Android 13, with this stack hint:

Deadly Exception: android.app.RemoteServiceException$CannotDeliverBroadcastException: cannot ship broadcast
       at android.app.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.foremost(ActivityThread.java:7898)
       at java.lang.replicate.Methodology.invoke(Methodology.java)
       at com.android.inner.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
       at com.android.inner.os.ZygoteInit.foremost(ZygoteInit.java:936)

Software code doesn’t seem within the stack hint and seems in purposes that don’t ship or obtain streams themselves. The perpetrator might be some library (probably Firebase Cloud Messaging).

So the neighborhood did the precise factor and reported this bug on September sixth. Up to now, a number of model corporations have reported seeing the difficulty with Android 13 units, together with:

  • Atlasian
  • the bbc
  • Costco
  • RingCentral
  • Aim
  • walmart

These are simply those identifiable by area identify. My present employer is a part of an analogous sized model and we’ve not posted a “me too!” remark, so I am guessing plenty of others are simply this drawback, hoping for a repair.

And it in all probability takes “somebody who is aware of somebody” for this matter to get a lot consideration.

Google’s challenge tracker has a daily historical past of returning conclusive outcomes. I’ve personally submitted
19 numbers in that component, of which solely 8 reached an actual closing state (Mounted, WAI or Infeasible). 3 are nonetheless open, together with one from 2019. And eight are “Deprecated”, which principally means it was ignored after which closed. I’ve received
a similar track record overall.

What complicates the issue is that this component is riddled with spam. Solely 38 of the newest 250 tickets are actual. The remaining are spam.

The sensation this creates is that Google has largely given up on this challenge tracker. Google is correct, after all, as it’s their drawback tracker.

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

In reality, the feasibility of this challenge tracker appears tied to the actual element. Some Jetpack libraries do a stable job of creating use of the difficulty tracker. Different parts, akin to the of developer.android.com

it is the place issues go to die, buried beneath much more spam.

If you happen to work for Google and need the neighborhood to report points, ensure that we all know the place you’re. Perhaps it is this challenge tracker, in a greater maintained element (or not less than one which spammers aren’t utilizing). Perhaps it is the GitHub challenge tracker for some related repository. You could discover that the very best method is thru unofficial means, akin to Kotlinlang Slack or social media. So long as it tells us what to make use of, we are able to use it.

And, um, if somebody may look that bugI’d drastically respect it.


— October 16, 2022