awaldraff Posted September 21, 2016 Share Posted September 21, 2016 Installed Sierra last night. None of my workflows are working anymore. Is there a compatibility issue? Link to comment
FroZen_X Posted September 21, 2016 Share Posted September 21, 2016 I have been using Alfred 3 with the first Public beta for sierra and haven't had any issues. Were you on Alfred 3 before or did you also update from Alfred 2? Gotta have to know some more. What exactly doesn't work, how does it show etc.? Link to comment
willbraden Posted October 14, 2016 Share Posted October 14, 2016 I too am having issues. My issues include not passing through data while the notifications say they do, and providing live results from websites on some workflows while not on other workflows. I upgraded from Alfred 2 before I upgraded to Sierra. Link to comment
Vero Posted October 14, 2016 Share Posted October 14, 2016 @willbraden and @awaldraff Could you give one particular example, as suggested by @FroZen_X? Perhaps include a link to the workflow? Some workflows simply need a little update to say they refer to Alfred 3 instead of Alfred 2, while others may be relying on deprecated APIs or sources to present results. The more details you can provide, the easier it will be for us to help but broadly, workflows from Alfred 2 will work just fine in Alfred 3 without any changes. Cheers, Vero Link to comment
Stefan64 Posted January 3, 2017 Share Posted January 3, 2017 I'm having issues too: The workflows don't appear to be broken, the just never get called: it seems like the websearch always gets the precedence over a recognized workflow: e.g. radd some reminder should call the reminder-workflow: it also shows up in the quick-list up to the rad - but when it is completed, it gets replaced by the websearch and hitting return then searches for radd some reminder in google. I upgraded to Sierra on the week, had no issues previously with any of the workflows. PS: Adding a comment/log-entry to a workflow confirms, that the workflow is never called and the entries get intercepted by the websearch. Link to comment
Stefan64 Posted January 3, 2017 Share Posted January 3, 2017 okok, and I take everything back: This behavior occurs when the workflow is broken and exits with an error - and this is exactly what happened to some of the workflows that depend on mac-os-apps that changed under sierra, like notes and reminders. I still wished that there was some place in Alfred where we could see that the workflow throws errors - this way, Alfred just silently chews up the error and falls back to websearch... Link to comment
dfay Posted January 3, 2017 Share Posted January 3, 2017 You mean like the workflow debugger? Stefan64 1 Link to comment
Stefan64 Posted January 3, 2017 Share Posted January 3, 2017 yeah, right, should have known better, thank you! dfay 1 Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now