Xcode Not Working After Upgrading to macOS Ventura: How To Repair It

Should you’ve not too long ago upgraded to macOS Ventura, you may run into issues with Xcode not working. There are a few the explanation why this is perhaps. I am going to stroll you thru tips on how to repair this so you may as soon as once more run Xcode in your Mac.

Earlier Variations of Xcode Incompatible With macOS Ventura

The most typical perpetrator behind Xcode not working below macOS Ventura is outdated software program. Simply because you may have the most recent working system updates doesn’t suggest Xcode obtained up to date, too.

When this occurs, you may get an error message telling you that it’s worthwhile to replace to the most recent model.

If every thing was working wonderful previous to upgrading to Ventura, you most likely have some model of Xcode 13 nonetheless put in, like 13.4.1. That model is not suitable with macOS Ventura, which requires Xcode 14 or newer.

Two Choices to Repair Xcode Not Engaged on macOS Ventura

There are two methods you may repair this difficulty. One is to replace the software program developer instruments, and the opposite is to “trick” macOS into considering the older model is definitely the latest.

Replace Xcode From the Mac App Retailer

The popular technique is to replace your Xcode set up to the latest model. That is, in actual fact, the one decision that Apple’s liable to acknowledge or assist.

Fooling macOS Into Pondering the Older Model Is Up to date

The subsequent technique is unquestionably a hack, if you’ll. When you have an Xcode undertaking that completely will depend on utilizing Xcode 13, you may observe these steps.

That being stated, this is how one can idiot Ventura into considering Xcode 13 is actually the latest model.

1. open Functions > Utilities > Terminal.
2. Now, we will create a script that may modify the construct variety of the Xcode app. kind nano xcode14.sh and press return.
3. Copy the whole script (discovered on StackOverflow). I’ve included it beneath these directions for simple reference.
4. Paste the script into your Terminal window.
5. press Management-X to stop nano, then Y to save lots of adjustments. Subsequent, press return to verify.
6. Nonetheless in Terminalrun the script as such: sh xcode14. sh.
   

The output above will mirror the change in construct numbers for Xcode, and Xcode 13 will open because it did previous to updating to macOS Ventura.

As soon as that is executed, you’ll run Xcode 13 on macOS Ventura with none problem. You will not even need to run the script once more, as macOS Ventura will proceed to see the previous model as suitable.

That is the script you need to copy and paste in steps 3 and 4 above:

#!/bin/sh

set -euo pipefail

# Set the paths to your Outdated/New Xcodes
OLD_XCODE="/Functions/Xcode_13.4.1.app" #Outdated model of Xcode
NEW_XCODE="/Functions/Xcode.app" # To get construct quantity

# Get New Xcode construct quantity
OLD_XCODE_BUILD=$(/usr/libexec/PlistBuddy -c "Print CFBundleVersion" 
${OLD_XCODE}/Contents/Data.plist)
NEW_XCODE_BUILD=$(/usr/libexec/PlistBuddy -c "Print CFBundleVersion" 
${NEW_XCODE}/Contents/Data.plist)

echo The Outdated Xcode construct model is $OLD_XCODE_BUILD
echo The New Xcode construct model is $NEW_XCODE_BUILD

# Change Outdated Xcode construct model to New Xcode
/usr/libexec/PlistBuddy -c "Set :CFBundleVersion ${NEW_XCODE_BUILD}" 
${OLD_XCODE}/Contents/Data.plist

# Open Outdated Xcode (system will test construct model and cache it)
open $OLD_XCODE

# Revert Outdated's Xcode's construct model
/usr/libexec/PlistBuddy -c "Set :CFBundleVersion ${OLD_XCODE_BUILD}" 
${OLD_XCODE}/Contents/Data.plist