Factor Trackers and the “Can not Ship Broadcast” Worm
There may be a malicious program, distinctive 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.primary(ActivityThread.java:7898)
at java.lang.replicate.Approach.invoke(Approach.java)
at com.android.inner.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
at com.android.inner.os.ZygoteInit.primary(ZygoteInit.java:936)
Utility code does no longer seem within the stack hint, and it displays up in apps
that don’t ship or obtain publicizes on their very own. The perpetrator most likely is a few
library (in all probability Firebase Cloud Messaging).
So, the neighborhood did the appropriate factor and reported this malicious program, again on September 6. To
date, a host of name-brand firms have reported seeing the issue with Android 13
gadgets, together with:
- Atlassian
- the BBC
- Costco
- RingCentral
- Goal
- Walmart
The ones are simply those identifiable by way of area call. My present employer
is a part of a similarly-sized model, and we haven’t posted a “me too!” remark,
so my bet is that loads of others are simply staring at this factor, hoping for a repair.
And it’s most likely going to take “anyone who is aware of anyone” for this factor to get a lot
consideration.
Google’s factor tracker has a so-so monitor file
of having conclusive effects. For my part, I’ve filed
19 problems in that part,
simplest 8 of which were given 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 mainly way
it used to be omitted after which closed. I’ve
a identical monitor file general.
Compounding the issue is that this part is riddled with unsolicited mail.
Best 38 of the latest 250 tickets are actual. The remaining are unsolicited mail.
The vibe that this offers off is that Google has in large part given up in this factor
tracker. That’s Google’s proper, in fact, as it’s their factor tracker.
However, then, how does Google need us to document issues like the only cited above?
Actually, the viability of this factor tracker turns out tied to the specific
part. Some Jetpack libraries do a forged process of constructing use of the problem tracker.
Different elements, like the only for developer.android.com
are the place problems move to die, buried underneath but extra unsolicited mail.
In case you paintings for Google, and you need the neighborhood to document problems, be sure that
we all know the place this is. Possibly it’s this factor tracker, in a better-maintained
part (or a minimum of one the spammers aren’t the use of).
Possibly it’s GitHub’s factor tracker for some related repo. Possibly
you in finding the most productive way is by way of unofficial way, corresponding to Kotlinlang Slack or
social media. As long as you let us know what we must use, we will be able to use it.
And, um, if anyone may take a look at that malicious program,
I’d in point of fact admire it.
