chrome.identity.getAuthToken returning "bad client id: {0}" error

Question

I'm trying to use chrome.identity.getAuthToken to get a token, but every time I try this error shows up:

OAuth2 request failed: Service responded with error: 'bad client id: {0}'

I have no idea why this is happening. The client ID I put in manifest.json is exactly the same as the one on the Google Developers Console, and the correct scopes is also included:

oauth2: {
    "client_id": "NUMBERS-NUMBERS&LETTERS.apps.googleusercontent.com",
    "scopes": ["https://www.googleapis.com/auth/SOME_SERVICE"]
}

The extension is up on the webstore, and I don't see why it is still giving the bad client ID error.

What is possibly causing this error? What am I missing here?

Did you fix your issue ? If yes, can you share your answer ? — Florent Gz, Nov 17 '14 at 16:13
@FlorentGz - By choosing an email and a product name in the consent screen, the error simply stopped showing up. — Derek 朕會功夫, Nov 17 '14 at 16:55

score 2 · Answer 1 · answered Apr 11 '15 at 16:54

Just as a note for myself and for someone run into.

I have encounter this problems with chrome app , the answers is not my problem ,and finally I found the solution for my problem but produce the same error as the question.

As https://developer.chrome.com/apps/app_identity#client_id say is much special for chrome apps, you have to create a separate client id for your chrome app.

Go to the "API Access" navigation menu item and click on the Create an OAuth 2.0 client ID... blue button. Enter the requested branding information, select the Installed application type.

you must to choose Installed application an set you Application ID.

what's your Application ID ? chrome-extension://your application id

chrome-extension://gfmehiepojbflifceoplblionpfclfhf/

this worked for me. Thanks for the help. – UKDataGeek Dec 31 '21 at 00:09 — UKDataGeek, Dec 31 '21 at 00:09

score 1 · Accepted Answer · answered Aug 24 '14 at 13:14

1

I overcomed this problem by setting up the email address and product name in "Consent screen" in the Google Developer Console. Please refer to https://developers.google.com/console/help/new/#userconsent for detail.

answered Aug 24 '14 at 13:14

Shih-Wen Su

2,589
24
21

score 1 · Answer 3 · answered Jan 20 '20 at 10:09

I had a similar problem. Everything seemed to work fine on my own laptop, but when i ran it on another device i got that "bad client id" error.

My problem was that the client-id changed from one device to another, as i did not yet upload my extension to the chrome store.

To overcome that problem, i followed the instructions of How to change chrome packaged app id Or Why do we need key field in the manifest.json?.

You need to create a key to keep the client-id persistent through all devices.

Hope that helps finding the right answer for people with the same issue quicker.

chrome.identity.getAuthToken returning "bad client id: {0}" error

3 Answers3