2019.3474 has issue with gpgs version 2.
Just build with 2019.3468 and it works ok.
I reverted changes in my latest null check commit. It would take some work to get a proper fix for crashes. I’m working on it.
Thank you vlads.
I hope it won’t take too long.
Please let me know when it’s done and I will test it asap.
Don’t know if it’s gonna help but today I got a user review saying that crashes, (playing the live app downloaded from play store) have stopped. I haven’t changed anything and the app was updated on Saturday.
Also, the past days, working with a user who has that problem (I can’t reproduce the crash in my devices) eventually had crashes although we created new filenames for the snapshots (using all the parameters this time).
Hello! I deployed new version of the plugin. It should ignore null fields and snapshots should still work. Please, give it a try.
I’m leaving for a meeting with a client.
I will check it the moment I come back to the office!
Same problem.
gpgs.snapshots.open crashes the app.
One of the users with a device that crashes (who contacted with me) hadn’t install the app before.
Maybe what you did was correct but there is something else too.
I would need new crash logs to figure out what is going wrong.
That’s hard to do since I can’t reproduce the crash in my devices.
I will try my best to get logs and post them here.
gpgs version 2 is a complete disaster.
I will update some apps and I hope I will not get the same crash again.
Find a user who has a bug, add him to beta, get crash logs. It is very hard to debug an issue which you can’t show how to reproduce.
Beta testing is open only can’t choose specific user, only the maximum number.
I will create an alpha release and invite users who experience the crashes.
Please, make a new build. I fixed some bugs. I didn’t work on this plugin before, let’s try to make it better. I think it should be working fine now, I don’t see any issues with my test project.
Same crash 
I’m waiting for crash logs of alpha version.
I had another alpha for personal testing, on May, without errors in pre-launch report.
I haven’t changed my code but this time in pre-launch report, in test results I get this:
9 devices without issues, 1 device with issues
device K3 2017 (LGE)
android: 6.0
3 issues identified
FATAL EXCEPTION: main Process: com.android.vending, PID: 21275 java.lang.OutOfMemoryError: OutOfMemoryError thrown while trying to throw OutOfMemoryError; no stack trace available
2
FATAL EXCEPTION: Db-notification\_cache Process: com.android.vending, PID: 21887 java.lang.IllegalMonitorStateException at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:123) at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1235) at java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:429) at java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:442) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1037) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1098) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588) at ifo.run(Unknown Source) at java.lang.Thread.run(Thread.java:818)
3
FATAL EXCEPTION: pool-2-thread-1 Process: com.android.vending, PID: 22837 java.lang.OutOfMemoryError: Failed to allocate a 34 byte allocation with 96 free bytes and 96B until OOM at java.lang.StringFactory.newStringFromChars(Native Method) at java.lang.IntegralToString.convertInt(IntegralToString.java:246) at java.lang.IntegralToString.intToString(IntegralToString.java:166) at java.lang.Integer.toString(Integer.java:487) at java.lang.Integer.toString(Integer.java:474) at com.android.internal.util.XmlUtils.writeValueXml(XmlUtils.java:717) at com.android.internal.util.XmlUtils.writeMapXml(XmlUtils.java:300) at com.android.internal.util.XmlUtils.writeMapXml(XmlUtils.java:269) at com.android.internal.util.XmlUtils.writeMapXml(XmlUtils.java:235) at com.android.internal.util.XmlUtils.writeMapXml(XmlUtils.java:192) at android.app.SharedPreferencesImpl.writeToFile(SharedPreferencesImpl.java:600) at android.app.SharedPreferencesImpl.access$800(SharedPreferencesImpl.java:52) at android.app.SharedPreferencesImpl$2.run(SharedPreferencesImpl.java:515) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588) at java.lang.Thread.run(Thread.java:818)Also, having no issues in your test project means nothing.
I can’t reproduce the error in my devices either. 
That chats have seems unrelated - out of memory.
Yes, I’m waiting for the crash logs.
Crash logs.
Samsung Galaxy Note 9, android 9
com.google.android.gms.tasks.RuntimeExecutionException: at com.google.android.gms.tasks.zzu.getResult (Unknown Source:17) at plugin.gpgs.v2.Snapshots$11.onComplete (Snapshots.java:260) at com.google.android.gms.tasks.zzj.run (Unknown Source:23) at android.os.Handler.handleCallback (Handler.java:873) at android.os.Handler.dispatchMessage (Handler.java:99) at android.os.Looper.loop (Looper.java:214) at android.app.ActivityThread.main (ActivityThread.java:6981) 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:1445) Caused by: com.google.android.gms.common.api.ApiException: at com.google.android.gms.common.internal.ApiExceptionUtil.fromStatus (Unknown Source:14) at com.google.android.gms.games.internal.zzi.zza (Unknown Source:26) at com.google.android.gms.games.internal.zzk.onComplete (Unknown Source:6) at com.google.android.gms.common.api.internal.BasePendingResult.zza (Unknown Source:46) at com.google.android.gms.common.api.internal.BasePendingResult.setResult (Unknown Source:42) at com.google.android.gms.common.api.internal.BaseImplementation$ApiMethodImpl.setFailedResult (Unknown Source:17) at com.google.android.gms.common.api.internal.zzd.zza (Unknown Source:64) at com.google.android.gms.common.api.internal.zzd.zza (Unknown Source:11) at com.google.android.gms.common.api.internal.GoogleApiManager$zza.zzc (Unknown Source:9) at com.google.android.gms.common.api.internal.GoogleApiManager$zza.zzb (Unknown Source:4) at com.google.android.gms.common.api.internal.GoogleApiManager$zza.zzbl (Unknown Source:33) at com.google.android.gms.common.api.internal.GoogleApiManager$zza.zzbj (Unknown Source:56) at com.google.android.gms.common.api.internal.GoogleApiManager$zza.onConnected (Unknown Source:16) at com.google.android.gms.common.internal.zzf.onConnected (Unknown Source:2) at com.google.android.gms.common.internal.BaseGmsClient$PostInitCallback.handleServiceSuccess (Unknown Source:148) at com.google.android.gms.common.internal.BaseGmsClient$zza.deliverCallback (Unknown Source:46) at com.google.android.gms.common.internal.BaseGmsClient$zza.deliverCallback (Unknown Source:2) at com.google.android.gms.common.internal.BaseGmsClient$CallbackProxy.deliverCallback (Unknown Source:57) at com.google.android.gms.common.internal.BaseGmsClient$zzb.handleMessage (Unknown Source:275) at android.os.Handler.dispatchMessage (Handler.java:106) at android.os.Looper.loop (Looper.java:214) at android.os.HandlerThread.run (HandlerThread.java:65)Actually, this is snapshot.save() function crashing now when failing to save. I fixed the crash, but it would still fail (not it will send proper save failed message instead of the crash).
more crash logs.
samsung galaxy j5 (2016)
java.lang.NullPointerException: at com.ansca.corona.CoronaActivity.getOverlayView (CoronaActivity.java:997) at plugin.gpgs.v2.Connector$1.run (Connector.java:79) at android.os.Handler.handleCallback (Handler.java:751) at android.os.Handler.dispatchMessage (Handler.java:95) at android.os.Looper.loop (Looper.java:154) at android.app.ActivityThread.main (ActivityThread.java:6816) at java.lang.reflect.Method.invoke (Native Method) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1563) at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1451)
also this keeps coming
samsung galaxy s9+
java.lang.NullPointerException: at plugin.gpgs.v2.Utils.gameToHashtable (Utils.java:285) at plugin.gpgs.v2.Utils.snapshotMetadataToHashtable (Utils.java:306) at plugin.gpgs.v2.Snapshots$OpenSnapshotOnCompleteListener.onComplete (Snapshots.java:503) at com.google.android.gms.tasks.zzj.run (Unknown Source:23) at android.os.Handler.handleCallback (Handler.java:873) at android.os.Handler.dispatchMessage (Handler.java:99) at android.os.Looper.loop (Looper.java:214) at android.app.ActivityThread.main (ActivityThread.java:6981) 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:1445)
Vlad I really appreciate your efforts and thank you for helping us.
In several of our apps we have a few hundred of affected devices and users try again and again and again to launch the app after crash.
Because of that we see thousands of crashes and losing many potential customers.
That’s really frustrating for us.
It’s so hard to have successful apps and that kind of crashes affects the downloads and the reputation.
I hope there will be a solution for every crash soon.