-
Hi, I'm trying to use my own OAuth 2.0 JSON secret, but Is there a way to force re-authentication? Below is the output: tw_gtasks_sync --tw-filter "pending" -l "Dom's To-Do list" --google-secret ~/.config/gtasks_secret.json
11:49:19.68 | INFO | Loading preferences...
11:49:19.69 | INFO | Loading preferences...
11:49:19.69 | INFO | Caching this configuration under the name - Dom%27s%20To-Do%20list__pending__None__.yaml...
11:49:19.69 | INFO |
Configuration:
===============
- TW Filter : pending
- TW Tags : ()
- TW Project : None
- TW Sync All Tasks : False
- Google Tasks : Dom's To-Do list
- Prefer scheduled dates: False
11:49:19.69 | INFO | Loading preferences...
11:49:19.69 | INFO | Using already cached credentials...
11:49:19.83 | INFO | Initializing Taskwarrior...
11:49:19.98 | INFO | Detecting changes from Gtasks...
11:49:19.98 | INFO | Detecting changes from Tw...
11:49:19.98 | WARNING |
Google Tasks
------------
* Items created: 0
* Items updated: 0
* Items deleted: 0
Taskwarrior
-----------
* Items created: 0
* Items updated: 0
* Items deleted: 0
11:49:19.98 | SUCCESS | Sync completed successfully. You can now use the -b/--combination option to refer to this particular combination
tw_gtasks_sync --combination Dom%27s%20To-Do%20list__pending__None__.yaml Thanks! |
Beta Was this translation helpful? Give feedback.
Answered by
shymega
Aug 22, 2024
Replies: 1 comment
-
Fixed. The solution is to delete |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
shymega
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Fixed. The solution is to delete
$HOME/.gtasks_credentials.pickle
.