Google+ APIs and OAuth requests are being shutdown on March

Solar2D Android
#1

Hi,

I got the a message from Google titled “Google+ APIs and OAuth requests are being shutdown on March” and our app is listed using the following methods of OAuth calls: plus.login, plus.me, plus.profile.language.read, plus.moments.write, plus.circles.members.read, plus.profile.agerange.read, plus.circles.members

I’m a bit confused should we update our app or not. I’m not aware such calls or maybe I just don’t remember :slight_smile: We use the following plugins.

 plugins = { ["plugin.bit"] = { publisherId = "com.coronalabs" }, ["plugin.unityads"] = { publisherId = "com.coronalabs", supportedPlatforms = { iphone=true, android=true } }, ["plugin.applovin"] = { publisherId = "com.coronalabs", supportedPlatforms = { iphone=true, android=true } }, ["plugin.gpgs"] = { publisherId = "com.coronalabs", supportedPlatforms = { android=true } }, ["CoronaProvider.gameNetwork.apple"] = { publisherId = "com.coronalabs", supportedPlatforms = { iphone=true } }, ["plugin.flurry.analytics"] = { publisherId = "com.coronalabs", supportedPlatforms = { iphone=true, android=true } }, ["plugin.google.iap.v3"] = { publisherId = "com.coronalabs", supportedPlatforms = { android=true } }, }
#2

Yeah i received this email too, for all my games which use gpgs (i use v2) here is a link with more info 

https://developers.google.com/+/integrations-shutdown

#3

Yeah, seems like a GPGS V2 issue.  So this happens in March, and there’s also the Google Drive API deprecation in December 2019 to go along with that.  Both target my apps that use GPGS.

https://forums.coronalabs.com/topic/74512-gpgs-google-drive-android-api-is-being-deprecated/

#4

GPGS uses a Google Plus login. GPGS v2 was designed and rewritten around not using Google Plus for logins. GPGS v2 should solve this. There are however breaking changes.

I would recommend visiting out blog:  https://coronalabs.com/blog

and search for GPGS and read the GPGS v2 posts from the last quarter or so of 2018 to catch up on the changes you need to implement GPGS v2. It’s mostly compatible, but v1, but there are changes to the init and login process and the saving of game data doesn’t work with some code people copied from other developers who shared it in the forums. i.e. there were multiple ways of doing it, now there seems to be fewer ways of doing it.

Rob

#5

Hey Rob, it is strange, i do use GPGS v2 for all our games and still received the notification from google for these apps… i call the login for gpgs v2 exactly how it is specified in the blog and docs.

gpgs.login( { userInitiated=true, listener=gpgsLoginListener } )

#6

Hi,

today I got an email titled “correction”. So do we have to update the app?

Earlier this week we sent you an email related to your projects that will be impacted by the Google+ API shutdown, which also affects requests for Google+ OAuth scopes.

The email listed that one or more of your projects are requesting the “plus.me” scope, and would thus be affected. We would like to clarify that only  projects directly requesting the “plus.me” scope are affected. This scope may have been listed in some emails, even if not directly requested by your project. We apologize for any confusion caused.

If you are directly requesting the “plus.me” scope, any other Google+ OAuth scopes, or making any Google+ API calls, please ensure that you remove these requests from your project  before March 7, 2019.

To see if your project is directly requesting the “plus.me” or any other Google+ OAuth scopes:

  • If your project is written in Google Apps Script, you can view which scopes your project is requesting by reviewing your project properties in App Script Editor.
  • If your project is not written in Google Apps Script, please check your code for references to “plus.me” in OAuth scope requests. We recommend that you review projects using any 3rd-party libraries that support sign-in or social functionality, as these may also be affected by the shutdown.
#7

To save people some time: https://coronalabs.com/blog/2018/10/31/update-on-the-new-gpgs-v2-plugin/

#8

GPGS v2 was specifically built to remove the Google + scope. It sounds like Google may have sent out some messages by mistake.

Rob

#9

I also received the original email and correction email.

I am not sure if I missed any previous notification, but we basically have about a month to get updates out, if I read this correctly.

–john

#10

Yeah i received this email too, for all my games which use gpgs (i use v2) here is a link with more info 

https://developers.google.com/+/integrations-shutdown

#11

Yeah, seems like a GPGS V2 issue.  So this happens in March, and there’s also the Google Drive API deprecation in December 2019 to go along with that.  Both target my apps that use GPGS.

https://forums.coronalabs.com/topic/74512-gpgs-google-drive-android-api-is-being-deprecated/

#12

GPGS uses a Google Plus login. GPGS v2 was designed and rewritten around not using Google Plus for logins. GPGS v2 should solve this. There are however breaking changes.

I would recommend visiting out blog:  https://coronalabs.com/blog

and search for GPGS and read the GPGS v2 posts from the last quarter or so of 2018 to catch up on the changes you need to implement GPGS v2. It’s mostly compatible, but v1, but there are changes to the init and login process and the saving of game data doesn’t work with some code people copied from other developers who shared it in the forums. i.e. there were multiple ways of doing it, now there seems to be fewer ways of doing it.

Rob

#13

Hey Rob, it is strange, i do use GPGS v2 for all our games and still received the notification from google for these apps… i call the login for gpgs v2 exactly how it is specified in the blog and docs.

gpgs.login( { userInitiated=true, listener=gpgsLoginListener } )

#14

Hi,

today I got an email titled “correction”. So do we have to update the app?

Earlier this week we sent you an email related to your projects that will be impacted by the Google+ API shutdown, which also affects requests for Google+ OAuth scopes.

The email listed that one or more of your projects are requesting the “plus.me” scope, and would thus be affected. We would like to clarify that only  projects directly requesting the “plus.me” scope are affected. This scope may have been listed in some emails, even if not directly requested by your project. We apologize for any confusion caused.

If you are directly requesting the “plus.me” scope, any other Google+ OAuth scopes, or making any Google+ API calls, please ensure that you remove these requests from your project  before March 7, 2019.

To see if your project is directly requesting the “plus.me” or any other Google+ OAuth scopes:

  • If your project is written in Google Apps Script, you can view which scopes your project is requesting by reviewing your project properties in App Script Editor.
  • If your project is not written in Google Apps Script, please check your code for references to “plus.me” in OAuth scope requests. We recommend that you review projects using any 3rd-party libraries that support sign-in or social functionality, as these may also be affected by the shutdown.
#15

To save people some time: https://coronalabs.com/blog/2018/10/31/update-on-the-new-gpgs-v2-plugin/

#16

GPGS v2 was specifically built to remove the Google + scope. It sounds like Google may have sent out some messages by mistake.

Rob

#17

I also received the original email and correction email.

I am not sure if I missed any previous notification, but we basically have about a month to get updates out, if I read this correctly.

–john