Makes sense. I added a lot of null checks. Now null values should just be ignored. Please, make a new build and see if you can reproduce a bug again.
First test.
Build with corona 2019.3473.
Retrieving saved data from snapshots doesn’t work any more.
vlads whatever you did broke the plugin even more!
gpgs.snapshots.open fails completely. Doesn’t even get to the listener parameter.
On the other hand log in reminds more the gpgs ver 1 and I like it.
Every time you install or delete app’s data the welcome message and choose account message both appear.
In gpgs version 2 it happens only the first ever time you install an application.
Any details? Is there any output when you fail to load a game? “everything is broken” doesn’t really help.
I’m off work right now.
Later I will get some logs.
I made the post because it’s really serious.
gpgs.snapshots.open listener paramerter doesn’t work and you can’t get your saved snapshots.
local function gpgsSnapshotOpenForReadListener( event ) print( "snapshot open event:", json.prettify(event) ) if not event.isError then local data = event.snapshot.contents.read() native.showAlert('Snapshots', 'Reading was ' .. (event.isError and 'unsuccessful' or 'successful') .. ',', { 'OK'}) end end function myData.openSnapshot() print("Opening snapshot") myData.gpgs.snapshots.open({ filename = snapshotFilename, create = true, listener = gpgsSnapshotOpenForReadListener }) end
gpgsSnapshotOpenForReadListener doesn’t get called.
Imho you should check it soon.
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.