:  ~ 1 min read

It all started with this post by Joe for updating a plug-in from the terminal, which lead to this script for automating the process of updating all plug-ins.

Even though I could have created an Alfred workflow to easily run the script with a single command, I always wanted to start working on Mac apps, so this was a good opportunity to get my feet wet.

I said I'll give open source by default a try, but I also wanted to have it on the MAS for a little while before that, just to have a feel about how the process goes, so I submitted it. It was rightfully rejected: no matter how foolproof I'd make it, it would never assure that it won't break Xcode - it's at the user's discretion if he takes the risk to update his plug-ins or not (if one of the plug-ins is no longer compatible with the latest version, it would make Xcode crash on launch), a risk Apple doesn't want to take.

So I tweaked the app to loosen some stuff up, like sandbox removal, and I uploaded it on GitHub. If you have any suggestions, be it for a feature, or on improving the code, I'd be more than happy to have a chat @rolandleth or at

Short description:

PlugRocket is a simple app that adds Xcode's UUID to each of your plug-ins Info.plist's compatibility list. This means Xcode will see them as compatible and load them, but this does not mean they are guaranteed to also work; no updates for the plug-ins are downloaded and installed.

If a plug-in will cause Xcode to start crashing after using PlugRocket, you can use the revert function: you can either undo all the changes, or only select the plug-ins that are causing the crash.