Xcode 14.3 Released [macOS Ventura]

Announcements
1

The Xcode 14.3 image has been released on Gen2 Intel resource class and can be selected as follows:

macos:
    xcode: 14.3.0

:rotating_light: This image includes some breaking changes :rotating_light:

This image is based on macOS Ventura (13.2), therefore there may be breaking changes when switching from a macOS Monterey (12) image. Please ensure your Xcode projects are updated locally before updating the executor on CircleCI.

Additionally, this image is only available on Gen2 Intel resource classes. Please see the following for information regarding deprecation of medium and large Gen1 resource classes:

If you run into any unexpected behaviour, or any other problems, upgrading your pipelines to this image, please let us know in this thread, or by reaching out to support.

:information_source: VM Image Info :information_source:

Xcode 14.3 Build version 14E222b is installed at /Applications/Xcode-14.3.app

The full manifest of installed software can be found here

2

Can’t even start a workflow when specifying this image. Is there an additional requirement vs. simply specifying xcode: 14.3.0 in the circle config?

3

I got an issue after updating to Xcode 14.3

[14:39:33]: Exit status: 65
[14:39:33]: 
[14:39:33]: Maybe the error shown is caused by using the wrong version of Xcode
[14:39:33]: Found multiple versions of Xcode in '/Applications/'
[14:39:33]: Make sure you selected the right version for your project
[14:39:33]: This build process was executed using '/Applications/Xcode-14.3.app'
[14:39:33]: If you want to update your Xcode path, either
[14:39:33]: 
[14:39:33]: - Specify the Xcode version in your Fastfile
[14:39:33]: ▸ xcversion(version: "8.1") # Selects Xcode 8.1.0
[14:39:33]: 
[14:39:33]: - Specify an absolute path to your Xcode installation in your Fastfile
[14:39:33]: ▸ xcode_select "/Applications/Xcode8.app"
[14:39:33]: 
[14:39:33]: - Manually update the path using
[14:39:33]: ▸ sudo xcode-select -s /Applications/Xcode.app
4

@kevnm67 You are probably using Gen1 resource classes which are no longer receiving new images. Full details here:

@n-mohammad-tuhin Please ensure your build can run locally against Xcode 14.3 on macOS 13 with no issues. It is often the case that configs get updated without projects being tested locally first to ensure none of the major software changes in the image cause things to fall over. Additionally error 65 is commonly related to code signing, so please verify everything is correct in this regard. If you still face issues after this, please reach out to support.

1 Like
6

@bytesguy Even when I specify the resource class (using the g2 as you mentioned) I get the same result as my original comment (with my config defining macos+resource class ~yall’s docs). Also, according to yall’s announcement omitting explicit resource declaration in circle configs should automatically default to gen2,

If your project config doesn’t specify a macOS resource class, jobs will be defaulted to macos.x86.medium.gen2 .

7

@kevnm67 Please reach out to support, it could be an account specific problem as I can’t reproduce the issue.

8

Thank you for reply.
In local it is working perfectly.
In CI, test lane works without problem. But my distribution lane has the above problem.
Now I am reaching out the support about this issue.

9

Thanks for the update.
Is macos.x86.large.gen2 available for this image?
Or just macos.x86.medium.gen2?