Error 400: invalid_scope
See original GitHub issueGetting Error 400: invalid_scope when tried to authorize.
Steps to Reproduce the Problem
- Open cmd
- Type clasp login
- copy url and paste in browser
- hits to error
Specifications
- Node version (
node -v
): 5.6.0 - Version (
clasp -v
):1.5.3 - OS (Mac/Linux/Windows):Windows
Issue Analytics
- State:
- Created 5 years ago
- Reactions:6
- Comments:14 (6 by maintainers)
Top Results From Across the Web
"Error 400: invalid_scope" error when performing OAuth2 flow ...
I'm trying to use the Datastudio API to manipulate reports permissions in Datastudio. I have G Suite account registered and when I perform...
Read more >Ask Question - Stack Overflow
Error 400 : invalid_scope "https://www.googleapis.com/auth/chat.bot" · Ask Question. Asked 4 years, 9 months ago. Modified 1 year ago. Viewed 9k times.
Read more >Authorization Error 400: invalid_scope - Google Groups
Basically, the cause is the oauth URL is too long for the browser to take from the command line but ok to be...
Read more >Erreur 400 : invalid_scope via OAuth - Issue Tracker - Google
When trying to get access to Keep API for an account, an auhtorization error is thrown because the scope is not valid **Problem...
Read more >Authorization Error Error 400: invalid_scope #1358 - GitHub
Hi Team, We getting below error while configuring the GAM 6.0. Please check or suggest. Authorization Error Error 400: invalid_scope Some ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi all, It looks like there’s an outage with StackDriver causing the error. I’m trying to have the team fix it.
If you want to temporarily fix login until that problem is resolved, follow these instructions:
Open the file
(If that doesn’t work, your computer may have a different location. Try this to find the location:
npm list -g | grep "clasp"
)And comment out the line with a prefix of
//
:Update: Aug 31, 6:30pm PST The API team says that they will fix this issue Monday. 🙁
I’ll give updates here.
Just tried using Clasp for the first time today and got a similar error when attempting to login.