search

Melvin-Abraham / Google-Assistant-Unofficial-Desktop-Client

A cross-platform unofficial Google Assistant Client for Desktop (powered by Google Assistant SDK)
Apache License 2.0
3.6k stars 403 forks source link

Authentication Failure #671

Closed DanTheTechMan closed 1 year ago

DanTheTechMan commented 2 years ago

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: image 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.

dannytech commented 2 years ago

I was able to fix this by creating a new OAuth Client, and downloading the key from that (rather than using the Web Client key).

lentas1 commented 2 years ago

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.

i tried but not working

lentas1 commented 2 years ago

znoob's help fixed it

lentas1 commented 2 years ago

next time it doesnt work

EmperorMAZE commented 2 years ago

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: image 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.

Same problem. Any solution?

EmperorMAZE commented 2 years ago

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.

it worked for me.. Thanks buddy..

Nivet2006 commented 2 years ago

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: image 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.

Same problem. Any solution?

@X-KRYPTONITE-X Check the following solution by etatus. It works.....

Download the JSON file from Web client credential from [Google API & Services > Credentials] page and use it as the Key File in the client. image

When the client ask you for the code and you get the error "Unable to process request due to missing initial state [....]" in the browser, just copy from the url bar the code under the "code" GET parameter. That is the code you must paste in the client. image

Hope this helps...... 😊

paulsybrandy commented 2 years ago

Out of everything before your post, nothing worked. Your fix however, WORKED! Many thanks my friend!

Nivet2006 commented 2 years ago

Out of everything before your post, nothing worked. Your fix however, WORKED! Many thanks my friend!

@paulsybrandy

Happy to know that my fix worked for you, buddy!!

hedhehd commented 2 years ago

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.

Thank you so much for the help!

zhydkov commented 2 years ago

Ok, that's what I do to solve the problem:

  1. Download the JSON file from Web client credential from [Google API & Services > Credentials] page and use it as the Key File in the client.

image

  1. When the client ask you for the code and you get the error "Unable to process request due to missing initial state [....]" in the browser, just copy from the url bar the code under the "code" GET parameter. That is the code you must paste in the client.

image

thanks

ghost commented 2 years ago

What is the status on this issue?

xor7589 commented 2 years ago

I had that issue too, worked redownloading from console. "token_uri":"https://oauth2.googleapis.com/token" and extra "redirect_uris":["http://localhost"] is only difference

stratile commented 2 years ago

@sumeshir26 please help me... I tried re-downloading the .json file but nothing seems to work image

sumeshir26 commented 2 years ago

@sumeshir26 please help me... I tried re-downloading the .json file but nothing seems to work image

Download the JSON file from Web client credential from [Google API & Services > Credentials] page and use it as the Key File in the client.
hendisama commented 2 years ago

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 very much, I am following the above steps, but in addition, before arrived in "Credentials" you need to click "API.." menu first then afterward it will send one error, but you may copy the code from variable "code=..." in the POST (HTML) message

mewmix commented 2 years ago

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.

freaking legend!!!

SantiagoSinatra commented 2 years ago

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."

image image

Any advice on how to fix it?

laiviettrung commented 2 years ago

Im getting the same error something went wrong

GuyMayer commented 2 years ago

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

Funkeemonkee06 commented 2 years ago

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

gamer564q commented 2 years ago

im getting the same error

im-coder-lg commented 2 years ago

@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 commented 1 year ago

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

Gracias...

WatchTheory commented 1 year ago

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

Worked for me, thanks

Melvin-Abraham commented 1 year ago

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

Melvin-Abraham commented 1 year ago

Closing as resolved

manofthepeople commented 1 year ago

it says when i do this image

ryukinix commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

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.

image

im-coder-lg commented 1 year ago

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

@dash-1-1 have you tried this?

JohnLGalt commented 1 year ago

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."

image image

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 commented 11 months ago

help me i face failed to get tokens

WhiteCat65 commented 7 months ago

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

D4nChen commented 5 months ago

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

I have the same issue.

ak-47-brar commented 4 months ago

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

hey did you got the fix for this

ak-47-brar commented 4 months ago

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: image 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 commented 4 months ago

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

hey did you got the fix for this

I followed this guide and resolved it.

im-coder-lg commented 4 months ago

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 commented 1 month ago

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