How to update xcode
How to update xcode
How to Download Xcode and Install it on Your Mac – and Update it for iOS Development
Xcode is the tool developers use to build apps for the Apple ecosystem – MacOS, iOS, and all things Apple.
This guide will walk you through how to successfully install Xcode onto your Mac, from start to finish.
Here are some handy tips to know before you get started:
8 gigabytes zipped. When you unzip it, that’s another 17 gigabytes. Then you’ll need the command line tool, which is yet another 1.5 gigabytes.
Here’s an overview of the steps to install Xcode
Note that I have listed some Terminal commands in the steps below. These commands can be typed into your present working directory. This means that you don’t need to navigate to any particular folder.
If you really want to, you can first type cd before typing the commands in the below steps. This will return you back to the home folder.
Step #1: Download Xcode
There are two ways to do this. For the latest version and a theoretically «easy» installation, you can use the App Store. I don’t recommend this option.
I prefer to use the developer site. This comes with the bonus option of being able to download any version you’d like.
Option #1: Download via the App Store for the latest version (not my preferred option)
In theory, this should be a seamless and pain-free process. But if the installation fails for any reason on the last step, it is very hard to troubleshoot.
There are a few reasons for failure, and no easy way to know which is the underlying cause. If you do encounter a failure, you will need to re-download the entire file again each time you try to fix the failure. As the latest version is 8 gigabytes, I didn’t much enjoy this approach.
But if you’re feeling brave, here are the steps:
Option 2: Download via the Developer site for a specific version (my preferred option)
Step #2: Install the command line tool (CLT)
If you have multiple users on your computer, you will need to update the CLT for each user.
A screenshot of https://developer.apple.com/download/more/
But if you have an existing version of Xcode installed on your machine, you’ll probably see this error:
This means you’ll need to go to the developer website instead.
Installing the CLT
Double click the box and follow the prompts to install the CLT. It will take a few minutes to complete.
Step #3: Open Xcode
Open the Applications folder and open the new version of Xcode. If you renamed Xcode, make sure you open the correct application
Xcode may prompt you to install additional components. Click install. This will take a few minutes.
While it’s installing, check that your default Xcode version is the one you just downloaded:
Once the components are installed, Xcode will launch. You should be able to pick up your old projects and continue where you left off seamlessly*.
*Note that if you use any proxy tools, such as Charles, you will need to re-install those certificates in your simulator again.
If you encounter any errors while trying to build or run a project, check which device you are trying to launch. The new version may not remember the device you were using before. If so, click on the device and choose «Add additional simulators» from the drop down menu to add the device you want.
Step #4. Delete the files
If you don’t need the older versions of Xcode on your computer, you can uninstall them and get some hard drive space back.
That’s everything. I hope this has helped you successfully install Xcode. Have fun with it!
Xcode
Xcode is a complete developer toolset for creating apps for Mac, iPhone, iPad, Apple Watch, and Apple TV. Xcode brings user interface design, coding, testing, debugging, and submitting to the App Store into a unified workflow.
Downloading and updating Xcode
The current release of Xcode is available as a free download from the Mac App Store. The Mac App Store will notify you when an update is available or you can have macOS update automatically as it becomes available.
The latest beta version and previous versions of Xcode can be downloaded from the Downloads page. To download Xcode, simply sign in with your Apple ID. Apple Developer Program membership is not required.
Learning about Xcode
For step-by-step guidance on how to use Xcode to build, test, and submit apps to the App Store, take a look at Xcode documentation. You can also learn about the latest features and capabilities in Xcode. For details on the latest released versions, including each beta release, view the Xcode release notes.
Submitting apps to the App Store
Xcode provides an integrated workflow for Apple Developer Program members to prepare and submit apps to the App Store. To submit your apps, use the latest version of Xcode available on the Mac App Store or, when available, the latest Release Candidate from the Downloads page.
Minimum SDK requirements for App Store submissions.
iOS and iPadOS apps submitted to the App Store must be built with Xcode 13 and the iOS 15 SDK. And watchOS apps submitted to the App Store must be built with Xcode 13 and the watchOS 8 SDK.
Minimum requirements and supported SDKs
Xcode Version | Minimum OS Required | SDK | Architecture | Deployment Targets | Simulator | Swift |
---|---|---|---|---|---|---|
Xcode 14 | macOS Monterey 12.4 | iOS 16 macOS 13 tvOS 16 watchOS 9 DriverKit 22 | i386 x86_64 armv7k arm64 arm64e arm64_32 | iOS 11-16 iPadOS 13-16 macOS 10.13-13 tvOS 11-16 watchOS 4-9 DriverKit 19-22 | iOS 12.4-16 tvOS 12.4-16 watchOS 7-9 | Swift 4 Swift 4.2 Swift 5.7 |
Xcode 13.4 | macOS Monterey 12 | iOS 15.5 macOS 12.3 tvOS 15.4 watchOS 8.5 DriverKit 21.4 | i386 x86_64 armv7 armv7s armv7k arm64 arm64e arm64_32 | iOS 9-15.5 iPadOS 13-15.5 macOS 10.9-12.3 tvOS 9-15.4 watchOS 2-8.5 DriverKit 19-21.4 | iOS 12.4-15.5 tvOS 12.4-15.4 watchOS 7-8.5 | Swift 4 Swift 4.2 Swift 5.6 |
Xcode 13.3 | macOS Monterey 12 | iOS 15.4 macOS 12.3 tvOS 15.4 watchOS 8.5 DriverKit 21.4 | i386 x86_64 armv7 armv7s armv7k arm64 arm64e arm64_32 | iOS 9-15.4 iPadOS 13-15.4 macOS 10.9-12.3 tvOS 9-15.4 watchOS 2-8.5 DriverKit 19-21.4 | iOS 12.4-15.4 tvOS 12.4-15.4 watchOS 7-8.5 | Swift 4 Swift 4.2 Swift 5.6 |
Xcode 13.2 | macOS Big Sur 11.3 | iOS 15.2 macOS 12.1 tvOS 15.2 watchOS 8.3 DriverKit 21.2 | i386 x86_64 armv7 armv7s armv7k arm64 arm64e arm64_32 | iOS 9-15.2 iPadOS 13-15.2 macOS 10.9-12.2 tvOS 9-15.2 watchOS 2-8.3 DriverKit 19-21.2 | iOS 10.3.1-15.2 tvOS 10.2-15.2 watchOS 3.2-8.3 | Swift 4 Swift 4.2 Swift 5.5 |
Xcode 13.1 | macOS Big Sur 11.3 | iOS 15 macOS 12 tvOS 15 watchOS 8 DriverKit 21.0.1 | i386 x86_64 armv7 armv7s armv7k arm64 arm64e arm64_32 | iOS 9-15 iPadOS 13-15 macOS 10.9-12 tvOS 9-15 watchOS 2-8 DriverKit 19-21.0.1 | iOS 10.3.1-15 tvOS 10.2-15 watchOS 3.2-8 | Swift 4 Swift 4.2 Swift 5.5 |
Xcode 13 | macOS Big Sur 11.3 | iOS 15 macOS 11.3 tvOS 15 watchOS 8 DriverKit 20.4 | i386 x86_64 armv7 armv7s armv7k arm64 arm64e arm64_32 | iOS 9-15 iPadOS 13-15 macOS 10.9-11.3 tvOS 9-15 watchOS 2-8 DriverKit 19-20.4 | iOS 10.3.1-15 tvOS 10.2-15 watchOS 3.2-8 | Swift 4 Swift 4.2 Swift 5.5 |
Xcode 12.5.1 | macOS Big Sur 11 | iOS 14.5 macOS 11.3 tvOS 14.5 watchOS 7.4 DriverKit 20.4 | i386 x86_64 armv7 armv7s armv7k arm64 arm64e arm64_32 | iOS 9-14.7 iPadOS 13-14.7 macOS 10.9-11.5 tvOS 9-14.7 watchOS 2-7.6 DriverKit 19-20.4 | iOS 10.3.1-14.5 tvOS 10.2-14.5 watchOS 3.2-7.4 | Swift 4 Swift 4.2 Swift 5.4 |
Xcode 12.5 | macOS Big Sur 11 | iOS 14.5 macOS 11.3 tvOS 14.5 watchOS 7.4 DriverKit 20.4 | i386 x86_64 armv7 armv7s armv7k arm64 arm64e arm64_32 | iOS 9-14.6 iPadOS 13-14.6 macOS 10.9-11.4 tvOS 9-14.6 watchOS 2-7.5 DriverKit 19-20.4 | iOS 10.3.1-14.5 tvOS 10.2-14.5 watchOS 3.2-7.4 | Swift 4 Swift 4.2 Swift 5.4 |
Xcode 12.4 | macOS Catalina 10.15.4 (Intel-based Mac) |
macOS Big Sur 11
(Apple silicon Mac)
macOS 11.1
tvOS 14.3
watchOS 7.2
DriverKit 20.2
x86_64
armv7
armv7s
armv7k
arm64
arm64e
arm64_32
iPadOS 13-14.4
macOS 10.9-11.1
tvOS 9-14.3
watchOS 2-7.2
DriverKit 19-20.2
tvOS 10.2-14.3
watchOS 3.2-7.2
Swift 4.2
Swift 5.3
macOS Big Sur 11
(Apple silicon Mac)
macOS 11.1
tvOS 14.3
watchOS 7.2
DriverKit 20.2
x86_64
armv7
armv7s
armv7k
arm64
arm64e
arm64_32
iPadOS 13-14.3
macOS 10.9-11.1
tvOS 9-14.3
watchOS 2-7.2
DriverKit 19-20.2
tvOS 10.2-14.3
watchOS 3.2-7.2
Swift 4.2
Swift 5.3
macOS Big Sur 11
(Apple silicon Mac)
macOS 11
tvOS 14.2
watchOS 7.1
DriverKit 20
x86_64
armv7
armv7s
armv7k
arm64
arm64e
arm64_32
iPadOS 13-14.2
macOS 10.9-11
tvOS 9-14.2
watchOS 2-7.1
DriverKit 19-20
tvOS 10.2-14.2
watchOS 3.2-7.1
Swift 4.2
Swift 5.3
macOS Big Sur 11
(Apple silicon Mac)
macOS 10.15.6
tvOS 14
watchOS 7
DriverKit 19
x86_64
armv7
armv7s
armv7k
arm64
arm64e
arm64_32
iPadOS 13-14.1
macOS 10.9-11
tvOS 9-14
watchOS 2-7
DriverKit 19
tvOS 10.2-14
watchOS 2-7
Swift 4.2
Swift 5.3
macOS 10.15.6
tvOS 14
watchOS 7
DriverKit 19
x86_64
armv7
armv7s
armv7k
arm64
arm64e
arm64_32
iPadOS 13-14
macOS 10.6-10.15.6
tvOS 9-14
watchOS 2-7
DriverKit 19
tvOS 10.2-14
watchOS 3.2-7
Swift 4.2
Swift 5.3
macOS 10.15.6
tvOS 13.4
watchOS 6.2
DriverKit 19
x86_64
armv7
armv7s
armv7k
arm64
arm64e
arm64_32
iPadOS 13-13.7
macOS 10.6-10.15.6
tvOS 9-13.4
watchOS 2-6.2
DriverKit 19
tvOS 10.2-13.4
watchOS 3.2-6.2
Swift 4.2
Swift 5.2
macOS 10.15.6
tvOS 13.4
watchOS 6.2
DriverKit 19
x86_64
armv7
armv7s
armv7k
arm64
arm64e
arm64_32
iPadOS 13-13.6
macOS 10.6-10.5.6
tvOS 9-13.4
watchOS 2-6.2
DriverKit 19
tvOS 10.2-13.4
watchOS 3.2-6.2
Swift 4.2
Swift 5.2
macOS 10.15.4
tvOS 13.4
watchOS 6.2
DriverKit 19
x86_64
armv7
armv7s
armv7k
arm64
arm64e
arm64_32
iPadOS 13-13.5
macOS 10.6-10.15.4
tvOS 9-13.4
watchOS 2-6.2
DriverKit 19
tvOS 10.2-13.4
watchOS 3.2-6.2
Swift 4.2
Swift 5.2
macOS 10.15.4
tvOS 13.4
watchOS 6.2
DriverKit 19
x86_64
armv7
armv7s
armv7k
arm64
arm64e
arm64_32
iPadOS 13-13.4.x
macOS 10.6-10.15.4
tvOS 9-13.4
watchOS 2-6.2
DriverKit 19
tvOS 10.2-13.4
watchOS 3.2-6.2
Swift 4.2
Swift 5.2
macOS 10.15.2
tvOS 13.3
watchOS 6.1.1
DriverKit 19
x86_64
armv7
armv7s
armv7k
arm64
arm64e
arm64_32
iPadOS 13-13.3
macOS 10.6-10.15.2
tvOS 9-13.3
watchOS 2-6.1.1
DriverKit 19
tvOS 10.2-13.3
watchOS 3.2-6.1.1
Swift 4.2
Swift 5.1
macOS 10.15.1
tvOS 13.2
watchOS 6.1
DriverKit 19
x86_64
armv7
armv7s
armv7k
arm64
arm64e
arm64_32
iPadOS 13-13.2.x
macOS 10.6-10.15.1
tvOS 9-13.2
watchOS 2-6.1
DriverKit 19
tvOS 10.2-13.2
watchOS 3.2-6.1
Swift 4.2
Swift 5.1
macOS 10.15
tvOS 13
watchOS 6
DriverKit 19
x86_64
armv7
armv7s
armv7k
arm64
arm64e
arm64_32
iPadOS 13-13.1
macOS 10.6-10.15
tvOS 9-13
watchOS 2-6
DriverKit 19
tvOS 10.2-13
watchOS 3.2-6
Swift 4.2
Swift 5.1
macOS 10.15
tvOS 13
watchOS 6
DriverKit 19
x86_64
armv7
armv7s
armv7k
arm64
arm64e
arm64_32
iPadOS 13
macOS 10.6-10.15
tvOS 9-13
watchOS 2-6
DriverKit 19
tvOS 10.2-13
watchOS 3.2-6
Swift 4.2
Swift 5.1
macOS 10.14.6
tvOS 12.4
watchOS 5.3
x86_64
armv7
armv7s
armv7k
arm64
arm64e
arm64_32
macOS 10.6-10.14.6
tvOS 9-12.4
watchOS 2-5.3
tvOS 10.2-12.4
watchOS 3.2-5.3
Swift 4.2
Swift 5
macOS 10.14.4
tvOS 12.2
watchOS 5.2
x86_64
armv7
armv7s
armv7k
arm64
arm64e
arm64_32
macOS 10.6-10.14.4
tvOS 9-12.2
watchOS 2-5.2
tvOS 9-12.2
watchOS 2-5.2
Swift 4.2
Swift 5
Legend
Minimum OS Required: The version of macOS required to install this version of Xcode.
SDK: The version of SDKs included in this version of Xcode.
Architecture: The architectures supported for development by this version of Xcode.
OS: The iOS, iPadOS, macOS, tvOS, and watchOS versions supported by this version of Xcode for developing, installing, and debugging applications.
Simulator: Versions of iOS, tvOS, and watchOS simulators supported for development by this version of Xcode.
Swift: Version of Swift supported for development by this version of Xcode.
Providing feedback and reporting bugs
Your feedback goes a long way toward making Xcode even better. With Feedback Assistant, you can report issues or request enhancements to APIs and tools. Provide detailed information about issues, including your system and developer tool versions, and any relevant crash logs or console messages. To ask questions and find answers from Apple engineers and other developers, visit the Apple Developer Forums.
Invalid private key and certificate pairing
If you receive an error message saying, «Xcode could not find a valid private-key/certificate pair for this profile in your keychain,” the Keychain Access application on your Mac is missing either the public or private key for the certificate you’re using to sign your app.
This often happens when you’re trying to sign and build your app from a different Mac than the one you originally used to request your code signing certificate. It can also happen if your certificate has expired or has been revoked. Ensure that your app’s provisioning profile contains a valid code signing certificate, and that the Keychain Access application on your Mac contains that certificate, the private key originally used to generate that certificate, and the WWDR Intermediate Certificate.
For instructions on how to resolve this and other code signing errors, review the Code Signing Support page.
Apple security updates
For information on the security content of Xcode updates, visit the Apple security updates page.
Feedback Assistant
Submit bug reports and request enhancements to APIs and developer tools.
Send us feedback
Forums
Ask questions and discuss development topics with Apple engineers and other developers.
Contact us
Have a question or request? We can help by phone or email.
Xcode 10.2 on High Sierra – Step by Step
If your question is “How to update Xcode 10.1 to Xcode 10.2.1?” then you have come to the right place!
Recently Apple has updated Xcode to only work with the latest Mac OS Mojave (10.4.4), this means that developers who have old Macs won’t be able to update their OS and develop in Swift 5 using Xcode 10.2.1.
We at CodeWithChris however, found a solution to this dilemma!
Please do note however that this is a workaround. This is not in anyway supported by Apple as they have specifically set the new version of Xcode 10.2.1 for the latest OS only. We found that these steps work for us and we cannot guarantee if it will work for you.
Presenting: Installing/Updating Xcode 10.1 to Xcode to 10.2.1 on Mac OS High Sierra (10.13.6) or Mac OS Mojave (10.4.0)
Please note that we won’t be using the App Store to do this
Step 1:
Log-in your Apple account and download Xcode 10.2.1 (or whatever is the latest)
Xcode direct download from apple developer site
The logo of Xcode should have an error icon on it, you can ignore this for now
Xcode 10.1 vs (Incompatible) Xcode 10.2.1
Step 2:
Open the app directory (right click->show package contents) of your xcode 10.2.1 app
Navigate to Xcode 10.2.1.app/Contents/ and edit the file Info.plist, change the Minimum System Version to 10.13.6 (it should have 10.14.3 originally written on it), make sure to save.
Info.plist contents with the edited Minimum System Version
Additionally, navigate to Xcode.app/Contents/Developer/Applications/Simulator.app/Contents/ edit Info.plist and also change the Minimum System Version to 10.13.6.
Step 3: (This is the reason why we need Xcode 10.1 installed)
Now go to your xcode 10.1 app directory (right click->show package contents) and copy the file xcodebuild located on Xcode 10.1.app/Contents/Developer/usr/bin/
xcodebuild file that needs to be overwritten from Xcode 10.1 folder to Xcode 10.2.1 folder
Then, go to your xcode 10.2.1 app directory and overwrite the file xcodebuild located on Xcode 10.2.1.app/Contents/Developer/usr/bin/
Step 4:
Finally, restart your mac to reflect the changes made to the system.
And your done! you can now use xcode 10.2.1 in your your Mac! You will notice that the error icon is gone and you can now launch and use xcode10.2.1 for app development!
(Now working) Xcode 10.2.1
45 Comments
Thank you so much! I am a Mac newbie, so this was a bit intimidating, but I wanted to share that not only does following these instructions verbatim work fine on High Sierra for me, but it worked to the latest Xcode of 10.3. The only thing I must point out that the instructions omitted (assumed we would know) is how to edit the Info.plist files. No, using vi didn’t cut it. Presumably this is the second reason we needed to have 10.1 installed first, I learned you need to use Xcode to edit the Info.plist files. No save button, just edit the value and quit out. Rebooted. When I ran the 10.3 app it complained it needed to download more updates, which scared me, but it did this and then Xcode 10.3 opened up without any complaints! Didn’t try to use it yet, assume it works.
Thanks 😉 you saved my time and money…..
I did all of this post.
Install xcode 10.3 and it works(all about this post).
after download https://github.com/iGhibli/iOS-DeviceSupport the folder that i need 13.0,13.1,13.2
after move this folder to Xcode 10.3 directory
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport
Restar the Mac.
now i can debug from IMAC 2010 with Xcode 10.3 a iPhone 7 device with iOS 13.2.2
Hey Folks,
So far any solution found for XCODE 11.xx
I really need an XCODE version which can work with OSX 13
Cheers
It work for Xcode 10.3. Has anyone tried it for XCode 11.1
move the archive to another carpet and edit. after you must replace the archive.
HOW DID YOU EVEN EDIT THE INFO.PLIST. LIKE. ITS ALL MESSED UP WHEN OPENED WITH TEXT EDIT PEOPLE.
You open it with your previous Xcode version
I not leaving my name and I might be late but I recommend using the existing Xcode 10.1 for editing the plist file. Also, check out dosdude1 patcher, check the all tabs before downloading as I know my Mac and it’s use case wouldn’t run without full graphics acceleration.
Does this work with Xcode 11.1?
Just a note, to allow the editing of PLIST files you have to reboot your computer and hold the ⌘+R keys, then when you reach the menu, select utilities—Terminal, when the terminal is finished loading, type; csrutil disable.
This disables SIP (System Integrity Protection), is only to be done when it’s really necessary (modifying Library things does not count) and could expose your Mac to dangers. Please remember to enable it back.
ran the following to bypass the startup OS version error
First time I ran it, it installed the libraries. Send time it started the IDE.
I had to rename the Xcode Application name once more to remove the cannot run image.
Thank you Bob. This made the trick!
the simulator is working too now. Have to do the same for simulator info.plist. (/Applications/Xcode1021.app/Contents/Developer/Applications/Simulator.app/Contents/info.plist).
Hi,
Thanks for putting this up.. and saved me to buy a new mac. Does anyone experiencing with the simulator greyed out? Please let me know if you have an idea on how to get it to work.
Thanks
Folks, It is necessary to rename the application as Xcode10.2.1
which editor used to change the information?
Brilliant – thank you!! This worked exactly as indicated.
As some seem to fail I’ll share my success:
Using hardware: iMac (21.5-inch, Mid 2010), 3.06 GHz. 12 GB.
Finally I’ll add my local date, afaics otherwise wholly lacking on this page: September 2019.
Thanks a lot! Xcode 10.3 worked like a charm on iMac mid 2011 running High Sierra
Like Jurie, I was also able to get this working for 10.3 on High Sierra. Note: For some reason the plist files were cached before I edited them, so after editing and rebooting I was still blocked. So, I had to force a re-cache of the plist files (there are multiple ways to do this) to be able to start xcode 10.3.
Hi,
So I’ve posted a couple times with issues I was having. I’ve resolved my issues and thought I’d post again. Machine:Macbook Pro 13″ mid 2010 running OS 10.13.6, Xcode 7.
OS 10.13.6 is max for this machine Apple won’t let it go any further. Xcode stopped updating a long time ago I don’t know why.
1) If you have Xcode prior to 8 and you want to keep your program code you must install Xcode 8 to bring your code up to date. Apparently, open all your code inside 8 and let it update everything.
2) You cannot go from Xcode 7 directly to 10.2.1 or 10.3 doesn’t matter if you have existing code or not, you must install Xcode 10.1 first, let it load all the supporting files.
3) Follow the instructions EXACTLY as Chris has written them to upgrade from 10.1 to 10.2.1. Skip a step and it won’t work.
Tips: remove the Xcode quick-launch from the Dock, rename your current Xcode version in the Application directory (now), Download the file from Apple to your download directory, unpack it in the download directory, make the edits as outlined by Chris, move the file to the Applications directory, make sure everything is closed (not JUST minimized), reboot your computer, go to the Applications directory and launch Xcode and follow the prompts–be patient your computer is old it will run slow!
4) I upgraded from 7 to 10.1 then from 10.1 to 10.2.1 then to 10.3. I followed the procedures outlined above each time.
Yes, I have Xcode 10.3 running on a MacBook Pro 13″ mid 2010.
It was Soooo Excellent to see the screen come up and tell me 10.3!
Tip: when I loaded my first couple programs it took a LONG LONG time for them to load and execute. I’m not sure what is being updated but you need to be patient!! If you are not sure if something is running look in the Dock, if it’s there click it once and see if it comes up. wait. wait.
Thanks a lot!
You saved my early 2011 macbook pro 13″!!
This worked fine for me with Xcode 10.3 on a Mac Mini (2011) with High Sierra. Does anybody know a trick to install (and use) the command line tools for XCode 10.3 under High Sierra?
So how did you get it to install? I downloaded 10.3 and after unpacking it stopped. When I tried to run it so it would install it says I cannot run on 10.13.6 OS. I modified the files as instructed while it was still sitting in the download directory and it still wouldn’t install or run. I moved it myself to the Applications folder and tried to run it but no luck. (Mid 2010 Macbook Pro 13)
Thank you so much. I bought a mac just to compile Xcode, a Pro Early 2011 and I was desperate when I figured out Xamarin didn’t work with Xcode 10.1
Thank you so much.
Thank you! This worked on my Mac Mini 2011 on High Sierra with Xcode 10.1 upgrading to Xcode 10.3. Followed all the steps, be patient. After the last step and restarting it will still look like it can’t run, but when you do it asks to install additional updates and after that it works. Could run the simulator and build to my phone running iOS 12.4.
How to update Xcode?
I have a Mac running High Sierra, version 10.13.6. When running MacPorts I get the following error message that I should update my Xcode installation:
Error: The installed version of Xcode (8.3.1) is too old to use on the installed OS version. Version 9.3 or later is recommended on Mac OS X 10.13.
Build version 8E1000a
But when I launch App Store I can’t find any updates.
Has anyone an idea how I can update Xcode including command line utilities?
2 Answers 2
You probably just install the current version from the MAS.
The command line utilities are included within the Xcode bundle. On first launch symlinks to the utilities are installed into the system so they can be accessed from the Terminal/command line.
There is also a separate Command Line Tools package available from the Developer Account download archive (needs an Apple Developer Account).
I found this answer on Stack Overflow helpful. If I launch App Store.app and it doesn’t list Xcode under my available Updates, instead I search for Xcode, I click on the search result, and it shows a large, blue Update button in the upper-right corner to click.
In this screenshot, the Update button has been replaced by the circular progress indicator (I’m awaiting the download to finish).
Xcode Command Line Tools Installation FAQ
How to install, update, and uninstall Xcode command line tools on macOS
Xcode is an IDE from Apple to create apps for iPhone, iPad, Mac, Apple Watch, and Apple TV. You probably need some of its tools without install the entire package. Maybe you want to write a command-line software on macOS, or maybe you need to use Homebrew package manager. In that case, you only need the subset of it: Xcode command-line tools.
How to Install Xcode Command Line Tools
Here is an example session when I install Xcode command-line tools.
A standard License Agreement will appear. If you want to, you can read them all. Click Agree to continue the installation process. Xcode command line tools license agreement
A pop-up window will appear informing you of the download progress. This time you do nothing. Wait until the download process finished. This can take a long time, it depends on your internet speed. Downloading Xcode command line tools
After the downloading finished, the final pop up window will appear. This is to inform you that the Xcode command-line tools were installed on your machine successfully. Xcode command line tools was installed successfully
How to Uninstall Xcode Command Line Tools
In the case in the future you don’t need it again and want to free some space, you can uninstall it.
It’ll ask your password you used for login. Enter your password and wait until it’s finished.
How to Update Xcode Command Line Tools
As I mention earlier, you probably use Xcode command line tools just for the Homebrew package manager. So am I on the other machine.
One time when I do some check and update, I got the following message.
Then I try to re-install from the command-line but got the following error message instead.
So here is the solution. First, uninstall Xcode installation by removing its folder.
Then re-install again from the beginning.
Follow the installation guideline and wait until it’s finished. Xcode command-line tools now updated to the latest version.