Fatal Exception: java.lang.IllegalStateException: GoogleApiClient is not connected yet. [79783005]

Fixed

Bug

Status Update

No update yet.

Description

ca...@instantbits.com

created issue #1

May 16, 2018 04:34PM

I've started receiving this crash under crashlytics since upgrading to Cast SDK 3. I don't know how to reproduce it, it has never happened to me. I'm guessing I'm doing something wrong, but I don't see any of my code on the stacktrace. How can I figure out where the issue is?

Which version of the Cast SDK are you using? Cast SDK 3 - I'm targeting Google Play Services 15

Fatal Exception: java.lang.IllegalStateException: GoogleApiClient is not connected yet.
at com.google.android.gms.common.api.internal.zzaj.execute(Unknown Source)
at com.google.android.gms.common.api.internal.zzbd.execute(Unknown Source)
at com.google.android.gms.common.api.internal.zzav.execute(Unknown Source)
at com.google.android.gms.cast.Cast$CastApi$zza.sendMessage(Unknown Source)
at com.google.android.gms.cast.framework.media.RemoteMediaClient$zza.zza(Unknown Source)
at com.google.android.gms.internal.cast.zzcm.zza(Unknown Source)
at com.google.android.gms.internal.cast.zzdh.zza(Unknown Source)
at com.google.android.gms.internal.cast.zzdh.zzda(Unknown Source)
at com.google.android.gms.internal.cast.zzdh.zza(Unknown Source)
at com.google.android.gms.internal.cast.zzdi.zza(Unknown Source)
at com.google.android.gms.internal.cast.zzdn.zza(Unknown Source)
at com.google.android.gms.internal.cast.zzdn.zza(Unknown Source)
at com.google.android.gms.internal.cast.zzdn.zzdc(Unknown Source)
at com.google.android.gms.internal.cast.zzdo.run(Unknown Source)
at android.os.Handler.handleCallback(Handler.java:751)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:241)
at android.app.ActivityThread.main(ActivityThread.java:6274)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)

Comments

sy...@google.com <sy...@google.com> #2May 17, 2018 11:11PM

Status: Won't Fix (Obsolete)

A link to another sample project demonstrating that the leak only happens when using: LocationServices.FusedLocationApi.requestLocationUpdates but does not happen using a deprecated method: googleMap.setOnMyLocationChangeListener.

https://github.com/fernandospr/android-maps-userlocation

[Deleted User] <[Deleted User]> #3Jun 12, 2018 10:08AM

Hello, I'm also experiencing the memory leak in my activity responsible for the location service.

The implementation of my project is not different from the example project attached by fernando.

sy...@google.com <sy...@google.com> Jul 3, 2018 06:02PM

Status: Assigned (reopened)

sy...@google.com <sy...@google.com> #4Jul 30, 2018 09:07PM

FYI this memory leak also seems to exist when using the new FusedLocationProviderClient. I took Fernano's sample from

comment #2

and hacked it up to use the FusedLocationProviderClient and was still able to observe the leak upon exiting the activity.

ca...@instantbits.com <ca...@instantbits.com> #5Jul 30, 2018 09:10PM

Leak still present in 2019 on latest play-services-location 16.0.0. 3+ years since first reported via linked Github issue, no fix or hint of acknowledgment. Clown college grade software engineering.

sy...@google.com <sy...@google.com> #6Jul 30, 2018 09:17PM

I am also still experiencing this!

sy...@google.com <sy...@google.com> #7Aug 2, 2018 10:36PM

Marked as fixed.

Still present in 'com.google.android.gms:play-services-location:17.0.0'

As an alternative I am using FusedLocationProviderClient with PendingIntent:

IntentFilter intentFilter = new IntentFilter(ACTION_LOCATION);
registerReceiver(locationReceiver, intentFilter);
mFusedLocationClient.requestLocationUpdates(mLocationRequest, locationPendingIntent);
and
unregisterReceiver(locationReceiver);
mFusedLocationClient.removeLocationUpdates(locationPendingIntent)

Here is forked LocationUpdates repo with LeakCanary installed and an option to switch between LocationCallback and PendingIntent. LeakCanary not reporting anything when using PendingIntent.

https://github.com/dejandobnikar/location-samples/tree/master/LocationUpdates

ca...@instantbits.com <ca...@instantbits.com> #8Aug 3, 2018 06:07PM

Thank you for your feedback. We assure you that we are doing our best to address all issues reported. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with the bug report here

https://goo.gl/TbMiIO and reference this bug for context.

sy...@google.com <sy...@google.com> #9Aug 4, 2018 12:15AM

Comment #8

, the one thing that would matter to address is how to *actually* get this issue fixed. It appears pointless to file a new issue, and unclear where to do so, as this issue has not received attention from Google's side throughout the years despite quite a few people starring it and bug reports in different places. The continued existence of the bug was confirmed not long ago in prior comments by different people. I've just confirmed it again myself on R Beta 3.

ca...@instantbits.com <ca...@instantbits.com> #10Aug 6, 2018 01:37PM

According to some Google DevRel it might soon be fixed, see the answer (from 8 days ago) here:

https://github.com/googlecodelabs/while-in-use-location/issues/7

sy...@google.com <sy...@google.com> #11Aug 6, 2018 06:30PM

This issue still exists, how can this be prioritized?

re...@gmail.com <re...@gmail.com> #12Aug 8, 2018 10:51AM

There is an issuetracker Component available these days for Play Services Location: https://issuetracker.google.com/components/1065160

Maybe move this issue to that Component to track it better?

bu...@gmail.com <bu...@gmail.com> #13Sep 8, 2018 12:49PM

I can't move it right now, but I think it's ok to stay here.

As I wrote in the code lab issue, I misunderstood when the rewrite went out (which should fix the issue).

It goes live in version 20 (current version location 19.0.1). The engineer who wrote the rewrite checked and wasn't seeing the same issue, i.e., it should be resolved.

However, that does mean we have to wait until 20 is released. I can check in again here when it's live for you to double check.