johandebeurs / alfred-mstodo-workflow

Fast task entry, searching and completion for Microsoft Todo via Alfred 4/5
MIT License
138 stars 4 forks source link

Unable to complete authentication after full reset #22

Closed jwvdm closed 3 years ago

jwvdm commented 3 years ago

Thank you for your work on this project!

This workflow was working great for some time and, as others have reported, recently stopped working. To debug, I decided to do a full reset by executing the command _td-full-reset. I was hoping this would allow me to redo the authentication, but unfortunately authentication is not working after the reset.

I'm on MacOs 10.15.7 using Alfred 4.3 and Microsoft ToDo v0.1.2. Debugging output below

[15:08:20.134] Logging Started...
[15:08:23.670] Microsoft ToDo[Script Filter] Queuing argument ''
[15:08:24.088] Microsoft ToDo[Script Filter] Script with argv '(null)' finished
[15:08:24.091] STDERR: Microsoft ToDo[Script Filter] .
2021-01-14 15:08:24,014 root         DEBUG    loading cached data: /Users/janwillem/Library/Caches/com.runningwithcrayons.Alfred/Workflow Data/com.johandebeurs.alfred.mstodo/__workflow_latest_version.cpickle
2021-01-14 15:08:24,014 mstodo       INFO     Workflow response complete
2021-01-14 15:08:24,014 workflow     DEBUG    set last run version: 0.1.2
2021-01-14 15:08:24,015 workflow     DEBUG    ---------- finished in 0.034s ----------
[15:08:24.092] Microsoft ToDo[Script Filter] <?xml version="1.0" encoding="utf-8"?>
<items><item valid="yes"><title>Please log in</title><subtitle>Authorise Alfred ToDo Workflow to use your Microsoft account</subtitle><icon>icons/dark/account.png</icon></item><item autocomplete="-help " valid="no"><title>Having trouble?</title><subtitle /><icon>icons/dark/help.png</icon></item><item autocomplete="-about " valid="no"><title>About</title><subtitle>Learn about the workflow and get support</subtitle><icon>icons/dark/info.png</icon></item></items>
jwvdm commented 3 years ago

Immediately after posting this report, I tried one more time, and somehow this time the "Please log in" notice appeared this time around. I then had to to do the login twice (it did not work the first time around apparently with as similar error as #20). Not quite sure what is happening, but this is working once again on my system!