Tatsh
commented
4 years ago The original app may be dead (this code hasn't seen an update since February). In any case, you should create your own app and get its client ID and secret, as stated in the README.
So, is this because the default application id has run out of transfer quota or something?
According to Google on the browser side, I was able to pass authentication, but actually trying to sync anything dies with,
`Failed to refresh auth token: HTTP 400, body: { "error": "invalid_grant", "error_description": "Bad Request" } exception: /build/grive2-g1y2_j/grive2-0.5.2/libgrive/src/protocol/OAuth2.cc(111): Throw in function void gr::OAuth2::Refresh() Dynamic exception type: boost::exception_detail::clone_impl
[gr::expt::BacktraceTag*] = #0 0x5601511a83db grive gr::Exception::Exception()
1 0x56015118b065 grive gr::OAuth2::AuthFailed::AuthFailed()
2 0x56015118ace2 grive gr::OAuth2::Refresh()
3 0x56015118a034 grive gr::OAuth2::OAuth2(gr::http::Agent*, std::cxx11::basic_string<char, std::char_traits, std::allocator > const&, std:: cxx11::basic_string<char, std::char_traits, std::allocator > const&, std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&)
4 0x560151145458 grive Main(int, char**)
5 0x560151146153 grive main
6 0x7f6bba5fbb97 /lib/x86_64-linux-gnu/libc.so.6 __libc_start_main
7 0x560151143a9a grive _start
`
Tried a couple of times, got fresh auth codes on the browser, but no difference.
Or do I need to include the scope with the token as well? That's not on the token field but I do see that in the page header when getting the token...
I'd suggest a more helpful error message if at all possible.