java.lang.IllegalArgumentException: Service not registered: com.google.android.gms.measurement.internal.zzji@dbed45a

I have the following exception when FirebaseAnalytics.logEvent executes :

com.dreamtechs.MadfooatCom W/ConnectionTracker: Exception thrown while unbinding
 java.lang.IllegalArgumentException: Service not registered: com.google.android.gms.measurement.internal.zzji@dbed45a
        at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:1832)
        at android.app.ContextImpl.unbindService(ContextImpl.java:1880)
        at android.content.ContextWrapper.unbindService(ContextWrapper.java:741)
        at com.google.android.gms.common.stats.ConnectionTracker.zza(com.google.android.gms:play-services-basement@@17.3.0:55)
        at com.google.android.gms.common.stats.ConnectionTracker.unbindService(com.google.android.gms:play-services-basement@@17.3.0:50)
        at com.google.android.gms.measurement.internal.zzir.zzah(com.google.android.gms:play-services-measurement-impl@@17.4.3:251)
        at com.google.android.gms.measurement.internal.zzir.zzam(com.google.android.gms:play-services-measurement-impl@@17.4.3:268)
        at com.google.android.gms.measurement.internal.zzir.zzc(com.google.android.gms:play-services-measurement-impl@@17.4.3:335)
        at com.google.android.gms.measurement.internal.zziq.zza(com.google.android.gms:play-services-measurement-impl@@17.4.3:2)
        at com.google.android.gms.measurement.internal.zzaj.run(com.google.android.gms:play-services-measurement-impl@@17.4.3:7)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at com.google.android.gms.measurement.internal.zzfz.run(com.google.android.gms:play-services-measurement-impl@@17.4.3:21)

implementation 'com.google.android.gms:play-services-base:17.3.0'
implementation 'com.google.android.gms:play-services-basement:17.3.0'
implementation "com.google.android.gms:play-services-vision:20.1.0"
implementation "com.google.android.gms:play-services-places:17.0.0"
implementation "com.google.android.gms:play-services-location:17.0.0"
implementation "com.google.android.gms:play-services-auth:18.0.0"
implementation 'com.google.android.gms:play-services-gcm:17.0.0'
implementation 'com.google.android.gms:play-services-analytics:17.0.0'
implementation 'com.google.android.gms:play-services-auth-api-phone:17.4.0'


implementation "com.google.firebase:firebase-core:17.4.3"
implementation "com.google.firebase:firebase-messaging:20.2.0"
implementation "com.google.firebase:firebase-invites:17.0.0"
implementation "com.google.firebase:firebase-config:19.1.4"
implementation 'com.google.firebase:firebase-firestore:21.4.3'
implementation 'com.google.firebase:firebase-functions:19.0.2'
implementation 'com.google.firebase:firebase-crashlytics:17.0.1'
implementation 'com.google.firebase:firebase-analytics:17.4.3'

[vkryachko]

Hey folks,

As many of you have pointed out, it turns out that there exist some device configurations that trigger the warning even with the workaround I provided above.

Unfortunately there is nothing more we can do to “silence” the warning on the SDK side. The warning is caused by “Google Play Services” itself. The good news is that the root cause of the issue is now fixed, however it will roll out to devices around February, so we will have to live with this warning for a few months.

I understand that it is causing inconvenience for developers, but fwiw it’s a warning not a crash. So please bear with us till the update gets rolled out. Thanks

PS: Many of you have commented that this warning is sometimes followed by a crash(with its own exception), I am fairly confident that in most cases, the crash is completely unrelated to this warning and just so happens to occur right after it. So please investigate your crashes independently, just ignoring the warning. If however you think that the crash is related, please provide:

• full stack traces at the event of crash
• relevant dependencies of your app
• ideally steps to reproduce

[venator85]

Adding:

implementation 'com.google.android.gms:play-services-basement:17.4.0'

seems to solve the issue (the warning is no longer logged).