How to troubleshoot an unsuccessful workflow import?

[ldavisrobeson]

I'm unable to import a workflow (https://github.com/yannickglt/alfred-devdocs). It opens in Alfred and I get the screen to choose a category for it, but when I click "Import" nothing happens and the workflow doesn't show up in the sidebar (Categories set to "All").

 

I don't know how to troubleshoot why it's not working, since the "toggle debugging mode" option only works for existing workflows.

 

[rice.shawn]

It seems like the first thing to do is to check your workflows directory to see if the workflow was installed. Alfredworkflow files are actually just renamed zip files, and Alfred unzips them into the correct directory. Then, it modifies the info.plist file to migrate hotkeys and keywords (in the note).

 

Depending on how many workflows you've installed, it might take a little while. If you're comfortable using the terminal, then just go to the workflows directory and type

grep -R "Yannick" *

Since "Yannick Galatol" created that workflow, the string should show up in an info.plist file. If it doesn't, then that means that the workflow wasn't unzipped into the directory. If it does, then it might point to a corrupted info.plist file. This might indicate a bug with Alfred.

[Vero]

I'm unable to import a workflow (https://github.com/yannickglt/alfred-devdocs). It opens in Alfred and I get the screen to choose a category for it, but when I click "Import" nothing happens and the workflow doesn't show up in the sidebar (Categories set to "All").

 

I don't know how to troubleshoot why it's not working, since the "toggle debugging mode" option only works for existing workflows.

 

Another step worth taking is to repair permissions on your Mac, as it's possible that OS X is stopping Alfred from being able to write new workflows to the preferences file.. You can do this by launching the Disk Utlity app and choosing "repair permissions".