-
Notifications
You must be signed in to change notification settings - Fork 354
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
Authorization expiration(?) #882
Comments
Yes, sorry, if you set your app in the OAuth consent screen to Testing, the validity of refresh tokens is limited to one week. I don't think there is a workaround. |
Dear Alessandro, Thank you very much for your reply. This explains the behaviour and gives me the option of changing how things work. best wishes, 'ö-Dzin |
It looks like you can use production mode without Google verification. See rclone/rclone#7963 |
I just encountered the expiration for the first time. When I went to move the credential into Production, as recommended above, Google provided this confirmation box:
... Update ... this seems to have worked. I couldn't access the mountpoint until I forced reauthentication via browser (and Google gave me the 'this app has not been verified by Google', but allowed to to proceed if I was willing to be unsafe). I deleted the whole ... |
From time to time (approximately weekly) my drives fail to mount. I have to remove them, recreate them and reauthorize them, and then they're fine for a while.
The expiration may depend on time or usage (I'm not sure).
I'd like to be able to diagnose the problem and if possible to set these drives so that they don't expire.
Has anyone else seen this issue? Do you have any ideas or solutions?
Many thanks,
'ö-Dzin
The text was updated successfully, but these errors were encountered: