google oauth error invalid_client no support email

52
votes

I try to implement google oauth, following the Google OAuth2ForDevices.

My App is registered on Google Cloud Console, as native App. When I try to follow the OAuth2ForDevices using Google Chromes - Advanced Rest Client Application, I get the json response with the user_code and verfication_url. Opening the verfication_url and enterering the user_code, leads to the follwoing Error:

invalid_client: no support email Error 400

I tried this with 2 registred Apps on Google Cloud Console. Both leading to the same error.

Anys hints, how to solve this? Do I have to register a support email somewhere in google cloud services?

4
oauth-2.0devicegoogle-oauth
In APIs & auth | Consent screen, did you set an EMAIL ADDRESS? I'm not sure that's the solution. I'm having the same problem, trying to debug now. I cannot set an email address on the consent screen because I get an "oops, our bad" error, apparently a google bug. This post seems to be the same problem: groups.google.com/forum/#!topic/… – janos
@janos that did the trick. Thanks a lot. I added my email adress in the consent screen. and now it works fine! – jerik
Good for you! Sadly I'm still stuck, I cannot set the email address... :( – janos

4 Answers

88
votes

It seems this can happen if you did not set an EMAIL ADDRESS on the Consent screen.

  1. Go to your Google Cloud Console
  2. Open your project
  3. Click APIs & auth
  4. Click Consent screen, and set EMAIL ADDRESS
  5. As per @ajmccall's answer, delete and recreate the client ID

This seems to have helped others, right now it does not help me. When I set an email address and click Save an error pops up:

Whoops! Our bad.

Please try again. If the problem persists, please let us know using the "Send feedback" link below. Copy the tracking number below, and include it with your feedback. Thanks!

This post seems to be about the same problem:

https://groups.google.com/forum/#!topic/google-doubleclick-for-publishers-api/6savNh4PBBI

12
votes

If you create OAuth credentials BEFORE you set the support email address in the consent screen, then it appears that you will always get this error, even after setting the support email.

I resolved this by setting the support email, and then recreating all necessary OAuth ids in the credentials page.

1
votes

Had the same issue. Worked when I logged in with an email not associated with your api auth.

0
votes

I had to recreate all my credentials (a new Client ID and a new Key).