Fixing Xcode CLI builds with broken plugin warnings

I'm a big fan of Carthage, but one issue that had been plaguing me for months was the command line warning messages about my Xcode plugnis not being "compatible".

It rather clutters up the Terminal.

It rather clutters up the Terminal.

PluginLoading: Required plug-in compatibility UUID ACA8656B-FEA8-4B6D-8E4A-93F4C95C362C for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/Xcode_beginning_of_line.xcplugin' not present in DVTPlugInCompatibilityUUIDs

etc.

This post gives some good relief - you just pipe a script straight from the 'net straight to sh (🙃) - , allowing Xcode to now recognise all my plugins properly (which were actually working in the Xcode app, but apparently not at the command line) but it revealed that one plugin was broken, the excellent FuzzyAutocomplete:

WARNING: Failed to load plugin at path: "/Users/ian/Library/Application Support/Developer/Shared/Xcode/Plug-ins/FuzzyAutocomplete.xcplugin", skipping. Error: Error Domain=NSCocoaErrorDomain Code=3588 "dlopen(/Users/ian/Library/Application Support/Developer/Shared/Xcode/Plug-ins/FuzzyAutocomplete.xcplugin/Contents/MacOS/FuzzyAutocomplete, 265): Symbol not found: OBJC> CLASS_> $_DVTTextCompletionInlinePreviewController

I guess I hadn't noticed it was broken, so for now I'll just remove it.

Much better!

Much better!