Closed sreeram-dev closed 2 years ago
This is interesting. I haven't had this problem and I've been using the gCal module since the beginning. I wonder if the expires_at
is a new value, and my token has no expiry attached to it?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This is still an issue. What's more interesting, the token.json
as generated by quickstart.py
does not work with wtfutil
. I have the quickstart.py
in ~/.config/wtf/gcal/
, in my config file in gcal section I have
secretFile: "~/.config/wtf/gcal/token.json"
and after removing token.json
, running quickstart.py
, going through the OAuth dance, and running wtfutil
I get
oauth2/google: no credentials found
Which is even more annoying when the token eventually expires and I have to figure out again how to make it work.
What's broken?
Response after completing the oauth2 redirection flow to get google calendar API access token for gcal integration.
Without refresh token in gcal_auth.json, gcal module breaks after sometime. We need to periodically fetch and store the new access token using refresh token.
Workaround
I am presently using
quickstart.py
script to get refresh token and access token, and store it ingcal_auth.json
.