Sudden massive increase in crashes on live version

[adbourdages]

I know that Google Play Games is having a hard time right now due to a recent update and this may be related to that.

On my Play console crash report there has been a major uptick of crashes. Here's an example stack trace. Unfortunately it is obfuscated.

at android.os.Parcel.createException (Parcel.java:1978) at android.os.Parcel.readException (Parcel.java:1935) at android.os.Parcel.readException (Parcel.java:1885) at com.google.android.gms.internal.games.zza.transactAndReadExceptionReturnVoid (Unknown Source:10) at com.google.android.gms.games.internal.zzz.zza (Unknown Source:12) at com.google.android.gms.games.internal.zze.zza (Unknown Source:12) at com.google.android.gms.games.internal.zzac.zzbj (Unknown Source:12) at com.google.android.gms.games.internal.zzaf.zzbj (Unknown Source:6) at com.google.android.gms.games.internal.zze.onConnectedLocked (Unknown Source:11) at com.google.android.gms.common.internal.BaseGmsClient.zza (Unknown Source:113) at com.google.android.gms.common.internal.BaseGmsClient.zza (Unknown Source:129) at com.google.android.gms.common.internal.BaseGmsClient.zza (Unknown Source:354) at com.google.android.gms.common.internal.BaseGmsClient$zzf.zzm (Unknown Source:19) at com.google.android.gms.common.internal.BaseGmsClient$zza.zza (Unknown Source:12) at com.google.android.gms.common.internal.BaseGmsClient$zzc.zzo (Unknown Source:11) at com.google.android.gms.common.internal.BaseGmsClient$zzb.handleMessage (Unknown Source:49) at android.os.Handler.dispatchMessage (Handler.java:106) at com.google.android.gms.internal.common.zze.dispatchMessage (Unknown Source:7) at android.os.Looper.loop (Looper.java:280) at android.app.ActivityThread.main (ActivityThread.java:6706) at java.lang.reflect.Method.invoke (Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:493) at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:858)

[PickleJesus123]

I am getting the same crashes. I went from 7 crashes per 1000 devices, to 800 crashes per 1000 devices. It is causing my organic growth to disappear in the Play Store.

[adbourdages]

I think the number of crash has peaked - at leas in my case. I see it being the worst around December 15th and then dropping. I'm also getting way less support emails as well for issues with Google Play Games. Looks like the update to Play Games app has made it to most players.

Your numbers (800 per 1000) are crazy. I hope you are seeing the same drop I have. As for these bugs here, I hope that the code gets ironed out against the same happening in the future.

[PickleJesus123]

The crash rate is booming again for me. It appeared to peak and drop for a few days, and then it shot up even higher. I am now in the "bad behaviour threshold" thanks to this shoddy update from Google, and my livelihood is now at stake. Went from 3000 installs/day to 0 installs per day. Currently removing Google Play services from my app permanently.

[yome]

This hit us hard too.

We pushed an update disabling the auto-login to Google Play Games and it seems to work around the issue. Things are slowly going back to normal but damage was done.

[PickleJesus123]

This hit us hard too. We pushed an update disabling the auto-login to Google Play Games and it seems to work around the issue. Things are slowly going back to normal but damage was done.

Did you update to Unity 2019.3.0f3 as well? I couldn't tell at first if it was GPGS or Unity

[yome]

We didn't update Unity. The particular game that was affected is on Unity 2018.4.11f1.

[PickleJesus123]

We didn't update Unity. The particular game that was affected is on Unity 2018.4.11f1

Thanks for the reply. Good to know that it's this Google plugin specifically causing the crashes. Hopefully my app can recover now that Google Play Services has been removed entirely. Either that, or my app is dead now.

[ozdemir08]

I know that Google Play Games is having a hard time right now due to a recent update and this may be related to that.

On my Play console crash report there has been a major uptick of crashes. Here's an example stack trace. Unfortunately it is obfuscated.

at android.os.Parcel.createException (Parcel.java:1978) at android.os.Parcel.readException (Parcel.java:1935) at android.os.Parcel.readException (Parcel.java:1885) at com.google.android.gms.internal.games.zza.transactAndReadExceptionReturnVoid (Unknown Source:10) at com.google.android.gms.games.internal.zzz.zza (Unknown Source:12) at com.google.android.gms.games.internal.zze.zza (Unknown Source:12) at com.google.android.gms.games.internal.zzac.zzbj (Unknown Source:12) at com.google.android.gms.games.internal.zzaf.zzbj (Unknown Source:6) at com.google.android.gms.games.internal.zze.onConnectedLocked (Unknown Source:11) at com.google.android.gms.common.internal.BaseGmsClient.zza (Unknown Source:113) at com.google.android.gms.common.internal.BaseGmsClient.zza (Unknown Source:129) at com.google.android.gms.common.internal.BaseGmsClient.zza (Unknown Source:354) at com.google.android.gms.common.internal.BaseGmsClient$zzf.zzm (Unknown Source:19) at com.google.android.gms.common.internal.BaseGmsClient$zza.zza (Unknown Source:12) at com.google.android.gms.common.internal.BaseGmsClient$zzc.zzo (Unknown Source:11) at com.google.android.gms.common.internal.BaseGmsClient$zzb.handleMessage (Unknown Source:49) at android.os.Handler.dispatchMessage (Handler.java:106) at com.google.android.gms.internal.common.zze.dispatchMessage (Unknown Source:7) at android.os.Looper.loop (Looper.java:280) at android.app.ActivityThread.main (ActivityThread.java:6706) at java.lang.reflect.Method.invoke (Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:493) at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:858)

Have your crash numbers come back to normal? Also, what version of this plugin are you using? I guess this stack trace is related to the sign in issue we had but I'll deobfuscate it to be sure that it's not something else if you let me know the plugin version you're using.

[PickleJesus123]

My crash rate is no longer 800 per 1000, and it has fell to 18 per 1000 which is still unacceptably high (since the "bad behaviour threshold is 11 per 1000). I previously had 5.5 crashes per 1000 in the past.

As of right now my production version is using unity 2019.3.0f4 with the latest IAP imported, and Google Mobile Ads plugin v3.18.3. I removed Google Play Services entirely, and also removed Chartboost Mediated ads and UnityAds mediated ads, and have mediation paused on my Admob console.

The bugged out version was using unity 2019.3.0f3, with the latest PlayGamesServices and the latest Admob. The chartboost and Unityads were from April though.

Before the crashes started happening (when my app was a-ok), I had Unity 2019.2.13f1 and Admob v3.18.2 plugin, with Unityads mediated ads and Chartboost mediated ads from April

During the death of my app in the play store, most of my errors were

java.lang.Error: FATAL EXCEPTION [main] Unity version : 2019.3.0f3 Device model : HUAWEI DRA-LX2 Caused by at com.moat.analytics.mobile.cha.n.ͺ (SourceFile:5303) at com.moat.analytics.mobile.cha.n.ʽ (SourceFile:178) at com.moat.analytics.mobile.cha.n.ˎ (SourceFile:144) at com.moat.analytics.mobile.cha.n. (SourceFile:81) at com.moat.analytics.mobile.cha.n.ˏ (SourceFile:63) at com.moat.analytics.mobile.cha.f.ˎ (SourceFile:108) at com.moat.analytics.mobile.cha.t$2$2.ˏ (SourceFile:135) at com.moat.analytics.mobile.cha.t$d$5.run (SourceFile:245) at android.os.Handler.handleCallback (Handler.java:795) at android.os.Handler.dispatchMessage (Handler.java:99) at android.os.Looper.loop (Looper.java:166) at android.app.ActivityThread.main (ActivityThread.java:6861) at java.lang.reflect.Method.invoke (Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:450) at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:936) Caused by: java.lang.ClassNotFoundException: at dalvik.system.BaseDexClassLoader.findClass (BaseDexClassLoader.java:125) at java.lang.ClassLoader.loadClass (ClassLoader.java:379) at java.lang.ClassLoader.loadClass (ClassLoader.java:312)

[ozdemir08]

We encountered a bug affecting sign-in and have pushed out a fix with Play Games. Thank you to everyone that brought it to our attention and we apologize for any inconvenience caused.