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

Invalid grant #65

Closed
bmihaljevic opened this issue Feb 18, 2016 · 8 comments
Closed

Invalid grant #65

bmihaljevic opened this issue Feb 18, 2016 · 8 comments

Comments

@bmihaljevic
Copy link

Hi,

I now get the following error when trying to sync.

Failed to refresh auth token: HTTP 400, body: {
"error" : "invalid_grant"
}
exception: /home/bmihalje/Downloads/grive2/libgrive/src/protocol/OAuth2.cc(116): Throw in function void gr::OAuth2::Refresh()
Dynamic exception type: boost::exception_detail::clone_implgr::OAuth2::AuthFailed
[gr::expt::BacktraceTag*] = #0 0x51c88a :0 gr::Exception::Exception()
#1 0x4feadd :0 gr::OAuth2::AuthFailed::AuthFailed()
#2 0x4fe76c :0 gr::OAuth2::Refresh()
#3 0x4fd5a6 :0 gr::OAuth2::OAuth2(gr::http::Agent*, std::string const&, std::string const&, std::string const&)
#4 0x4b52c3 :0 Main(int, char**)
#5 0x4b59af :0 main
#6 0x7fc34fc57ec5 /lib/x86_64-linux-gnu/libc.so.6 __libc_start_main
#7 0x4b3ff9 :0 _start

Do you have any ideas what the problem might be?

Thank you.

@redjamesg
Copy link

Last time I saw that, I had to delete the .grive and .grive-status and let it sync all over with the exchange of grant permission.

@vitalif
Copy link
Owner

vitalif commented Feb 18, 2016

Try grive -a

@bmihaljevic
Copy link
Author

Thanks, @redjamesg , that solved it!

I had already been trying with grive -a but that was not fixing it.

@rdh61
Copy link

rdh61 commented Oct 21, 2016

@redjamesg, @bmihaljevic

Where are .grive and .grive-status? Can't find them!

Thank you.

@j0nn0
Copy link

j0nn0 commented Oct 25, 2016

They are created in your base GDrive (wherever you have decided that to be) when you first run grive. So e.g. if your GDrive is ~/GoogleDrive, then when you run grive -a you must first cd to ~/GoogleDrive and run it from there (in terminal.) Then, you will find .grive and .grive-status there. You must be owner of the GDrive, so best to put it in your home or a partition that you own. Do you have the latest stable version? Maybe recompile/reinstall.

@rdh61
Copy link

rdh61 commented Oct 28, 2016

Thank you @j0nn0. I deleted those two files (.grive and .grive-status), ran grive -a, and now grive is working for me again.

@tscloud
Copy link

tscloud commented Oct 31, 2016

I have a similar situation but slightly different stack trace. Running version:
grive version 0.5.1-dev Oct 13 2016 12:07:36
I do not have .grive-status but do have .grive-state. Should I delete .grive and .grive-state?

@savanna
Copy link

savanna commented Apr 2, 2019

I ran into the same issue. I only removed .grive file and re-run grive -a that fixed the problem. Still curious why it didn't work without removing .grive file though.

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

7 participants