Closed davecahill closed 8 years ago
Thank you for including all of that info, this is not something that I have seen before. It is clear that the background server receives the request from your browser after logging in to Wunderlist, but maybe the URL is not what it expected.
First, please try copying the localhost URL from your browser into the workflow's login help screen. When you press return it will validate that URL – if it works you will be logged in but if it does not the error log might show something else to help track this down.
First, please try copying the localhost URL from your browser into the workflow's login help screen. When you press return it will validate that URL – if it works you will be logged in but if it does not the error log might show something else to help track this down.
This did the trick - turned out to be a silly firewall issue. Debug logs showed "host not found" for www.wunderlist.com, which seemed weird since I could hit than in my browser. Sounded like a firewall issue, so I checked - turns out my firewall (Little Snitch) had just updated, but was in some strange state pending a restart, so wasn't warning when it denied connections. After a restart, the workflow is working great.
Feel free to close this - I won't close it myself in case you want to use it to track adding a warning message when the server can't reach Wunderlist (that's probably a rare case :)). Thanks very much for the quick reply!
Thank you, I appreciate the follow-up and am glad you figured it out!
Steps:
Debug info
Obtained by clicking bug icon in Alfred and logging all information. Username replaced with "***".
Python version checked on command line:
OSX version: El Capitan, 10.11.5
Debug output copied from Alfred preferences: