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)

The issue turns out to be a problem with how the requestFocus() was being called. in updateFocusRectInWindowSnapshot, there is a check for isFocused that should also consider hasFocus(). The line should be changed from:

    if (!view.isFocused) {

        if (!view.isFocused && !view.hasFocus()) {

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

Resolved the original issues by using the correct rect value. However the focus shouldn't skip focus even with incorrect value. re-open the issue for investigation purpose. Thank you!

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

Project: platform/frameworks/support
Branch: androidx-main
Author: George Mount <mount@google.com>
Link: https://android-review.googlesource.com/3447394

Fix requestFocus with bad previous rectangle

Expand for full commit details

Fix requestFocus with bad previous rectangle 
 
Fixes: 388590015 
 
When requestFocus() is called on a ComposeView with a previousRect 
set to something that doesn't make sense (empty rectangle from the 
wrong direction, for example), the previous behavior would not 
find a matching component in that direction. Instead, it would 
find the next View to focus on and pass the focus on. 
 
With this CL, if the ComposeView isn't currently focused and a 
focusSearch fails to find something focusable in relation to the 
previous rectangle, an attempt is made irrespective of the 
previous rectangle. 
 
Relnote: "Fixed focus issue where requestFocus() with a 
nonsensical previouslyFocusedRect parameter (related to 
the focus direction) would skip past a ComposeView." 
 
Test: new test, manual testing 
Change-Id: Ifdc2f17b23620d1ae14848624f447f84cc1b0b5d

Files:

M compose/ui/ui/src/androidInstrumentedTest/kotlin/androidx/compose/ui/focus/RequestFocusTest.kt
M compose/ui/ui/src/androidMain/kotlin/androidx/compose/ui/platform/AndroidComposeView.android.kt

Hash: 8501eec732d61bd71c385a90f58a194191816d57
Date: Fri Jan 10 11:04:59 2025

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

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.compose.ui:ui-android:1.8.0-beta01
androidx.compose.ui:ui-jvmstubs:1.8.0-beta01
androidx.compose.ui:ui-linuxx64stubs:1.8.0-beta01

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

We didn't finalize the version number and will share the version number when it is released. This fix is on priority and will be released in next release.

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

Marked as fixed.

The fix is available to public. Client apps should update to 16.0.1 or newer to get the fix.
Release notes:

https://developers.google.com/cast/docs/release-notes#august-2-2018

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

Thanks.

Will be testing this on my next beta. What is the difference between com.google.android.gms:play-services-cast and com.google.android.gms:play-services-cast-framework? I don't see com.google.android.gms:play-services-cast-framework on this page

https://developers.google.com/android/guides/setup

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

Thanks for the update. com.google.android.gms:play-services-cast is a basic library for Google Cast and com.google.android.gms:play-services-cast-framework is a CAF sender framework library.

Comment #8

document seems to be an ancient page and we didn't update with new library. However, we are actively updating below document

https://developers.google.com/cast/docs/android_sender_setup

We created a new internal bug to update

comment #8

document and will be available in future.

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

Thanks for the clarification. So far this issue appears to be fixed at least with my beta users.

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

Thanks for the continuous updates. Let us know if you need any other details.

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

My google play server will not update have clears cookie done everything keep getting error 504 will not down load update

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

I have hackers from thawte wells Fargo spectrum PCH Wells Fargo GMBH Defense Department wiki net gear and Symantec that have taken my full identity and bank account info and they have attached their info to my HD because I deleted apps and turned off trusted crudentials. Now they control all of my devices illegally and apps as well as all settings and illegally recording video and sound in my own home. They have taken all personal info including pictures for identity and followed me through Google maps, I caught some of these people stealing my personal postal mail after following me. They have hack my my Alaska account which is taxes Alaska permit found dividends and unemployment I can't not access at all for about 3 years now. I've reported several times to vital statistics FBI and local police departments. Now they are in every email and online account taking and or deleting my personal emails. Taking full reports of everything on my devices illegally and using my identity as well as controlling everything on it.

Sent from my Galaxy Tab® A