has been deprecated in Google Play services 9.4. In the past, the
https://www.googleapis.com/auth/plus.login scope allowed access to a list of
people in the user's circles in addition to their name and profile information.
Starting in September 2016, the
plus.login scope will allow access to only the
name and profile info for new users; calls to
Plus.PeopleApi.loadConnected return empty
results for those new sign-ins. In 2017 Q1, you will get empty results back for
Instead of requesting the
plus.login scope, we strongly recommend you instead
profile scope, which can give your app a streamlined, one-tap
In place of the social connection data from
Plus.PeopleApi, you can get rich
cloud- and device-based contacts data from the
or use the new Google People API.
To enhance the distribution of your app through the social graphs of your app's
user base, use Firebase Invites.
We are also deprecating Google+ Sign-In and the
APIs. As a replacement, use
By using the latest API, you can improve the security, user experience, and
performance of your app, particularly if your app currently does either of the
- Retrieves the user's email address using
Plus.AccountApi.getAccountName()(which requires the user to grant the Contacts runtime permission on Android Marshmallow and newer)
GoogleAuthUtil.getTokento obtain a token
Read our earlier blog post for details:
Improving the Security and User Experience of your Google Sign In Implementation.
Also, check out the migration guide
GoogleAuthUtil and Plus API users.
With the deprecation of the Google+ People API, we also changed our branding guidelines. All sign-in buttons should be branded as "Sign in with Google" with either blue or white backgrounds, as long as the Google G logo has a white background.