neilmiddleton

And cause untold issues for anyone doing anything else with Ruby.

Got it now, thanks. So, for posterity, there's two things here. Firstly you need to include the Ruby 2.0.0 gems as well as 1.8 for pre-mavericks installs, and then you need to respect the different encoding that Alfred seems to run with Ruby scripts (as per Clinton's response).

Can I confirm that this is the only change that you made to the workflow? I just did a fresh install of it from https://github.com/neilmiddleton/alfred-devcenter-search/raw/master/Heroku%20DevCenter%20Search.alfredworkflow and made that one change, but no cigar.

Yeah, that's odd, but at the moment it doesn't look like Alfred is even hitting the workflow script. I wonder if usage of Ruby workflows is just low.

I'm becoming less convinced that this is a Ruby problem at all, but an Alfred / Mavericks problem. If I run my Ruby script directly using the same path/command as Alfred it works fine. However, from Alfred it immediately fails silently as described earlier in this thread. If I go one step further and modify the workflow itself, for instance flip it to try and run the Ruby script with Python, I see exactly the same behaviour, and still nothing in the logs. It seems that Alfred is immediately failing the execution of the script and not logging anything to the Alfred-Workflow.log.

So, I suspect there is a couple of things at play here. I was able to modify my workflow so that it worked successfully via the command line calling the script directly. To do this I had to re-bundle so that the path for Ruby 2.0.0 was correct. However, it still fails as described via Alfred, again putting nothing in the logs.

I'm seeing similar issues with Workflows. My workflow (here) worked fine before mavericks, now does nothing, and doesn't yield anything in the logs.