-
Notifications
You must be signed in to change notification settings - Fork 400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get Token/Code UI incorrectly tries to load localhost #684
Comments
This is most likely the answer: #683 (comment) |
Definitely can be a duplicate of #682 My searching didn't find that one guess I forgot to try "local host" vs "localhost" 🤦♂️ |
Is it fixed? |
fixed? |
I found the fix 😄 |
Copying the code from the URL worked for me as well. I was stuck for a minute there. Thanks. |
Me too, I was stuck on it for a while and I made a GitHub account just to give you my thanks. |
hey guys plz help out which code to be copied from url |
I have fixed this error on my installation simply changing the protocol from https to http at this point of the installation guide:
To: http://localhost:5754/auth/handler Hope it will help somebody! |
Worked For me was stuck on this on local host thing |
What went wrong?
After following the Setup Authentication Guide there was an error loading the Get Token experience which went to load localhost (of which there is no local web server running).
url:
http://localhost/?code=<valid-code-to-copy>&scope=https://www.googleapis.com/auth/assistant-sdk-prototype
What did you expect to happen?
The above was the expectation from the setup guide, but there was no UI for selecting/copying the token. Though I've done one of these consent apps before and knew that the URI parameter was correct and valid to copy into the Google Assistant Desktop client successfully.
Steps to reproduce the bug
Follow the instructions in https://github.com/Melvin-Abraham/Google-Assistant-Unofficial-Desktop-Client/wiki/Setup-Authentication-for-Google-Assistant-Unofficial-Desktop-Client (making sure to download the
.json
credentials file a second time (as per the other issue reported -> #671App Version
v1.0.0
OS Version
MacOS 12.3
Relevant Assets
Based on the conversation in a few other issues I've decided to open a new one tracking this specific aspect to the authentication process / token generation.
#671 (comment)
#342 (comment)
Pre-submission Checklist
The text was updated successfully, but these errors were encountered: