Closed drscotthawley closed 2 years ago
Ok, well, ultimately I just created a new OAuth Client ID and switched to that, and everything works again, no problems.
Wondering if I'll need to repeatedly create a new Client ID every month?
...in any case, feel free to close this issue for now if you like.
Dear Ivan (et al), Thank you for creating such a helpful tool. I have some code that used to work in back October, but now that I'm re-running it on the same computer, in the same environment, with no changes to the code, I'm getting an error when I try to call
FetchMetaData()
. For example,Output log looks like:
The only change I can think of -- and I mention this because I noticed threads elsewhere about oauth2 failing if the system time is not correct -- is that I wrote the code & generated the credentials at home in Central time zone, and I'm currently travelling and running the code in Pacific time zone.
BUT: I just forced an system time update with via
sudo service ntp stop; sudo ntpdate time.nist.gov
..and I still get the same error as above.Do you have any suggestions for getting around this? Thanks!
PS- My
settings.yaml
file reads as:Update: Ok I notice that even though my
credentials.json
file is brand-new after running the scripts(s), it contains a field that reads"token_expiry": "2021-10-13T18:09:06Z"
. But I wasn't aware of having created any expired credentials. When I check my Drive API dashboard, my credentials don't say anything about an expiration date. (?)