I've been trying to install the Xcode 7 Beta 3 from Apple for hours and it just won't run on Yosemite 10.10.3. I download and run the installer, and everything works fine, but when I try to open Xcode beta I get a window that lasts for 30 minutes that says "Verifying" and then when it closes sometimes I get a window that says the Xcode beta was downloaded from the internet and it wants to know if I still want to open it. I click "Open" and nothing happens!!! According to task manager, Xcode beta is not responding. I've tried to reverify it 6 times, and even deleted and reinstalled xcode 7 beta from Apple. I'm going to put the El Capitan public beta on my external hard drive and see if xcode 7 will run on that. Though, is there anyway I can get Xcode 7 Beta 3 to run on Yosemite 10.10.3? I have a mid-2009 MacBook Pro, 2.66GHz Intel Core 2 Duo, 4 GB RAM, 256GB SSD.
Ran into the same issue with Xcode 7 beta 4. According to this blog post you just need to quarantine it to disable the Gate Keeper check.
cd /Applications
xattr -d com.apple.quarantine Xcode-beta.app
open Xcode-beta.app
assuming your install folder is /Applications
Update:
This command may not fix everything that needs to disable Gate Keeper. For maximum efficiency, use the recursive flag to make sure to get everything (including simulators) packaged in the app.
sudo xattr -dr com.apple.quarantine Xcode-beta.app
Note: you need sudo since some of the files are protected.
For whatever reason when I added the the xcode beta to my external drive, I opened the one in my external hard drive and now it works just fine. Maybe there's a bug that makes sure that there can't be two versions of Xcode on the same drive?
I have both XCode 6.4 ans XCode 7 installed on the internal drive of my macbook OSX 10.10.3 and it works...
Related
Xcode takes a lot of free space on my SSD therefore I installed it on my external HDD. But when I tried to download any of iOS simulators in Xcode preference I noticed that it was still downloaded on my SSD. Could you please tell how can I change iOS simulator directory? In terminal, anywhere else?
I tried to find command line combination, which change path to simulator
I expected that iOS simulators will get downloaded to my external hdd and would work well
As of Xcode 11 (released to beta to developers yesterday), we should locate the simulator runtimes located in /Volumes/*/Library/Developer/CoreSimulator/Profiles/Runtimes
I suggest you move them to that location on your spare drive. Doing so while CoreSimulatorService is running will probably confuse its state because we don't currently handle runtimes vanishing from the root filesystem (we do handle them disappearing due to a disk eject through), so you will probably need to SIGKILL CoreSimulatorService after doing the move by running:
sudo killall -9 com.apple.CoreSimulator.CoreSimulatorService 2> /dev/null
If you don't want to wait for Xcode 11, you can also just create a symlink from /Library/Developer/CoreSimulator/Profiles to /Volumes/MyHDD/Library/Developer/CoreSimulator/Profiles.
Delphi 10.2.3 MacOS Mojave (which I'm regretting)
I had Xcode 10 and it didn't work with Delphi. I removed Xcode 10 and I installed Xcode 9.4.1 and its command tools.
The PAServer continues to give this message on startup:
Acquiring permission to support debugging...failed
Delphi hangs during the "Launching:" phase of deploying an iOS app.
Everything worked fine before I upgraded to Mohave and tried Xcode 10.
What's a guy got to do to get Delphi 10.2.3 to debug iOS apps with Xcode 9 on Mojave?
The following seems to work:
Start the PAServer in Terminal under root:
sudo ./paserver
or set permissions for dbkosx as follows:
sudo chown root dbkosx_25_0
sudo chmod u+s,g+x dbkosx_25_0
Assuming you are in the PAServer-19.0.app/Contents/MacOS/ folder. If not, then execute this first:
cd /Applications/PAServer-19.0.app/Contents/MacOS/
Here's what fixed it. I deployed a blank iOS app from Xcode. Then Delphi started deploying normally again, including stepping into the debugger.
I have no idea what magic Xcode did to clear the logjam.
With new macOS Mojave coming out tomorrow (24 September 2018), is it going to support Xcode 9?
We could not switch one of our projects to Xcode 10 because of some outdated dependencies.
Yes.
You can use Xcode 9 (last release is Xcode 9.4.1) on macOS Mojave.
If you are upgrading from macOS High Sierra, you can choose to not update your copy of Xcode installed from the Mac App Store.
If you have already upgrade your App Store installed copy of Xcode to Xcode 10, you can download Xcode 9.4.1 DMG from Apple Developer Downloads.
Once downloaded, double click to mount the DMG, copy Xcode.app from the disk image to Desktop, rename it to Xcode 9.app and move it to /Applications directory. You can also add drag the Xcode 9.app file to Dock to add a shortcut.
Note: I’m not sure about expect version number compatibility, thus recommended to install the last release of Xcode 9, i.e. Xcode 9.4.1.
As mentioned in your comment, you currently have Xcode 9 installed from the Mac App Store and a GM build of Xcode 10 downloaded from Apple Developer. You can now take either one of the below mentioned approaches. However, before proceeding, consider deleting the Xcode_10.app from /Applications as it is a GM build and the public release for the same is now available:
Leave Xcode.app (Xcode 9) as is in the /Applications directory. Mac App Store will show that an update is available. Do not install the update from the Mac App Store. However, make sure that the version of Xcode 9 is the last released version, i.e. Xcode 9.4.1. Download Xcode 10 public build from Apple Developer Download using this link. Copy the Xcode.app from the downloaded DMG to ~/Desktop, rename it to Xcode 10.app and move it to /Applications directory.
Second alternative would be to update the Mac App Store installed copy to Xcode 10 and download Xcode 9.4.1 instead from Apple Developer Downloads. Similarly, rename the downloaded file to Xcode 9 and move it to /Applications directory.
I am trying to run Xcode 6.4 on El Capitan and I can run with the instructions on this post.
But I am looking for a way to run it without any external program as I ran before with OSX 10.10 (Yosemite).
I found this post that point to this instructions but it does not work. These are the instructions
Open this file /System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exception.plist
Find lines with name xcode in them (http://i.imgur.com/tcKWLhz.png)
Edit value HardDisabled from YES to NO
Save and reboot
1.a) If you can't save because file says it's locked then enable
rootless mode (sudo nvram boot-args="kext-dev-mode=1 rootless 0" or
sudo nvram boot-args="kext-dev-mode=1 rootless=0") and reboot.
1.b) If you still have problem, copy Exceptions.plist to Desktop (or
wherever else) and edit it them.
1.c) Save it and them remove
Exceptions.plist in System (sudo rm -rf
/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist)
1.d) Copy file from Desktop (or wherever else) to
/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources and
reboot.
I couldn't edit the Exceptions.plist file with the instructions above, but after a lot of tries I found the way to edit it.
Here you can find the instructions to edit it.
After all of this, I still receiving the message
You can't open the application "XCode.app" because it is not supported
on this type of Mac
when I try to run Xcode 6.4 from Finder
SOLUTION 1
The only thing I didn't do was to reinstall XCode 6.4 after the changes. I reinstalled it and it works!
SOLUTION 2
Dave Wood provided another solution to avoid to reinstall XCode. This is is post and as he posted in his answer the script is here
Xcode 6.4 runs out-of-the-box on:
El Capitan Beta 4 (build 15A226f)
El Capitan Beta 5 (build 15A235d)
El Capitan Beta 7 (build 15A263e)
Xcode 6.4 fails to open on:
El Capitan Beta 6 (build 15A244d) - Workaround here
cd /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator.sdk/usr/lib
sudo mv dyld_sim dyld_sim.orig
There are two places in Exceptions.plist which list Xcode. The one you don't have listed is:
<key>com.apple.Xcode</key>
<array>
<dict>
<key>AppStoreIdentifier</key>
<string>497799835</string>
<key>AppStoreUpdateIsFree</key>
<true/>
<key>HardDisabled</key>
<false/>
<key>HighVersion</key>
<string>5085.0</string>
</dict>
</array>
It is necessary to re-install Xcode afterwards.
In addition to the original first answer if you dont want to reinstall xcode again because of slow internet connection you can just copy xcode to desktop delete the one in application folder (Assuming you did all the required steps above except reinstalling). And move back xcode to application folder(while copying to desktop itself if you did above step right you will notice the cut icon will dissapear after copying)
User lembacon here found the solution:
cd /Applications/Xcode.app/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.
I confirm that this solution is working with Xcode 6.4.
I updated my Xcode from 6.2 to 6.3 and now instruments is not working anymore, it is requesting a template and it doesn't matter which one is chosen, it is not able to open it.
It is happening with iOS 8.2 on an iPhone 6+, and with the simulator (ios 8.2 and 8.3).
UPDATE I also updated my phone to iOS 8.3 and tried with Xcode 6.4Beta and I still have the same problem.
Try to run this from a terminal:
sudo chmod a+rwxt /Library/Caches/com.apple.dt.instruments
to fixup permissions on that directory.
Source : https://forums.developer.apple.com/thread/6441
I actually got the same problem with Xcode 7 and solved it by deleting instrument's default base temp directory, and I guess it was in this folder (/Library/Caches/com.apple.dt.instruments)