Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid scope error from oauth2 when starting up new bot #52

Open
austinvalle opened this issue Sep 3, 2016 · 2 comments
Open

Invalid scope error from oauth2 when starting up new bot #52

austinvalle opened this issue Sep 3, 2016 · 2 comments

Comments

@austinvalle
Copy link

When starting up a new bot, I get this message when trying to retrieve the authentication token:

400 That's an error
Error: invalid_scope
Request Details
scope=https://www.google.com/accounts/OAuthLogin
response_type=code
redirect_uri=urn:ietf:wg:oauth:2.0:oob
client_id=936475272427.apps.googleusercontent.com

Existing bots have not been affected as of right now.

@austinvalle
Copy link
Author

It looks like the issue also exists in the library (hangups) that hangupsjs was ported from, and is a result of some recent internal Google changes.

tdryer/hangups#260

@yohanes-ai
Copy link

Please refer to this link, this issue become wide spread for all Google Hangout Chat Bot
OAuth invalid scope

joakin added a commit to joakin/vicky-bot that referenced this issue Feb 6, 2017
Apparently hangouts changed the login method and the tokens are no
longer valid and there is no good way to get a new token.

Giving up on hangouts for now.

See yakyak/hangupsjs#52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants