Error: Getting metadata from plugin failed with error: invalid_grant about google-assistant-unofficial-desktop-client

[Melvin-Abraham]

@ozgurgulsuna You can fix this by deleting the tokens file that was fetched by the application (as per the "Saved Tokens Path") and relaunch the assistant. You will again be presented with "Get Token!" screen. Authenticate your Gmail account again and let it fetch the tokens. This should possibly fix the issue...

[paperfairy]

@Melvin-Abraham Following these steps doesn't give me a new token, but it gives me a code. Where do we dump this code?

https://i.imgur.com/RA3H1y8.gif

trying to clear the tokens path puts me in an endless loop :(

[Melvin-Abraham]

@paperfairy This was a known issue (see #39). The patch will be released in the next release. For the time being this should help:

Fixed in dd67747. Since, this fix will not be readily available until next release, you can either clone this project and build it yourself or if you do not want to build it yourself, you can temporarily disable Settings > Conversation > Enable microphone on application startup, relaunch assistant and let the assistant save the tokens after which you can enable the setting again.

Ref: #39 (comment)

After following either of these steps, you will be able to continue with the "Get Token" screen without any issue. For additional help with saving the tokens, refer to Guide: Setting authentication in the app

[rodrigoswz]

@ozgurgulsuna You can fix this by deleting the tokens file that was fetched by the application (as per the "Saved Tokens Path") and relaunch the assistant. You will again be presented with "Get Token!" screen. Authenticate your Gmail account again and let it fetch the tokens. This should possibly fix the issue...

I was with the exact same problem, doing that fixed it. Thank you!

[ozgurgulsuna]

@ozgurgulsuna You can fix this by deleting the tokens file that was fetched by the application (as per the "Saved Tokens Path") and relaunch the assistant. You will again be presented with "Get Token!" screen. Authenticate your Gmail account again and let it fetch the tokens. This should possibly fix the issue...

doing that also fixed it for me, thanks a lot !

[kbdharun]

@ozgurgulsuna You can fix this by deleting the tokens file that was fetched by the application (as per the "Saved Tokens Path") and relaunch the assistant. You will again be presented with "Get Token!" screen. Authenticate your Gmail account again and let it fetch the tokens. This should possibly fix the issue...

Thanks, Sorry I didn't know this was already there, and I am Extremely Sorry for Duplicate Comment.

[Mantej-Singh]

@ozgurgulsuna You can fix this by deleting the tokens file that was fetched by the application (as per the "Saved Tokens Path") and relaunch the assistant. You will again be presented with "Get Token!" screen. Authenticate your Gmail account again and let it fetch the tokens. This should possibly fix the issue...

Thank you so much for porting this app on windows and also for a fix for "You are Offline!" issue

[CyanoTex]

@paperfairy This was a known issue (see #39). The patch will be released in the next release. For the time being this should help:

Fixed in dd67747. Since, this fix will not be readily available until next release, you can either clone this project and build it yourself or if you do not want to build it yourself, you can temporarily disable Settings > Conversation > Enable microphone on application startup, relaunch assistant and let the assistant save the tokens after which you can enable the setting again.

Ref: #39 (comment)

After following either of these steps, you will be able to continue with the "Get Token" screen without any issue. For additional help with saving the tokens, refer to Guide: Setting authentication in the app

PLEASE do not have your window behavior settings to Close on Blur. It can become extremely irritating when the issue pops up.

[anuragdandge]

how long do we have to wait after putting that code in "Get Token " Window ?