You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having ANR reports from Google Play on some devices about time outs at auth stage with message like this:
"Input dispatching timed out (Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 2. Wait queue head age: 9899.7ms.)
com.ourgame.UnityPlayerActivity"
#00 pc 000000000001297c /system/lib/libc.so (syscall+28) #1 pc 00000000000a9af3 /system/lib/libart.so (art::ConditionVariable::Wait(art::Thread*)+82) #2 pc 000000000027cb75 /system/lib/libart.so (art::GoToRunnable(art::Thread*)+756) #3 pc 0000000000087739 /system/lib/libart.so (art::JniMethodEnd(unsigned int, art::Thread*)+8) #4 pc 0000000000cfcca1 /system/framework/arm/boot.oat (Java_android_os_BinderProxy_transactNative__ILandroid_os_Parcel_2Landroid_os_Parcel_2I+156)
at android.os.BinderProxy.transactNative (Native method)
at android.os.BinderProxy.transact (Binder.java:519)
at com.google.android.gms.internal.ahh.zzb (unavailable)
at com.google.android.gms.auth.api.signin.internal.u.a (unavailable)
at com.google.android.gms.auth.api.signin.internal.f.zza (unavailable)
at com.google.android.gms.common.api.internal.zzm.zzb (unavailable)
at com.google.android.gms.common.api.internal.zzal.zze (unavailable)
at com.google.android.gms.common.api.internal.zzal.zzd (unavailable)
at com.google.android.gms.common.api.internal.zzbi.zzd (unavailable)
at com.google.android.gms.common.api.internal.zzv.zzd (unavailable)
at com.google.android.gms.common.api.internal.zzba.zzd (unavailable)
at com.google.android.gms.auth.api.signin.internal.e.a (unavailable)
at com.google.android.gms.auth.api.signin.internal.c.b (unavailable)
at com.google.games.bridge.TokenFragment.onConnected (TokenFragment.java:516)
at com.google.android.gms.common.internal.zzae.zzk (unavailable)
locked <@addr=0x12df8290> (a java.lang.Object)
at com.google.android.gms.common.api.internal.zzba.zzj (unavailable)
at com.google.android.gms.common.api.internal.zzv.zzahl (unavailable)
at com.google.android.gms.common.api.internal.zzv.zzb (unavailable)
at com.google.android.gms.common.api.internal.zzy.zzj (unavailable)
at com.google.android.gms.common.api.internal.zzao.zzaie (unavailable)
at com.google.android.gms.common.api.internal.zzao.onConnected (unavailable)
at com.google.android.gms.common.api.internal.zzbi.onConnected (unavailable)
at com.google.android.gms.common.api.internal.zzt.onConnected (unavailable)
at com.google.android.gms.common.internal.zzac.onConnected (unavailable)
at com.google.android.gms.common.internal.zzn.zzakr (unavailable)
at com.google.android.gms.common.internal.zze.zzw (unavailable)
at com.google.android.gms.common.internal.zzi.zzaks (unavailable)
at com.google.android.gms.common.internal.zzh.handleMessage (unavailable)
at android.os.Handler.dispatchMessage (Handler.java:102)
at android.os.Looper.loop (Looper.java:135)
at android.app.ActivityThread.main (ActivityThread.java:5348)
at java.lang.reflect.Method.invoke! (Native method)
at java.lang.reflect.Method.invoke (Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:947)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:742)
Is it possible to prevent such behavior?
The text was updated successfully, but these errors were encountered:
Hello.
I'm having ANR reports from Google Play on some devices about time outs at auth stage with message like this:
"Input dispatching timed out (Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 2. Wait queue head age: 9899.7ms.)
com.ourgame.UnityPlayerActivity"
The reported callstack is:
"main" prio=5 tid=1 Native
| group="main" sCount=1 dsCount=0 obj=0x731e7ab0 self=0xb740a6f0
| sysTid=20232 nice=0 cgrp=default sched=0/0 handle=0xb6fddbec
| state=S schedstat=( 0 0 0 ) utm=255 stm=186 core=3 HZ=100
| stack=0xbe622000-0xbe624000 stackSize=8MB
| held mutexes=
Is it possible to prevent such behavior?
The text was updated successfully, but these errors were encountered: