I’ve got Migrate from legacy Google Sign-In to Credential Manager and AuthorizationClient in my Google Play Console.
Just checking this is on someone’s RADAR. Doesn’t give an exact deadline yet (beyond 2025), but hope that it won’t be left till the last minute?
Thanks,
PDG
I second that.
plugin.googleSignIn is one of Scott’s plugins from the Solar2D Marketplace. He’s got a whole bug reporting system for his plugins. The best way to insure this issue is on his radar is probably to contact him directly.
https://solar2dmarketplace.com/plugins?GoogleSignIn_tech-scotth
I do not use Scott’s plugin but I got that warning too.
Probably there is something more to check on Solar2D.
What plugins do you use?
plugins =
{
["plugin.admob"] =
{
publisherId = "com.coronalabs"
},
["plugin.pollfish"] =
{
publisherId = "com.coronalabs",
supportedPlatforms = { android=true }
},
["plugin.gpgs.v3"] =
{
publisherId = "com.solar2d",
},
["plugin.utf8"] =
{
publisherId = "com.coronalabs"
},
["plugin.google.iap.billing.v2"] =
{
publisherId = "com.solar2d"
},
},
Ah- so the login is presumably running through plugin.gpgs.v3. In that case, I’d suggest filing an issue on GitHub. That’s the best way to insure that the problem gets noticed and resolved.
I’m also having issues with this.
I’m trying to update an older, active app to the new gpgs v3 and I recieved the above in my Google Play inbox, as well as the following message in logcat:
12-18 13:41:14.042 23044 23073 D plugin.gpgs.v3: login()
12-18 13:41:14.060 25275 27216 W Auth.Api.SignIn: [Service,SignInChimeraService] **************************** WARNING ***************************
12-18 13:41:14.060 25275 27216 W Auth.Api.SignIn: You are using the deprecated legacy Google Sign-In APIs from
12-18 13:41:14.060 25275 27216 W Auth.Api.SignIn: play-services-auth SDK. Please migrate to the Credential Manager
12-18 13:41:14.060 25275 27216 W Auth.Api.SignIn: APIs, see https://goo.gle/gsi-migration.
12-18 13:41:14.060 25275 27216 W Auth.Api.SignIn: ****************************************************************
Although this actually seems to log in OK (I can load saved games etc), the onLogin handler from gpgs passes an error, but with no error code or description:
12-18 13:49:38.685 24440 24468 I Corona : gpgs.onLogin
12-18 13:49:38.685 24440 24468 I Corona : (table)
12-18 13:49:38.685 24440 24468 I Corona : [phase] = (string) logged in
12-18 13:49:38.685 24440 24468 I Corona : [name] = (string) login
12-18 13:49:38.685 24440 24468 I Corona : [isError] = (boolean) true
Additionally, in this case gpgs.isAuthenticated() always returns false.
To try to get to the bottom of this, I made a brand new test app and configured it for GPGS in Google Play Console / Cloud. Not fun! However, this app runs without any problems. The deprecation warning doesn’t show up, and no error is reported when logging in. isAuthenticated() returns true.
So this suggests that there is some configuration issue in the backend for legacy app, rather than a problem with the plugin itself.
I’ve been tearing my hair out about this. Has anybody else had a problem with updating a live GPGS app to the new version?
plugins =
{
["plugin.google.iap.billing.v2"] =
{
publisherId = "com.solar2d",
supportedPlatforms = { android=true }
},
--General
["plugin.googleSignIn"] =
{
publisherId="tech.scotth",
supportedPlatforms = { android = true, iphone = true }
},
Well, it looks like Scott’s plugin and the Solar2D plugin.gpgs.v3 plugin are both using the same deprecated API.
I can’t see into Scott’s bug reporting, but it doesn’t look like anyone has logged the issue for the Solar2D plugin over on GitHub. Since Scott is active in maintaining both his own plugins and a lot of the Solar2D plugins, if someone notified him about the issue, perhaps he could take care of both plugins at the same time. (Hint, hint- people who rely on this plugin, of which I am not one.)
I did log something via the plugin support, but haven’t heard anything back yet…
I am looking into this
Thanks
Scott
Great news!