Skip to content
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

Error: Getting metadata from plugin failed with error: invalid_grant #58

Closed
ozgurgulsuna opened this issue Jan 3, 2021 · 9 comments
Closed

Comments

@ozgurgulsuna
Copy link


You are Offline!
Please check your Internet Connection...
Error: Getting metadata from plugin failed with error: invalid_grant

This is the error I get when I try to interact with it.


Here is the console output

[ozgur@ozgur ~]$ g-assist
Gtk-Message: 01:47:27.764: Failed to load module "colorreload-gtk-module"
WARNING: Kernel has no file descriptor comparison support: Operation not permitted
(node:2768) Electron: Loading non-context-aware native module in renderer: '/run/user/1000/snap.g-assist/.org.chromium.Chromium.p0zq7X'. This is deprecated, see https://github.com/electron/electron/issues/18397.
(node:2830) Electron: Loading non-context-aware native module in renderer: '/run/user/1000/snap.g-assist/.org.chromium.Chromium.S8rREt'. This is deprecated, see https://github.com/electron/electron/issues/18397.

Error on DevTools

common.js: line 62 ;
    Auth error:Error: invalid_grant
main.js: Line 492 ;
    Error: 14 UNAVAILABLE: Getting metadata from plugin failed with error: invalid_grant
    at Object.exports.createStatusError (/snap/g-assist/1/res…pc/src/common.js:91)
    at ClientDuplexStream._emitStatusIfDone (/snap/g-assist/1/res…c/src/client.js:233)
    at ClientDuplexStream._receiveStatus (/snap/g-assist/1/res…c/src/client.js:211)
    at Object.onReceiveStatus (/snap/g-assist/1/res…nterceptors.js:1311)
    at InterceptingListener._callNext (/snap/g-assist/1/res…interceptors.js:568)
    at InterceptingListener.onReceiveStatus (/snap/g-assist/1/res…interceptors.js:618)
    at /snap/g-assist/1/res…nterceptors.js:1127

Screenshots
Screenshot_20210104_015326
and
Screenshot_20210104_015503

Desktop

  • OS --> Host: ozgur Kernel: 5.8.11-1-MANJARO x86_64 bits: 64 Desktop: KDE Plasma 5.19.5 Distro: Manjaro Linux
@Melvin-Abraham
Copy link
Owner

@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
Copy link

paperfairy commented Jan 5, 2021

@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

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

@Melvin-Abraham
Copy link
Owner

Melvin-Abraham commented Jan 5, 2021

@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
Copy link

@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
Copy link
Author

@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
Copy link

@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
Copy link

@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
Copy link

@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
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants