Open cburgard opened 2 years ago
@cburgard, you can try this method. Although it has been getting some problems as of late, it worked for me even after an OS switch. If you get some more weird things, try checking #671 if it's related to tokens, there is a comment on how to fix this at that issue.
Hi @cburgard, keeping this issue in mind a new version was released (v1.1.0
) along with an updated guide. Refer Configure Credentials Guide.
PS: Also, it seems like the AUR package is not in sync with the latest version as it's being maintained by a third-party. So, you may consider other sources.
What went wrong?
I was trying to install and setup the app. However, none of the suggested methods worked out of the box.
Version 1: Creating a device registration via the suggested webpage
I tried to follow the instructions under https://github.com/Melvin-Abraham/Google-Assistant-Unofficial-Desktop-Client/wiki/Setup-Authentication-for-Google-Assistant-Unofficial-Desktop-Client This worked up until the point where the JSON is fed into the client. It would then refuse to continue, the issue being this one here: https://github.com/Melvin-Abraham/Google-Assistant-Unofficial-Desktop-Client/issues/671
Version 2: JSON "Web client (auto created by Google Service)"
I tried to create the JSON using the "Web client" method suggested in the issue mentioned above. This worked in so far as the client would now continue to the OAuth step. However, upon trying to obtain the code from the OAuth link, the Browser would leave me with this message:
This persisted across multiple browsers and devices.
Version 3: Console method
In an act of desparation, I followed the instructions here: https://developers.google.com/assistant/sdk/reference/device-registration/register-device-manual
The
pip install
command left me with this message:However, I decided to continue anyway, first passing the JSON obtained in the previous step (Version 2). This left me with this message:
Version 4: Native web application
Following the link provided there, I was able to create a JSON file and download it. I would again perform the OAuth step using the "Console method" of calling "google-oauthlib-tool", and this time, it would succeed to the point where it would try and display the code.
However, the webpage displaying the code was just an empty directory listing of
localhost
, but fortunately, the code was displayed as part of the URL (code=ABCDEF...
)With this, I was finally able to authenticate my Google Assistant
What did you expect to happen?
The documentation should contain viable instructions how to register the app.
Please either fix the implementation or update the README.
Steps to reproduce the bug
Follow the instructions on the README to register a new installation on archlinux (using the
google-assistant-unofficial-desktop-client-bin
package from the AUR).App Version
Built from source
OS Version
Archlinux
Relevant Assets
No response
Pre-submission Checklist