Authentication Failure #671

DanTheTechMan · 2022-03-09T22:31:36Z

Hello,

I followed the instructions in the Setup Wiki and I don't believe I missed anything, however I keep getting an Authentication Failure error. Here's a screenshot of the error:

I've already tried moving the OAuth 2.0 JSON credentials file to various different locations on my PC (I'm using a Windows PC), however I keep getting this error. Is this a bug or am I doing something wrong or missing something? Please advise. Thanks.

WisdomCritFail · 2022-03-09T22:57:47Z

im getting the same error :(

kszkristof · 2022-03-10T13:35:44Z

same, on a win11 fresh install. i guess its good to know that its not only happening to me ¯_(ツ)_/¯

ZeKap · 2022-03-10T14:28:32Z

Same here on Linux (Ubuntu 20.04)

NicoAnth · 2022-03-11T13:19:48Z

Same here on windows 10

gabrielPaim98 · 2022-03-11T15:21:07Z

Same error hero. Looking at the dev tools there seems to be no "redirect_uri" on given client_secret.apps.googleusercontent.com.json.
I was able to fix it by going to Cloud Console, credentials, and using "Web client (auto created by Google Service" under OAuth 2.0 client IDs. Just download the .json file and change the "Key file Path" on the app to this new one.
Let me know if there might be any security issues with this 😀.

jamie-crawford · 2022-03-11T21:23:22Z

I had this error yesterday. Today I tried again and still received the error. On a lark, I redownloaded my key and it worked. The two key files are quite different in content. Not sure what changed, but it might be worth redownloading your key if you are still experiencing this.

im-coder-lg · 2022-03-12T00:41:33Z

Hmm @Melvin-Abraham documentation of this issue?

Enryhen · 2022-03-13T07:34:58Z

I have also experienced this same exact issue on windows 11, hope it could be fixed soon.

im-coder-lg · 2022-03-13T07:47:01Z

Download the JSON file again with the steps above. /ping @Melvin-Abraham !!!

Melvin-Abraham · 2022-03-13T12:53:14Z

Thank you folks for pointing this out and figuring out a solution 😊. I'll add this soon in the FAQ

dwnsideup · 2022-03-13T16:15:01Z

Same

sumeshir26 · 2022-03-14T02:53:50Z

@dwnsideup Try redownlowding your key file

zNoobs · 2022-03-14T10:51:11Z

Same problem,

JSON from https://console.actions.google.com/u/0/project/{YOURPROJECT}/deviceregistration/ doesn't work.
JSON (same Client ID as previous one) from https://console.cloud.google.com/apis/credentials?project={YOURPROJECT} doesn't work.
JSON "Web client (auto created by Google Service)" (different Client ID) from https://console.cloud.google.com/apis/credentials?project={YOURPROJECT} works

But after selecting the Google account and clicking on "Continue", I get a blank page with this error:
Unable to process request due to missing initial state. This may happen if browser sessionStorage is inaccessible or accidentally cleared.
I tried with another Google account, same error.
I tried with another web browser, same error.

EDIT:
Now the JSON from cloud console works (I didn't change any settings, I just redownloaded it), and I get the code (Setting authentication in the app step 10) but I get this error on the software:

Failed to get Tokens
Assistant failed to fetch the tokens from server. Either the auth code is invalid or the rate limit might have exceeded.
Try selecting a different Google Account.
Error: Error getting tokens

I tried with another Google account, same error.
Uing the JSON from Web client ID still shows "Unable to process request due to missing initial state. [...]" error.

kszkristof · 2022-03-14T12:40:10Z

Unable to process request due to missing initial state. This may happen if browser sessionStorage is inaccessible or accidentally cleared.

I got the same error when using Web client (auto created by Google Service) that was suggested by gabrielPaim98. I "fixed" it by deleting the existing client IDs and recreating a new one, waiting a day and then downloading the new JSON and it works now.

I don't know if the waiting affected the results or not but when I downloaded the JSON file directly after creating the client credentials, it didn't work..? I think that this is a problem on Google's end (it says that it has created the credentials but it haven't yet or something like that)

zNoobs · 2022-03-15T16:54:09Z

Still same error today, even with new JSON created:

Failed to get Tokens
Assistant failed to fetch the tokens from server. Either the auth code is invalid or the rate limit might have exceeded.
Try selecting a different Google Account.
Error: Error getting tokens

vettloffah · 2022-03-16T18:25:42Z

Tried with multiple keyfiles, including all recommendations above. Getting Unable to process request due to missing initial state. This may happen if browser sessionStorage is inaccessible or accidentally cleared. error each time.

Ahmed00010 · 2022-03-18T13:02:10Z

Same error hero. Looking at the dev tools there seems to be no "redirect_uri" on given client_secret.apps.googleusercontent.com.json. I was able to fix it by going to Cloud Console, credentials, and using "Web client (auto created by Google Service" under OAuth 2.0 client IDs. Just download the .json file and change the "Key file Path" on the app to this new one. Let me know if there might be any security issues with this grinning.

thanks

Hiddespenkelink · 2022-03-18T13:21:45Z

Also getting errors.

Using the Web Client ID the page doesn't load and this appears: This site can’t be reached localhost refused to connect.

Using the same client ID is the same for everyone Unable to process request due to missing initial state. This may happen if browser sessionStorage is inaccessible or accidentally cleared.

Same issue here

afrizalyogi · 2022-03-18T18:42:13Z

Also getting errors.

Using the Web Client ID the page doesn't load and this appears: This site can’t be reached localhost refused to connect.

Using the same client ID is the same for everyone Unable to process request due to missing initial state. This may happen if browser sessionStorage is inaccessible or accidentally cleared.

Hi guys, I found something that maybe can solve this
Unable to process request due to missing initial state. This may happen if browser sessionStorage is inaccessible or accidentally cleared. problem.

So, I was copy this code and paste it into the app. This worked for me but I don't know if it will work perfectly or not.

SivaMarti · 2022-03-18T23:21:45Z

Also getting errors.

Using the Web Client ID the page doesn't load and this appears: This site can’t be reached localhost refused to connect.

Using the same client ID is the same for everyone Unable to process request due to missing initial state. This may happen if browser sessionStorage is inaccessible or accidentally cleared.

Hi guys, I found something that maybe can solve this Unable to process request due to missing initial state. This may happen if browser sessionStorage is inaccessible or accidentally cleared. problem.

So, I was copy this code and paste it into the app. This worked for me but I don't know if it will work perfectly or not.

I would just like to verify that this solution by @afrizalyogi worked for me 100%.

I was having the exact same issue, "Unable to process request due to missing initial state. This may happen if browser sessionStorage is inaccessible or accidentally cleared."

The token code seems to appear in the url box. By copying the numbers starting after, "code=" and before "&scope", then pasting them in the Unofficial Google Assistant set up where it asks for the code, resulted in a successful authentication.

Also had to follow previous suggestions by others in this thread,

ie. deleting previous created Client IDs under OAuth 2.0 client IDs, creating a new Client ID for OAuth 2.0, publishing the project under OAuth consent screen to where it switches to "In production", deleting the previously downloaded OAuth client .json file and tokens.json file, redownloading the OAuth client .json file, completely exiting Unofficial Google Assistant from the tray, opening the Unofficial Google Assistant, deleting the previous input "Key File Path " and "Saved Tokens Path", setting the ""Key File Path" again with the newly downloaded OAuth client .json file.

(([One other thing that I did, personally, that wasn't mentioned in the instructions when starting out was to create a folder called "Google Assistant" in the C Drive so that all files were nested in that folder; so that it was structured ie. C:\Google Assistant\Google Assistant\ C:\Google Assistant*****.json C:\Google Assistant\tokens.json

Whether this helped are not, I don't know.]))

I hope this can help others get this project working until an update can be made.

ghost · 2022-03-20T23:17:32Z

Also getting errors.

Using the Web Client ID the page doesn't load and this appears: This site can’t be reached localhost refused to connect.

Using the same client ID is the same for everyone Unable to process request due to missing initial state. This may happen if browser sessionStorage is inaccessible or accidentally cleared.

Hi guys, I found something that maybe can solve this Unable to process request due to missing initial state. This may happen if browser sessionStorage is inaccessible or accidentally cleared. problem.

So, I was copy this code and paste it into the app. This worked for me but I don't know if it will work perfectly or not.

I would just like to verify that this solution by @afrizalyogi worked for me 100%.

I was having the exact same issue, "Unable to process request due to missing initial state. This may happen if browser sessionStorage is inaccessible or accidentally cleared."

The token code seems to appear in the url box. By copying the numbers starting after, "code=" and before "&scope", then pasting them in the Unofficial Google Assistant set up where it asks for the code, resulted in a successful authentication.

Also had to follow previous suggestions by others in this thread,

ie. deleting previous created Client IDs under OAuth 2.0 client IDs, creating a new Client ID for OAuth 2.0, publishing the project under OAuth consent screen to where it switches to "In production", deleting the previously downloaded OAuth client .json file and tokens.json file, redownloading the OAuth client .json file, completely exiting Unofficial Google Assistant from the tray, opening the Unofficial Google Assistant, deleting the previous input "Key File Path " and "Saved Tokens Path", setting the ""Key File Path" again with the newly downloaded OAuth client .json file.

(([One other thing that I did, personally, that wasn't mentioned in the instructions when starting out was to create a folder called "Google Assistant" in the C Drive so that all files were nested in that folder; so that it was structured ie. C:\Google Assistant\Google Assistant\ C:\Google Assistant*****.json C:\Google Assistant\tokens.json

Whether this helped are not, I don't know.]))

I hope this can help others get this project working until an update can be made.

This, and the quoted reply worked. Thanks!

tmack8001 · 2022-03-24T20:47:45Z

@afrizalyogi I hope you have either modified that token and/or rotated the credentials 😜 (not sure if tokens can be used multiple times, but typically not good security practice to share them in the clear)

GuyMayer · 2022-08-27T23:14:32Z

yes Found the solution here https://www.youtube.com/watch?v=PPL-jLOcZvs

Funkeemonkee06 · 2022-08-28T13:28:43Z

Same error hero. Looking at the dev tools there seems to be no "redirect_uri" on given client_secret.apps.googleusercontent.com.json. I was able to fix it by going to Cloud Console, credentials, and using "Web client (auto created by Google Service" under OAuth 2.0 client IDs. Just download the .json file and change the "Key file Path" on the app to this new one. Let me know if there might be any security issues with this grinning.

THANK YOU SO MUCH

Allow assistant to pick-up OAuth authorization code automatically from post consent screen if redirect URI points to localhost (port 5754) - Add dep: express.js - Add page for successful authorization - Update link for dep `google-assistant` with prefix `github:` Addresses Authentication Failure #671

gamer564q · 2022-09-15T20:33:36Z

im getting the same error

im-coder-lg · 2022-09-16T12:34:16Z

@gamer564q instead of its not working, check the comments that got a fix, this makes it hard for us to trace commented fixes.

@Melvin-Abraham can you convert this to a discussion if at all possible?

Morbiusk · 2022-11-16T03:07:06Z

yes Found the solution here https://www.youtube.com/watch?v=PPL-jLOcZvs

Gracias...

WatchTheory · 2022-11-16T18:22:36Z

yes Found the solution here https://www.youtube.com/watch?v=PPL-jLOcZvs

Worked for me, thanks

Melvin-Abraham · 2023-01-01T11:17:24Z

Addressed this issue in version v1.1.0. Also refer Configure Credentials Guide. This issue was added in FAQ as well

Melvin-Abraham · 2023-01-01T11:17:32Z

Closing as resolved

manofthepeople · 2023-01-13T08:39:34Z

it says
when i do this

ryukinix · 2023-06-02T01:32:39Z

Please update the guide considering this and not only FAQ! It's part of the flow currently, the default path, not a alternative one.

PaulMangoKe · 2023-06-18T14:28:52Z

Same error hero. Looking at the dev tools there seems to be no "redirect_uri" on given client_secret.apps.googleusercontent.com.json. I was able to fix it by going to Cloud Console, credentials, and using "Web client (auto created by Google Service" under OAuth 2.0 client IDs. Just download the .json file and change the "Key file Path" on the app to this new one. Let me know if there might be any security issues with this 😀.

Thank you sir!

PaulMangoKe · 2023-06-18T14:30:56Z

Also getting errors.

Using the Web Client ID the page doesn't load and this appears: This site can’t be reached localhost refused to connect.

Using the same client ID is the same for everyone Unable to process request due to missing initial state. This may happen if browser sessionStorage is inaccessible or accidentally cleared.

Hi guys, I found something that maybe can solve this Unable to process request due to missing initial state. This may happen if browser sessionStorage is inaccessible or accidentally cleared. problem.
So, I was copy this code and paste it into the app. This worked for me but I don't know if it will work perfectly or not.

I would just like to verify that this solution by @afrizalyogi worked for me 100%.
I was having the exact same issue, "Unable to process request due to missing initial state. This may happen if browser sessionStorage is inaccessible or accidentally cleared."
The token code seems to appear in the url box. By copying the numbers starting after, "code=" and before "&scope", then pasting them in the Unofficial Google Assistant set up where it asks for the code, resulted in a successful authentication.
Also had to follow previous suggestions by others in this thread,
ie. deleting previous created Client IDs under OAuth 2.0 client IDs, creating a new Client ID for OAuth 2.0, publishing the project under OAuth consent screen to where it switches to "In production", deleting the previously downloaded OAuth client .json file and tokens.json file, redownloading the OAuth client .json file, completely exiting Unofficial Google Assistant from the tray, opening the Unofficial Google Assistant, deleting the previous input "Key File Path " and "Saved Tokens Path", setting the ""Key File Path" again with the newly downloaded OAuth client .json file.
(([One other thing that I did, personally, that wasn't mentioned in the instructions when starting out was to create a folder called "Google Assistant" in the C Drive so that all files were nested in that folder; so that it was structured ie. C:\Google Assistant\Google Assistant\ C:\Google Assistant*****.json C:\Google Assistant\tokens.json
Whether this helped are not, I don't know.]))
I hope this can help others get this project working until an update can be made.

This, and the quoted reply worked. Thanks!

So grateful for people like you!

dash-1-1 · 2023-06-26T17:00:32Z

Help what to do about this

Error: Getting metadata from plugin failed with error: No access, refresh token, API key or refresh handler callback is set.

im-coder-lg · 2023-07-03T12:01:07Z

yes Found the solution here https://www.youtube.com/watch?v=PPL-jLOcZvs

@dash-1-1 have you tried this?

JohnLGalt · 2023-08-16T18:52:52Z

Same error hero. Looking at the dev tools there seems to be no "redirect_uri" on given client_secret.apps.googleusercontent.com.json. I was able to fix it by going to Cloud Console, credentials, and using "Web client (auto created by Google Service" under OAuth 2.0 client IDs. Just download the .json file and change the "Key file Path" on the app to this new one. Let me know if there might be any security issues with this 😀.

I managed to bypass the error in Google Assistant using the Web Client ID, but now when it opens the web browser, and i log in, it throws me to a "something went wrong" window and after that to another page that says "The server cannot process the request because it is malformed. It should not be retried. That’s all we know."

Any advice on how to fix it?

If you're still looking for an answer to this, I had the same thing occurring when I used a 3rd party tool to pick a browser when links are clicked (Browser Chooser 2) set as default browser.

Changing Chrome to be default browser (temporarily) in my OS (Win11) ended this exact issue so I could fix the main issue with the tokens as well.

iamarb · 2023-10-05T18:38:57Z

help me i face failed to get tokens

WhiteCat65 · 2024-02-15T07:29:48Z

I dont have "Web client (auto created by google)" what do i do

D4nChen · 2024-04-14T10:21:41Z

I dont have "Web client (auto created by google)" what do i do

I have the same issue.

ak-47-brar · 2024-05-02T13:05:49Z

I dont have "Web client (auto created by google)" what do i do

hey did you got the fix for this

ak-47-brar · 2024-05-02T13:14:33Z

Hello,

I followed the instructions in the Setup Wiki and I don't believe I missed anything, however I keep getting an Authentication Failure error. Here's a screenshot of the error: I've already tried moving the OAuth 2.0 JSON credentials file to various different locations on my PC (I'm using a Windows PC), however I keep getting this error. Is this a bug or am I doing something wrong or missing something? Please advise. Thanks.

did you got fix for this ?

D4nChen · 2024-05-02T13:47:11Z

I dont have "Web client (auto created by google)" what do i do

hey did you got the fix for this

I followed this guide and resolved it.

im-coder-lg · 2024-05-07T15:41:05Z

Okay, that guide solved it, but it was just a normal setup guide! So, the setup guide still works! Note that you don't necessarily download the OAuth JSON from the Actions Console; the GCP project connected to it has a better and proper(working) OAuth JSON, so follow that video, but rather download from the GCP Console. That ought to work. Now, we must find a loophole for Personal Results.

AthanasiosPetsanis · 2024-08-01T15:35:13Z

I had this error yesterday. Today I tried again and still received the error. On a lark, I redownloaded my key and it worked. The two key files are quite different in content. Not sure what changed, but it might be worth redownloading your key if you are still experiencing this.

This worked for me too, kinda. I had to create a new secret, delete the old one, download the json again and this time it worked

github-actions bot added the 🐛 bug Something isn't working label Mar 9, 2022

github-actions bot assigned Melvin-Abraham Mar 9, 2022

Melvin-Abraham pinned this issue Mar 13, 2022

im-coder-lg mentioned this issue Mar 14, 2022

Error:Invalid Key File[🐛 Bug]: #672

Open

3 tasks

emiliopedrollo mentioned this issue Mar 16, 2022

Not able to generate code for token #342

Open

afrizalyogi mentioned this issue Mar 19, 2022

[🐛 Bug]: Unable to process request due to missing initial state. This may happen if browser session Storage is inaccessible or accidentally cleared. #677

Closed

3 tasks

sumeshir26 mentioned this issue Mar 20, 2022

Authentication Failure #678

Open

tmack8001 mentioned this issue Mar 24, 2022

Get Token/Code UI incorrectly tries to load localhost #684

Open

3 tasks

cburgard mentioned this issue Aug 25, 2022

[🐛 Bug]: Issue with authentication and device registration #765

Open

3 tasks

im-coder-lg mentioned this issue Aug 27, 2022

Authentication Failure #766

Open

im-coder-lg mentioned this issue Sep 5, 2022

[🐛 Bug]: Cant Authorize - Cant get Token #729

Closed

3 tasks

zersiax mentioned this issue Nov 14, 2022

[🐛 Bug]: "Localhost couldn't provide a secure connection" #813

Open

3 tasks

Melvin-Abraham closed this as completed Jan 1, 2023

Melvin-Abraham mentioned this issue Jan 1, 2023

Incorrect Setup instructions Melvin-Abraham/gaudc-wiki#1

Closed

Authentication Failure #671

Authentication Failure #671

Comments

DanTheTechMan commented Mar 9, 2022

WisdomCritFail commented Mar 9, 2022

kszkristof commented Mar 10, 2022

ZeKap commented Mar 10, 2022

NicoAnth commented Mar 11, 2022

gabrielPaim98 commented Mar 11, 2022

jamie-crawford commented Mar 11, 2022

im-coder-lg commented Mar 12, 2022

Enryhen commented Mar 13, 2022 • edited Loading

im-coder-lg commented Mar 13, 2022

Melvin-Abraham commented Mar 13, 2022

dwnsideup commented Mar 13, 2022

sumeshir26 commented Mar 14, 2022

zNoobs commented Mar 14, 2022 • edited Loading

kszkristof commented Mar 14, 2022

zNoobs commented Mar 15, 2022

vettloffah commented Mar 16, 2022

Ahmed00010 commented Mar 18, 2022

Hiddespenkelink commented Mar 18, 2022

afrizalyogi commented Mar 18, 2022

SivaMarti commented Mar 18, 2022

ghost commented Mar 20, 2022

tmack8001 commented Mar 24, 2022

GuyMayer commented Aug 27, 2022

Funkeemonkee06 commented Aug 28, 2022

gamer564q commented Sep 15, 2022

im-coder-lg commented Sep 16, 2022

Morbiusk commented Nov 16, 2022

WatchTheory commented Nov 16, 2022

Melvin-Abraham commented Jan 1, 2023

Melvin-Abraham commented Jan 1, 2023

manofthepeople commented Jan 13, 2023

ryukinix commented Jun 2, 2023

PaulMangoKe commented Jun 18, 2023

PaulMangoKe commented Jun 18, 2023

dash-1-1 commented Jun 26, 2023

im-coder-lg commented Jul 3, 2023

JohnLGalt commented Aug 16, 2023 • edited Loading

iamarb commented Oct 5, 2023

WhiteCat65 commented Feb 15, 2024 • edited Loading

D4nChen commented Apr 14, 2024

ak-47-brar commented May 2, 2024

ak-47-brar commented May 2, 2024

D4nChen commented May 2, 2024

im-coder-lg commented May 7, 2024 • edited Loading

AthanasiosPetsanis commented Aug 1, 2024

Enryhen commented Mar 13, 2022 •

edited

Loading

zNoobs commented Mar 14, 2022 •

edited

Loading

JohnLGalt commented Aug 16, 2023 •

edited

Loading

WhiteCat65 commented Feb 15, 2024 •

edited

Loading

im-coder-lg commented May 7, 2024 •

edited

Loading