-
Notifications
You must be signed in to change notification settings - Fork 181
Question to oauth2 - invalid_scope #682
Comments
I think you need to create a new client ID for your application in Google's developer console. You need to use your own package name and signing certificate hash. |
thank you for answering:) I actually did, but there is no permission for the scope: oauth2:https://www.google.com/accounts/OAuthLogin What kind of config, permission should I add there? |
Not sure what you are doing, but the only two fields in the 'Create Client ID' dialog are 'package name' and 'signing certificate fingerprint'. You don't need any permissions. |
I exactly did this, but always invalid scope on different devices... :-( Maybe someone has an idea how solve this? |
Yes, there are debug and release Client IDs. |
I did not change anything. Only the package name of andlytics for tryouts ...and after I got this exception. |
Hallo everybody :-)
I tried to fork your project to use some parts of the code.Currently I have a new packagename in my project.
I got an" com.google.android.gms.auth.GoogleAuthException: INVALID_SCOPE" exception
here:
oauthLoginToken = GoogleAuthUtil.getTokenWithNotification(AndlyticsApp.getInstance(), accountName, OAUTH_LOGIN_SCOPE, null);
If I use the andlytics packagename everything goes right.
Do I have to add something to the developer console or even do somehting special with apk signing?
Thank you so much :-)
The text was updated successfully, but these errors were encountered: