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)

Don't think it's just related to the internet permission. I'm getting exactly the same stack trace in my app and it (a) has the internet permission defined and working fine and (b) the webview was showing a local file in the assets folder.

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

Don't know if it is also related, but I also got an obscure message a little later:

D/chromium(2735): Unknown chromium error: -6

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

"D/chromium(2735): Unknown chromium error: -6" is actually a 404 (i.e. a URL that wasn't found or was a virtual URL ("my://custom/url") or something). Implementing WebViewClient.shouldInterceptRequest() will make that error go away, but given that there's a thread local memory leak when using that (

http://code.google.com/p/android/issues/detail?id=21355) I wouldn't advise doing that.

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

Thanks for that comment - I was just deploying another version of my app to test that!

I noticed one of the images in the assets folder had a space in the filename. Looks like sdk < 14 never complained about the spaces and happily found and rendered the image. Sdk 14 is a bit more picky - I renamed the file and no longer get the -6 error. But I'm still getting the same removeMessages(...107) stacktrace when I view a local asset file.

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

It looks like it was a major WebKit upgrade (hooray!) which is unfortunately quite buggy (CSS 3d transforms throw errors (

http://code.google.com/p/android/issues/detail?id=21305) , memory leaks, ability to have it core dump quiet easily (

http://code.google.com/p/android/issues/detail?id=21266), etc).

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

Marked as fixed.

I am running into this same error.

I have the internet permission set up, and in my case, I open custom HTML that points to an external flash player.

The flash player works great, until I go fullscreen. Once I enter fullscreen mode and back out, every time I attempt to re-open the webview I get this same problem.

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

I was getting the same error in my application, however i think my issue is a developer error. In order to explain how i got this issue, ill describe what i did. I'm creating an Android application which is loading and running a GWT compiled JavaScript application into a WebView. I looked around for many different things until i realized that my problem was in my own WebViewClient class. I had my class implemented as follows:

private static class HelloWebViewClient extends WebViewClient
{
@Override
public boolean shouldOverrideUrlLoading( WebView view, String url )
{
view.loadUrl( url );
return true;
}
}

This quickly caused the above exception to manifest. I changed the above line to being the following:

private static class HelloWebViewClient extends WebViewClient
{
@Override
public boolean shouldOverrideUrlLoading( WebView view, String url )
{
return false;
}
}

And POOF! no more error. I can't say I can actually explain what I did wrong. But im sure if i dug a bit more, i'd find the problem. But for now, I'm happy that it works. I hope this is useful to someone :)

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

Any Solution on this issue I am still getting the same error..

I have tried with
private static class HelloWebViewClient extends WebViewClient
{
@Override
public boolean shouldOverrideUrlLoading( WebView view, String url )
{
return false;
}
}

but no solution

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

I discovered something.

I used to have a webview as "about page": placed into my assets/ directory as .html

A javascript there was reading url parameters and using them to write my application name and setting.

So the url opened was something like this:

file:///android_asset/about.html?title=MyAppTitle&version=0.6.0

Android 14 and greater are looking for a file named "about.html?title=MyAppTitle&version=0.6.0"

you have similar issues with spaces in name file.

It's an issue in resolving the filename, the new version is not smart enough to understand "?stuff" is a query string, until SDK 13 android resolved it correctly, since 14 it look for a file named like that...

Question for Android developers: assuming this will be fixed, will it be backported to every device as an OTA firmware update? or will we always had to support both buggish and non-buggish versions to support every device?

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

Comment 3 is on point. This issue is actually a 404. The URL that's being pointed to has an issue. Modify the URL

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

Comment 10 is not on point. Synthetic URLs should always be valid (i.e. that's one way of launching other apps via Intents...like market urls :-)

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

I'm seeing this issue in API 15 as well.
There seems to be a number of different reasons that shows up with the very same error message.