I am having trouble syncing with my google drive account from grive running on Ubuntu 14.04. I have never had problems previously. I tried purging drive from my system and deleting all local folders, but still come up with this when I try to run grive after reinstalling.
user@user-OptiPlex-780:~/drive$ grive
grive: Symbol `json_tokener_errors' has different size in shared object, consider re-linking
Reading local directories
Synchronizing folders
exception: /build/buildd/grive-0.2.0/libgrive/src/http/CurlAgent.cc(149): Throw in function long int gr::http::CurlAgent::ExecCurl(const string&, gr::http::Receivable*, const gr::http::Header&)
Dynamic exception type:boost::exception_detail::clone_impl<gr::http::Error>
std::exception::what: std::exception
[gr::expt::MsgTag*] =
[gr::http::CurlCodeTag*] = 0
[gr::http::HttpResponseTag*] = 400
[gr::http::UrlTag*] = https://docs.google.com/feeds/default/private/full/-/folder?max-results=50&showroot=true
[gr::http::HeaderTag*] = Authorization: Bearer ya29.WwFOho3OkmkxFIdn86HBbtpSIyBYDzDgQua1K6JcEu7kCBLgvY1aEiUHCZlSCuli_qPHkTfNZLhDfQ
GData-Version: 3.0
Here is a link to a google developers page that suggests that the API has changed today link. could that be an issue?
Best Answer
Yes, Grive is using the defunct Documents List API. As of around 9AM PST we stopped serving these API requests. This is why the Grive client is receiving '400 Bad Request' responses.
Looking at the project, it appears to be unmaintained for almost a year and definitely hasn't been updated (here & here) to the new API that was released in 2012 when Documents List was officially deprecated.