OAuth2 request failed: Service responded with error: 'bad client id: APP_ID_OR_ORIGIN_NOT_MATCH'

2,498 views
Skip to first unread message

Santiago Taco

unread,
Apr 22, 2018, 11:45:51 AM4/22/18
to Chromium-Extensions-Announce
Good morning everybody,

I am trying to use Gmail APi in a chrome extension. I have reviewed this sample:

If I use the same credentials the connection is fine but If I use my credencial it does not work.
I have created a Create an OAuth 2.0 client ID and I have enabled Gmail API service:

ID de clientes OAuth 2.0

NombreFecha de creaciónTipoID de cliente
testApi10 abr. 2018App de Chrome93059932430.................................................oogleusercontent.com
When I install the extension I get this error:

Error2: OAuth2 request failed: Service responded with error: 'bad client id: APP_ID_OR_ORIGIN_NOT_MATCH'

Could someone help me with this problem?

garima bhardwaj

unread,
Jul 31, 2018, 11:22:13 AM7/31/18
to Chromium-Extensions-Announce
Please make sure that the ext id you provide while generating the client ID matches with your extension ID. You can check this either in "more info" section in developer dashboard or under extension description in chrome://extensions

garima bhardwaj

unread,
Jul 31, 2018, 11:28:39 AM7/31/18
to Chromium-Extensions-Announce
If that is correct then check whether or not you have added the public key in the manifest.json which is present under More info section in your listings in chrome developer dashboard.

redwo...@gmail.com

unread,
Aug 27, 2018, 5:32:23 PM8/27/18
to Chromium-Extensions-Announce
Hey, i am having a similar problem. I think to add the public key will solve but i don't know where to put the public key at in the manifest file. When loading the extension I got an error because I had a 'key' object. I removed the 'key' object and now the extension won't work. So where does the public key go in the manifest?
Reply all
Reply to author
Forward
0 new messages