Xcode 6 won't start (OS X 10.9.4)

Question

Recently, within the last few days, whenever I try to open Xcode6-Beta2 on my 2013 11\" MacBook Air running OS X 10.9.4, I get a problem report and Xcode won\'t run. I tried uni

Answer 1

I was using Xcode6-Beta3 fine up until today when I updated to 10.9.4. Now I get the same error, the interesting part of which is:

Application Specific Information: dyld: launch, loading dependent libraries

Dyld Error Message: Symbol not found: _OBJC_CLASS_$_LSApplicationProxy Referenced from: /System/Library/PrivateFrameworks/PlugInKit.framework/Versions/A/PlugInKit Expected in: /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices in /System/Library/PrivateFrameworks/PlugInKit.framework/Versions/A/PlugInKit

I have filed a bug with Apple regarding this issue.

Answer 2

XCode 6 GM wasn't opening for me either, no matter how long I waited. I've seen this behavior before and it's usually due to a program needing ROOT access to complete or delete something, but for some reason isn't prompting you.

The workaround is launching Xcode by command line via SUDO (as Superuser/Root):

sudo open --new /Applications/Xcode.app

After it opens you may close it and re-launch it normally from that point forward.

Hope it helps.

Answer 3

Try running the Xcode binary directly instead of using LSS.

From the CLI:

/Applications/Xcode.app/Contents/MacOS/Xcode

If something is wrong it will give you way more useful output.

Answer 4

On my quite new Macbook Pro with plenty of memory and SSD, it took ages to start for the first time. So my suggestion would be to wait a little bit more and see if it does start. My first startup took aprox. 4 minutes or something.

Answer 5

I had the exact same problem after updating to 10.9.4.

I managed to get Xcode starting again by removing the PlugInKit.framework from the /System/Library/PrivateFrameworks folder

(Of course, it is a good idea to back up the framework instead of simply deleting it in case you need it later)

Updated Oct 9

Note: This was a solution to work around a XCode launch issue related to a "Symbol not found" error within the PlugInKit.framework while XCode 6 was still in Beta 2/3. This is probably not relevant any more now that XCode 6 is official.