All plugins fail to start in Xcode 5.0.2 on OS X 10.8.5.

[azav]

Console reports:
Reason for Failure: *** -[NSArrayM insertObject:atIndex:]: object cannot be nil.

Any ideas on this one?

The thing I want most in Xcode is to turn off the damned idiotic animations when opening/closing the nav/info panels and when expanding/collapsing the project folder content.

Thanks for putting this together.

[tom-seddon]

Thanks for the feedback, and sorry you're having difficulty. Are you definitely building with the Build All Fixins target? Can you supply a full console log? Sorry not to have a better answer straight away, but nothing in the fixins calls insertObject:atIndex:, so I'm not immediately sure where to start on this one...

--Tom

[azav]

Hi Tom. I just tried again under two Macs under 10.8.5 and Xcode 5.0.2. On one, I set the build targets to 10.8 and the other, I left them at 10.9. In both cases, a build all works as your docs indicate except for CustomizeWarnings, which fails to build since it can't find the DVTKit framework.

Plugins are installed into the proper directory.
However, on a relaunch, the show/hide animations for the Navigator and Utilities are not disabled. The panel still slides in and slides out as it always has when pressing command 1, command 0. There is also no new "Hide Distractions" menu item in the View menu.

The error for every plugin is this:
Failed to load plugin at: ... skipping. Reason for failure: *** -(__NSArrayM insertObject:atIndex:]: object cannot be nil

On the other computer where I set the build targets to 10.8, the error message indicates the missing DVTKit framework.

3/4/14 12:24:01.885 PM Xcode[1074]: [MT] PluginLoading: Required plug-in compatibility UUID 37B30044-3B14-46BA-ABAA-F01000C27B63 for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/XCFixin_FindFix.xcplugin' not present in DVTPlugInCompatibilityUUIDs

Also, I have code that you may enjoy that disables the rollout of contents within NSOutlineViews that you may wish to add to this project.

http://stackoverflow.com/questions/22116527/disable-roll-out-animation-for-nsoutlineview

Any help in resolving this would be appreciated.

[tom-seddon]

I don't have a fix for the plugins not loading, but I have pushed WIP Xcode 5.1 support to the xcode_51_arc branch, so if you have Xcode 5.1 you could try that instead. This works for me with Xcode 5.1 from the app store.

(I saw your post on xcode-users about getting Xcode 5.1 from the developer site - I don't know if that build is somehow different. I'm no longer an iOS developer, so I've just been getting Xcode 5 from the app store.)

The build issue at least could be fixed in the xcode_51_arc branch; the reference to the DVTKit framework was via a relative path. I've changed this to an absolute path, which should fix things, but do note you now need to have Xcode installed in /Applications/Xcode.app. Not sure there's any way around that.

--Tom

[azav]

On building all in Xcode 5.1, I get an error in XCFixin_CustomizeWarningErrorHighlights

ld: warning: directory not found for option '-F/Applications/Xcode.app/Contents/SharedFrameworks'
ld: framework not found DVTKit

All plugins do not load because of a DVTPlugincompatability error with a UUID.

3/13/14 9:19:08.406 AM Xcode[41668]: [MT] PluginLoading: Required plug-in compatibility UUID A2E4D43F-41F4-4FB9-BB94-7177011C9AED for plug-in at path '/Library/Application Support/Developer/Shared/Xcode/Plug-ins/XCFixin_UserScripts.xcplugin' not present in DVTPlugInCompatibilityUUIDs
3/13/14 9:19:08.407 AM Xcode[41668]: [MT] PluginLoading: Required plug-in compatibility UUID A2E4D43F-41F4-4FB9-BB94-7177011C9AED for plug-in at path '/Library/Application Support/Developer/Shared/Xcode/Plug-ins/XCFixin_TabAcceptsCompletions.xcplugin' not present in DVTPlugInCompatibilityUUIDs
3/13/14 9:19:08.408 AM Xcode[41668]: [MT] PluginLoading: Required plug-in compatibility UUID A2E4D43F-41F4-4FB9-BB94-7177011C9AED for plug-in at path '/Library/Application Support/Developer/Shared/Xcode/Plug-ins/XCFixin_InhibitTabNextPlaceholder.xcplugin' not present in DVTPlugInCompatibilityUUIDs
3/13/14 9:19:08.409 AM Xcode[41668]: [MT] PluginLoading: Required plug-in compatibility UUID A2E4D43F-41F4-4FB9-BB94-7177011C9AED for plug-in at path '/Library/Application Support/Developer/Shared/Xcode/Plug-ins/XCFixin_HideDistractions.xcplugin' not present in DVTPlugInCompatibilityUUIDs
3/13/14 9:19:08.410 AM Xcode[41668]: [MT] PluginLoading: Required plug-in compatibility UUID A2E4D43F-41F4-4FB9-BB94-7177011C9AED for plug-in at path '/Library/Application Support/Developer/Shared/Xcode/Plug-ins/XCFixin_FindFix.xcplugin' not present in DVTPlugInCompatibilityUUIDs
3/13/14 9:19:08.411 AM Xcode[41668]: [MT] PluginLoading: Required plug-in compatibility UUID A2E4D43F-41F4-4FB9-BB94-7177011C9AED for plug-in at path '/Library/Application Support/Developer/Shared/Xcode/Plug-ins/XCFixin_DisableAnimations.xcplugin' not present in DVTPlugInCompatibilityUUIDs
3/13/14 9:19:08.412 AM Xcode[41668]: [MT] PluginLoading: Required plug-in compatibility UUID A2E4D43F-41F4-4FB9-BB94-7177011C9AED for plug-in at path '/Library/Application Support/Developer/Shared/Xcode/Plug-ins/XCFixin_CustomizeWarningErrorHighlights.xcplugin' not present in DVTPlugInCompatibilityUUIDs
3/13/14 9:19:08.413 AM Xcode[41668]: [MT] PluginLoading: Required plug-in compatibility UUID A2E4D43F-41F4-4FB9-BB94-7177011C9AED for plug-in at path '/Library/Application Support/Developer/Shared/Xcode/Plug-ins/XCFixin_CurrentLineHighlighter.xcplugin' not present in DVTPlugInCompatibilityUUIDs

[azav]

It appears that the plugins not loading are because of this problem.
Each build of Xcode has its own UUID. The DVTPlugInCompatibilityUUIDs (can't find anything on it in the docs) needs UUID A2E4D43F-41F4-4FB9-BB94-7177011C9AED which apparently is Xcode 5.1's UUID.

However, when attempting to add this UUID to the info.pList for the plugin, Xcode 5.1 crashes on launch inside loadPluginBundle

Here is how I added the UUID to the info.pList:

DVTPlugInCompatibilityUUIDs

A2E4D43F-41F4-4FB9-BB94-7177011C9AED

[tom-seddon]

Interesting, thanks. I'll have to see what UUID my App Store copy has.

Regarding the build errors, where do you have Xcode installed? Is it not in /Applications/Xcode.app? Wherever it is, did you put it there yourself, or did the App Store put it there for you?

--Tom

[azav]

AHA. I dragged it in from the .dmg. It's build # (5B130a). I generally have multiple versions of Xcode in my Applications folder and I add the version number to the end of the file name. I'll change it back to Xcode. When I change the UUID to the proper one for each version of Xcode and build the plugin, I am getting a instant crashes when Xcode launches due to trying to read from an unmappable portion of memory. I'll try rebuilding and launching with Xcode 5.1's name changed back to Xcode first.

[azav]

Crashes on launch, so this means the plugin actually loads, but here is the crash.

Thread0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x00007fff86c32498 objc_msgSend_vtable3 + 24
1 com.apple.Foundation 0x00007fff88a5b307 -[NSBundle loadAndReturnError:] + 646
2 com.apple.Foundation 0x00007fff88a5b07c -[NSBundle load] + 19
3 com.apple.Xcode.DevToolsCore 0x0000000108ec8410 -[XCPluginManager loadPluginBundle:] + 479
4 com.apple.Xcode.DevToolsCore 0x0000000108ec7e17 -[XCPluginManager findAndLoadPluginsInDomain:] + 4302

[tom-seddon]

So just to be clear, does that crash occur when you've used /Applications/Xcode.app to build the fixins, and then run /Applications/Xcode.app to use them?

As for versions and UUIDs, my Xcode.app is the same: Version 5.1 (5B130a), and the UUID is A2E4D43F-41F4-4FB9-BB94-7177011C9AED.

You shouldn't need to insert the UUID anywhere, but I've now noticed that the UUID setup - see the Xcode5 Compatibility Script build phase of the Build All Frameworks target - which I didn't examine terribly closely at the time - relies on Xcode being in /Applications/Xcode.app. I hadn't noticed this before as I've had Xcode 5 as Xcode.app and Xcode 4 as Xcode4.app, and Xcode4 just doesn't check the UUIDs.

I suspect this won't be the last time a fixin will need to get a framework from Xcode.app, and I suppose the UUID thing will stick around too. So the end result, to be confirmed, will probably be that the fixins will just require that you have Xcode in /Applications/Xcode.app.

--Tom

[azav]

OK. I've redownloaded the 5.1 fork, made sure I launch from Xcode 5.1 named Xcode.app, rebuilt all plugins as 64 bit, quit Xcode, relaunched and Xcode crashes on startup in the plugin load routines with a SIGSEV just as before. FYI, I'm on 10.8.5, as opposed to 10.9.x.