#Xcode simulator quit xcodes update#

The only target available to add to its build phase is MyLibrary. But if I create a scheme manually, I cannot add all three of these targets to its build phase. I can build for previews successfully with this scheme. What I found was that an auto-created build scheme works, but the auto-created scheme contains three build targets: Having a resource (in my case, a xib) in the module, and.( You can find my test project here.)įrom there, a combination of two things led to the problem: I spent a while trying to find a minimal test case and eventually reduced it to a tiny SwiftPM package named MyPackage containing a single library target, MyLibrary, which includes a single module/target named MyTarget. But I couldn't get it working at all (on my real production project) in Xcode 14.0 with just those actions. In prior Xcodes, I was able to get previews to work with sufficient iterations of deleting DerivedData and dinking around with my package manifest. NEW_XCODE='/Applications/Xcode.I've encountered this problem with building for previews and it's been much harder to work around in 14.0 than in older releases. OLD_XCODE='/Applications/Xcode_13.4.1.app' #Old version of Xcode This is the script you should copy and paste in steps 3 and 4 above: #!/bin/sh You won’t even have to run the script again, as macOS Ventura will continue to see the old version as compatible. Once that’s done, you’ll be able to run Xcode 13 on macOS Ventura without any difficulty. MacOS unfortunately only supports running one version of Xcode at a time, and it needs to know the location of the currently running version. The Solution We need to change the names of the pre-iOS 12.2 variants to exactly match the new spelling. The output above will reflect the change in build numbers for Xcode, and Xcode 13 will open as it did prior to updating to macOS Ventura. QUICK FIX This is happening because you have multiple versions of Xcode installed. Still in Terminal, run the script as such: sh xcode14.sh.Press Control-X to quit nano, then Y to save changes.Paste the script into your Terminal window.I’ve included it below these instructions for easy reference. Copy the entire script ( found on StackOverflow).

Now, we’re going to create a script that will modify the build number of the Xcode app.

Open Applications > Utilities > Terminal.

That being said, here’s how you can fool Ventura into thinking Xcode 13 is really the most recent version. If you have an Xcode project that absolutely depends on using Xcode 13, you can follow these steps.īear this in mind: you likely will be completely unable to submit any builds created this way to the App Store for review. The next method is definitely a hack, if you will.

Once finished, you should be able to run Xcode once again.įooling macOS Into Thinking the Older Version Is Updated.

If you don’t have the most recent version of Xcode, the blue “Open” button shown should say “Update” instead.

From the search results, click on Xcode, as shown below.

#Xcode simulator quit xcodes update#

You can update Xcode to the latest version through the Mac App Store.