The Xcode 14.3 image has been released on Gen2 Intel resource class and can be selected as follows:
This image includes some breaking changes
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.
VM Image Info
Xcode 14.3 Build version 14E222b is installed at /Applications/Xcode-14.3.app
The full manifest of installed software can be found here
[14:39:33]: Exit status: 65
[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]: - Specify the Xcode version in your Fastfile
[14:39:33]: ▸ xcversion(version: "8.1") # Selects Xcode 8.1.0
[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]: - Manually update the path using
[14:39:33]: ▸ sudo xcode-select -s /Applications/Xcode.app
@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.