El Capitan beta 6 + Xcode

Could it be related to firmware update package? Should everybody be using the same one, regardless of Mac they are using?

Did not work. Late 2013 Retina MBP. But at least the rollback did.

I'm using a mid-2015 rMBP. I installed the firmware update first, then the delta.

Perfectly good reasoning but, no, not related. The exact same "firmware" update is automatically downloaded and installed with any given beta update regardless of Mac - they somehow pave the way for the beta (often just a redundancy I would guess) and are not related to the hardware.

There are, of course, firmware updates that appear, also in the App Store as an update, that conform more to a more typical conception of a firmware update, but these always identify the specific Mac and purpose in their name.

Here's some irony. I went and filed a bug report and when submitting, the bug reporter crashed. 😮 I had to force-quit Safari.

What's SIP and how can I go about disabling it if I encounter the sound issues? I'm about to install the firmware update then the delta...

xCode "O.K." again after reinstalling beta 5 but no sound and miserable graphics performance( MBP+ ACD 30").

--edit--

great, the thing from Max108 (cmd-r & Utilities /disable security config) brought back my graphics drivers, so xcode is usable again.

( but still no sound).

After reinstalling and doing the delta update, I noticed all my Mail accounts were gone. After adding them again, I can no longer send mail. Mail simply states that there is no subject to any mail.

I decided it might be better to reinstall again and do a manual beta update 5 times instead of using the delta. Now I'm faced with a new issue, I cannot reinstall because recovery software insists that I'm using the wrong password with my Apple ID.

"Springboard quit unexpectedly" with any playground open. If I OK the crash dialog, I'll get a new one within five seconds.

Didn't happen on El Cap beta 5.

Clearly an issue with the latest Beta. I personally can't open any new or old project without XCode crashing. I think we will need to wait for the next build. Hopefully by then they would have fixed it.

Same problem here. Probably the best way for now is waiting for next build of Xcode 7 beta.

Hi Max108 - thanks for your suggestion !

Quick question, instead of disabling SIP in Recovery can I do it via terminal?

sudo nvram boot-args="rootless=0";sudo reboot

Hi,

But no, that doesn't work anymore - removed after Dev Beta 2 I think.

Same here.

Today, Update to EI Captian Beta 6, I find my Xcode 7 beta4 can't load Storyboard. The Xcode is down. Other swift or .h .m file can be load. Only main.storyboard cannot to be Load!

Now...Waiting for fix it.

😢

just reinstall beta5 update, it's ok,needn't reinstall beta1

what is this ? (cmd-r & Utilities /disable security config)

MAX108 posted :

booting into Recovery Mode (cmd+R):

Utilities > Security Configuration > uncheck "Enforce System Integrity Protection"

--

that solved my graphics issue after reinstalling to beta 5 (but didn`t solve the sound issue which Max108 wanted to solve :-) ).

I have now worked with xCode for 7 hours . no problems anymore....

I have the same problem! Now i'm doing steps posted by Max108 and i hope that this work. I also hope that apple release a new xcode beta that resolve this problem (also for xcode 6.4 that for xcode 7)

I had back to EI Captian Beta 5.( Run the FirmwareUpdate.pkg first， and OSXUpd10.11.pkg ).

Xcode 7 beta 4 can work fine, Now!!!

(cmd-r & Utilities /disable security config) is not help for me.

My sound is always broken.

I have public beta 4 (i'm developer but i have public beta...) Max108 procedure work also for me?

Thanks

Yes! Work Also for me!

Samme issue here: Xcode 6.4 crashes immediately after I open a project, while Xcode 7 cannot open .storyboard files

Xcode works again, thanks.

Sound does not, even with Max108 suggestion and I cannot seem to play quicktime files (The document “.mp4” could not be opened. An unknown error occurred (-101)).

I find it somewhat troubling that Apple actually let something like this slip through the cracks. Doesn't anyone in the world's richest company actually dogfood their own software? Surely somebody must use Xcode internally within the company who would have seen this bug. Either that or developer productivity is not a priority for anyone in the company.

Hi guys, I've just found a temporary workaround. (Applies to Xcode 7 beta 4 on OS X El Capitan Developer Beta 6)

Open your Terminal:

cd /Applications/Xcode-beta.app (or wherever your Xcode 7 beta 4 is located)
cd Contents/Developer/Platforms/iPhoneSimulator.platform
cd Developer/SDKs/iPhoneSimulator.sdk/usr/lib
sudo mv dyld_sim dyld_sim.orig

The reason is that the internal implementation of `_NSGetExecutablePath` has been updated (where the Kernel is involved), and the host `dyld` has also been updated to track this change. The `dyld_sim`, however, has not yet been updated. So the problem is that `_NSGetExecutablePath` will return a path that contains a `executable_path=` part which causes that the `CFBundleGetMainBundle()` always returns `NULL`. This workaround simply forces the simulator to use the host `dyld`. By far, everything works great for me.