java.lang.IllegalStateException: Too many receivers, total of 1000

[nevenaCBC]

Environment

• Android Studio version: 3.6.3
• Firebase Component: Firebase Crashlytics, Firebase Analytics, Firebase Remote Config
• Component version: 17.2.2, 18.0.0, 20.0.0

Additionally:

        classpath 'com.android.tools.build:gradle:3.6.4'
        classpath 'com.google.gms:google-services:4.3.4'
        classpath 'com.google.android.gms:strict-version-matcher-plugin:1.2.2'
        classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0'

distributionUrl=https\://services.gradle.org/distributions/gradle-5.6.4-all.zip

The problem

After trying to upgrade from Fabric Crashlytics to Firebase Crashlytics (published only that change), our users experienced very severe issue and here is the log:

java.lang.RuntimeException: 
  at android.app.ActivityThread.handleCreateService (http://ActivityThread.java:4096)
  at android.app.ActivityThread.access$1900 (http://ActivityThread.java:232)
  at android.app.ActivityThread$H.handleMessage (http://ActivityThread.java:1982)
  at android.os.Handler.dispatchMessage (http://Handler.java:107)
  at android.os.Looper.loop (http://Looper.java:214)
  at android.app.ActivityThread.main (http://ActivityThread.java:7710)
  at java.lang.reflect.Method.invoke (Native Method)
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (http://RuntimeInit.java:516)
  at com.android.internal.os.ZygoteInit.main (http://ZygoteInit.java:950)
Caused by: java.lang.IllegalStateException: 
  at android.os.Parcel.createException (http://Parcel.java:2079)
  at android.os.Parcel.readException (http://Parcel.java:2039)
  at android.os.Parcel.readException (http://Parcel.java:1987)
  at android.app.IActivityManager$Stub$Proxy.registerReceiver (http://IActivityManager.java:4860)
  at android.app.ContextImpl.registerReceiverInternal (http://ContextImpl.java:1561)
  at android.app.ContextImpl.registerReceiver (http://ContextImpl.java:1512)
  at android.app.ContextImpl.registerReceiver (http://ContextImpl.java:1500)
  at android.content.ContextWrapper.registerReceiver (http://ContextWrapper.java:627)
  at ule.android.cbc.ca.listenandroid.notification.MediaNotification.registerNotificationReceiver (http://MediaNotification.java:191)
  at ule.android.cbc.ca.listenandroid.services.MediaService.onCreate (http://MediaService.java:318)
  at android.app.ActivityThread.handleCreateService (http://ActivityThread.java:4084)
Caused by: android.os.RemoteException: 
  at com.android.server.am.ActivityManagerService.registerReceiver (http://ActivityManagerService.java:15759)
  at android.app.IActivityManager$Stub.onTransact (http://IActivityManager.java:1923)
  at com.android.server.am.ActivityManagerService.onTransact (http://ActivityManagerService.java:3021)
  at android.os.Binder.execTransactInternal (http://Binder.java:1032)
  at android.os.Binder.execTransact (http://Binder.java:1005)

It only happens to a certain percentage of our users, but the ones who have it it's super severe (on 10 users we have about 70 crashes). That low percentage ends up being very big, since our overall audience number is around 250K.

Also a thing to note, it only happens on specific devices like: LG, Xiaomi, OnePlus,.. Never on Google Pixel.

Steps to reproduce

We actually only know this happens in the background. We're currently in the process of acquiring more devices so we can try to reproduce it, but on our devices this has never happened.

[google-oss-bot]

I found a few problems with this issue:

• I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
• This issue does not seem to follow the issue template. Make sure you provide all the required information.

[mrober]

This fix will be live in the next release.