java.lang.Object | |
↳ | com.google.android.gms.common.Scopes |
OAuth 2.0 scopes for use with Google Play services. See the specific client methods for details on which scopes are required.
Constants | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
String | APP_STATE | Scope for using the App State service. | |||||||||
String | CLOUD_SAVE | Scope for using the CloudSave service. | |||||||||
String | DRIVE_APPFOLDER | Scope for accessing appfolder files from Google Drive. | |||||||||
String | DRIVE_FILE | Scope for access user-authorized files from Google Drive. | |||||||||
String | OAuth 2.0 scope for accessing user's Google account email address. | ||||||||||
String | FITNESS_ACTIVITY_READ | Scope for read access to activity-related data types in Google Fit. | |||||||||
String | FITNESS_ACTIVITY_READ_WRITE | Scope for read/write access to activity-related data types in Google Fit. | |||||||||
String | FITNESS_BODY_READ | Scope for read access to biometric data types in Google Fit. | |||||||||
String | FITNESS_BODY_READ_WRITE | Scope for read/write access to biometric data types in Google Fit. | |||||||||
String | FITNESS_LOCATION_READ | Scope for read access to location-related data types in Google Fit. | |||||||||
String | FITNESS_LOCATION_READ_WRITE | Scope for read/write access to location-related data types in Google Fit. | |||||||||
String | FITNESS_NUTRITION_READ | Scope for read access to nutrition data types in Google Fit. | |||||||||
String | FITNESS_NUTRITION_READ_WRITE | Scope for read/write access to nutrition data types in Google Fit. | |||||||||
String | GAMES | Scope for accessing data from Google Play Games. | |||||||||
String | PLUS_LOGIN |
This constant is deprecated.
We recommend switching to PROFILE scope to get the one-tap sign-in
experience. See
Getting Profile Information. Your app will get much higher sign-in completion rate by
switching to profile scopes because of the streamlined user experience. And your existing
users with PLUS_LOGIN grant will not be asked to sign-in again.
If you really need user's age range and locale information (which is the only additional information you can get from PLUS_LOGIN as of September 2016), use below scopes in addition to PROFILE:
|
|||||||||
String | PLUS_ME | This scope was previously named PLUS_PROFILE. |
|||||||||
String | PROFILE | OAuth 2.0 scope for accessing user's basic profile information. |
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
![]() |
Scope for using the App State service.
Scope for using the CloudSave service.
Scope for accessing appfolder files from Google Drive.
Scope for access user-authorized files from Google Drive.
OAuth 2.0 scope for accessing user's Google account email address.
Scope for read access to activity-related data types in Google Fit. These include activity type, calories consumed and expended, step counts, and others.
Scope for read/write access to activity-related data types in Google Fit. These include activity type, calories consumed and expended, step counts, and others.
Scope for read access to biometric data types in Google Fit. These include heart rate, height, and weight.
Scope for read/write access to biometric data types in Google Fit. These include heart rate, height, and weight.
Scope for read access to location-related data types in Google Fit. These include location, distance, and speed.
Scope for read/write access to location-related data types in Google Fit. These include location, distance, and speed.
Scope for read access to nutrition data types in Google Fit.
Scope for read/write access to nutrition data types in Google Fit.
Scope for accessing data from Google Play Games.
This constant is deprecated.
We recommend switching to PROFILE
scope to get the one-tap sign-in
experience. See
Getting Profile Information. Your app will get much higher sign-in completion rate by
switching to profile scopes because of the streamlined user experience. And your existing
users with PLUS_LOGIN grant will not be asked to sign-in again.
If you really need user's age range and locale information (which is the only additional information you can get from PLUS_LOGIN as of September 2016), use below scopes in addition to PROFILE:
OAuth 2.0 scope for accessing the user's name, basic profile info and Google+ profile info.
When using this scope, your app will have access to:
This scope was previously named PLUS_PROFILE.
When using this scope, it does the following:
OAuth 2.0 scope for accessing user's basic profile information.
When using this scope, it does the following: