Input/Output error with valid Drive API Access

[matiasw]

Hi,
I'm having a problem similar to #237 and #310 , except, as far as I can tell, not for the same cause: these were because of a disabled Google Drive API Access, whereas my Drive API shows "Status Enabled" in the Google Cloud Console Project Metrics for the project I've created.
So, the google-drive-ocamlfuse was working fine, until this happened. I tried removing the config and and running google-drive-ocamlfuse -id [...] -secret [...] again, but it didn't help.

There is

[203.634170] curl: data in: {
  "error": "invalid_grant",
  "error_description": "Token has been expired or revoked."
}

in curl.log, but I can't fathom why, as the OAuth token of the project seems valid in the Cloud Console, and the client secret has "Status Enabled" also.

I tried creating a new OAuth token on Google Cloud console in the same way as worked the first time, but this time, I am getting "Input/Output error" on the mounted drive after deleting configuration and re-creating with this new token, which leads me to think this might be a problem with google-drive-ocamlfuse. I am using version 0.7.30.

Frankly, this may still be an error on my part with the Google Cloud services, but since simply creating a new token did not work and Google provides no support, I would greatly appreciate if someone would please help me resolve this issue.

[astrada]

I suggest upgrading to the latest version (0.7.32), and removing everything stored under ~/.gdfuse/default (at least the state file that stores the refresh token).

[matiasw]

I suggest upgrading to the latest version (0.7.32), and removing everything stored under ~/.gdfuse/default (at least the state file that stores the refresh token).

Ok - I don't know whether it was removing the .gdfuse directory or upgrading to 0.7.32 (which I should've tried before making this issue - sorry!), but the issue seems resolved for now. Thank you!

[greg7mdp]

Ok - I don't know whether it was removing the .gdfuse directory or upgrading to 0.7.32

It was probably removing the .gdfuse directory. I had the same issue and I was already on 0.7.32. Removing ~/.gdfuse/default didn't help. However removing .gdfuse caused chrome to ask me for the permissions again and all was good.

[matiasw]

I am re-opening this issue, because it has reappeared for me. Yes, removing .gdfuse and re-doing the auth process helped, again, but this is an unsustainable workaround.