This repository has been archived by the owner on Apr 19, 2023. It is now read-only.
"gdrive about" results in error #257
Comments
saaros
added a commit
to saaros/gdrive
that referenced
this issue
Feb 14, 2017
Commit b33b3e9 introduced a bug where we try to read a token file even if it doesn't exist, causing unauthenticated run (e.g. `gdrive about`) to fail with the error Failed getting oauth client: Failed to read token: unexpected end of JSON input Closes prasmussen#257.
saaros
added a commit
to saaros/gdrive
that referenced
this issue
Feb 14, 2017
Commit b33b3e9 introduced a bug where we try to read a token file even if it doesn't exist, causing unauthenticated run (e.g. `gdrive about`) to fail with the error Failed getting oauth client: Failed to read token: unexpected end of JSON input Closes prasmussen#257.
|
I am getting the same error. |
|
I was getting the same error, you can fix it with the patch from saaros's pull request until the devs accept it. |
fabzo
pushed a commit
to fabzo/gdrive
that referenced
this issue
Aug 6, 2017
Commit b33b3e9 introduced a bug where we try to read a token file even if it doesn't exist, causing unauthenticated run (e.g. `gdrive about`) to fail with the error Failed getting oauth client: Failed to read token: unexpected end of JSON input Closes prasmussen#257.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is the error that I got,
Failed getting oauth client: Failed to read token: unexpected end of JSON inputAlso .gdrive folder is not created in the home directory.
I am using "Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-62-generic x86_64)"
The text was updated successfully, but these errors were encountered: