Fixing Alcatraz after upgrading Xcode

fix_alcatraz_plugins.sh

# Upgrading Xcode can wreak havok on your custom Alcatraz setup.
# Each plugin must list the UUIDs of Xcode that it supports. Thus
# with each new release we must update the list of UUIDs for each
# plugin we want to continue using.
#
# You can discover the UUID of an Xcode app bundle by running this command

defaults read /Applications/Xcode.app/Contents/Info DVTPlugInCompatibilityUUID
# > 7FDF5C7A-131F-4ABB-9EDC-8C5F8F0B8A90

# This string must be added to the `Info.plist` file for each plugin.
# The entry within the plist file looks like this
#
#  ...
#  <key>DVTPlugInCompatibilityUUIDs</key>
#  <array>
#    <string>FEC992CC-CA4A-4CFD-8881-77300FCB848A</string>
#    ...
#  </array>
#  ...
#

# Steps to (hopefully) fix Alcatraz
# First, close Xcode

# Uninstall the Alcatraz plugin
rm -rf ~/Library/Application\ Support/Developer/Shared/Xcode/Plug-ins/Alcatraz.xcplugin

# Add the newest Xcode UUID to all installed plugins
# This will attempt to find all `Info.plist` files and append the 
# Current Xcode UUID to the `DVTPlugInCompatibilityUUIDs` node.
find ~/Library/Application\ Support/Developer/Shared/Xcode/Plug-ins -name Info.plist -maxdepth 3 | xargs -I{} defaults write {} DVTPlugInCompatibilityUUIDs -array-add `defaults read /Applications/Xcode.app/Contents/Info DVTPlugInCompatibilityUUID`

# Reinstall Alcatraz
# This is especially helpful a few days after the release of a new
# Xcode version because the Alcatraz team has most likely updated
# the project to include support for the newest Xcode.
curl -fsSL https://raw.github.com/supermarin/Alcatraz/master/Scripts/install.sh | sh

# Now relaunch Xcode
#
# If this has not worked try perusing the Alcatraz github issues.
# It's likely others are having the same problem. 
# https://github.com/supermarin/Alcatraz/issues