Beware of this SDK.
It seems that google stopped supporting the C++ version of their GPG.
I reported some issues, including one critical, last April and they didn’t fix them yet.
No answer from them… makes me think they’ll soon drop the dev of that sdk (and as it’s based on google+ for the login, I can’t blame them).
Just saying.
ohh, I was thinking that it is actively developed as we used 1.3… 1.4 version and now it is 2.0.
And it’s implementation is more suitable for C++ Cocos2d-x.
btw. I think all google products not fixed in time… they just ignore everyone
Version 2.0
What’s new?
Also change log saying that probably they moving forward with development…
Authentication on iOS now uses the Google Sign-in SDK instead of the Google+ SDK. Among other benefits, this allows developers more flexibility and control over the initial sign-in redirect process, including the ability to redirect sign-in to an in-app webview.
The SDK now supports the arm64-v8a ABI.
LeaderboardManager().ShowUI() now allows selection of a default time span, using an optional LeaderboardTimeSpan parameter.
An important compatibility fix allows use of the newest versions of the Google Play Game Services client library on Android.
Oh well, maybe they fully rewrote some of their base code and it’s not bugged anymore.
But well, I was tired waiting for them to fix their bug so I switched to another game service.
Well, I do hope they better “commit” than the past 6 months, because not even answering when someone gives reproduction steps using their own samples is kind of lame.
Let’s hope the new gpg sdk version has fixed all that nasty critical issues