Bug Issue: android.gms.common.ConnectionResult.startResoluti - Crash reports in Googleplay

Pages: 1


  • Subscriber - Stencyl Studio
  • *
April 15, 2019, 11:32:12 am
I don't get this error, but been getting crash reports in googleplay. I think it has something to do with googleplay services, also in tandem with the error in this thread: http://community.stencyl.com/index.php?issue=1516.0
Code: [Select]
  at com.google.android.gms.common.ConnectionResult.startResolutionForResult (Unknown Source:19)
  at com.google.example.games.basegameutils.GameHelper.resolveConnectionResult (GameHelper.java:875)
  at com.google.example.games.basegameutils.GameHelper.onConnectionFailed (GameHelper.java:851)
  at com.google.android.gms.common.internal.zzm.zzo (Unknown Source:80)
  at com.google.android.gms.internal.zzaal.zzc (Unknown Source:25)
  at com.google.android.gms.internal.zzaaj.zzf (Unknown Source:22)
  at com.google.android.gms.internal.zzaaj.zzvB (Unknown Source:65)
  at com.google.android.gms.internal.zzaaj.zza (Unknown Source:11)
  at com.google.android.gms.internal.zzaan.zza (Unknown Source:7)
  at com.google.android.gms.internal.zzzy.onConnectionFailed (Unknown Source:9)
  at com.google.android.gms.common.internal.zzl$2.onConnectionFailed (Unknown Source:2)
  at com.google.android.gms.common.internal.zzf$zzj.zzn (Unknown Source:14)
  at com.google.android.gms.common.internal.zzf$zza.zzc (Unknown Source:41)
  at com.google.android.gms.common.internal.zzf$zza.zzu (Unknown Source:2)
  at com.google.android.gms.common.internal.zzf$zze.zzxa (Unknown Source:54)
  at com.google.android.gms.common.internal.zzf$zzd.handleMessage (Unknown Source:149)
  at android.os.Handler.dispatchMessage (Handler.java:109)
  at android.os.Looper.loop (Looper.java:207)
  at android.app.ActivityThread.main (ActivityThread.java:7536)
  at java.lang.reflect.Method.invoke (Native Method)
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:524)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:958)

Been getting in touch with google and this error along side the error from the other thread has been raising my android crash rate above the threshold and they want it fixed before they consider any features.

Much help appreciated.
« Last Edit: April 15, 2019, 12:09:09 pm by Raiyumi »


  • Master Stencyler
  • *
June 29, 2019, 02:05:33 am
I added some code about a month ago which should at least prevent this from crashing.


However, I'm not sure what actually causes the code to get to that state, or if there might not be something else causing an issue earlier on.


  • Master Stencyler
  • *
August 08, 2023, 11:00:40 pm
I'll tentatively mark this old issue as resolved since there've been no updates since I made my change.
  • Status changed from New to Resolved

Pages: 1


  • Reported
    April 15, 2019, 11:32:12 am
  • Updated
    August 08, 2023, 11:00:40 pm

  • View Status
  • Type
  • Status
  • Priority
  • Version
    Stencyl 3.5, 3.5.0 beta 1
  • Fixed in
  • Assigned to
  • Category