What would be helpful is to have some debugging information on why GPGS isn’t working. “It’s broke. Fix it” isn’t very helpful, in particular with really big plugins like GPGS. What would be a lot more helpful is a sample project with your code in it (complete with build.settings and config.lua) and a capture of an “adb logcat” sessions looking for errors from Google about why it’s not working. It’s really hard to speculate as to why something isn’t working for you.
The plugin is being updated to use a new GPGS library that gets away from using Google Plus to log in. Hopefully, this will contain updates that address other potential bugs, but we won’t know for certain unless we know what the specific issue is.
BTW: The new version of the plugin is a 100% rewrite of the old plugin. Every node had to be touched. This has taken a significant amount of time to do. I’m hoping that everything stayed call-compatible, but that’s why we need to do a lot of testing on it before we release it.
@genelixis we are aware of the current problem with building for Android when plugins are involved and our team is looking into the issue.
As far as the GPGS plugin goes, I can’t really answer that. I don’t have apps that use snapshots and I haven’t had a chance to do my own personal tests against that API node. Given it’s a complete rewrite of the plugin, I would hope you plan on running a full battery of testing against a beta plugin to make sure it works for you. We can’t test every use case, which is why we put these out as beta so we can collect information from a wider range of use cases.