{"id":38942,"date":"2023-04-03T14:01:19","date_gmt":"2023-04-03T18:01:19","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=38942"},"modified":"2025-10-11T12:18:07","modified_gmt":"2025-10-11T16:18:07","slug":"xcode-14-3","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2023\/04\/03\/xcode-14-3\/","title":{"rendered":"Xcode 14.3"},"content":{"rendered":"

Apple<\/a>:<\/p>\n

Clang and the build system support a new mode for building module dependencies called explicit modules which improves build performance, reliability, and correctness. The new mode is opt-in, and can be enabled by setting _EXPERIMENTAL_CLANG_EXPLICIT_MODULES<\/code> as a user-defined build setting in C and Objective-C projects which build with modules enabled.<\/p>

[…]<\/p>

Xcode now prompts a user prior to performing a clean action. This prompt can be bypassed by holding the option key while performing a clean, or by permanently hiding the prompt by enabling the “Don’t Ask Me” setting within the prompt.<\/p>

[…]<\/p>

Run scripts in a scheme’s pre-actions and post-actions for the Build section now cause the build to fail if any run script exits with a non-zero exit code, instead of reporting a false-positive successful build.<\/p>

[…]<\/p>

When a pre-build scheme action (such as compiling a package plugin) encounters an error, the status message at the top of Xcode’s workspace window sometimes doesn’t update. This leaves the previous status showing, possibly causing confusion if the previous status was “Build Succeeded.”<\/p>

[…]<\/p>

Xcode automatic signing now creates managed provisioning profiles for Developer ID. This resolves an issue that caused Xcode to throw an error when cloud signing with a Developer ID certificate during the app distribution workflow. <\/p>

[…]<\/p>

The timeout<\/code> argument of XCTestCase.wait(for:timeout:enforceOrder:)<\/code> and related methods is now optional—if you don’t specify it, the function waits indefinitely (until the overall test times out.) To ensure reasonable execution time, set an appropriate value for the executionTimeAllowance<\/code> property of the running XCTestCase<\/code> instance (self<\/code>).<\/p><\/blockquote>\n\n

The extra pieces can be downloaded here<\/a>, though the Additional Tools are still only at RC status.<\/p>\n\n

The two main changes I noticed are that there’s now an annoying animation when I use Open Quickly…<\/strong> and that tests now need a deployment target of macOS 12. This created a bunch of work silencing deprecation warnings, which is kind of silly because the code being tested runs on macOS 10.13 and so can’t depend on the newer APIs, anyway.<\/p>\n\n

I had to turn off the new module verifier because it warned about double-quoted includes even though I had turned off that warning. (I use such includes to be able to use the same file both in a framework and when I want to include a few individual files in a standalone binary.)<\/p>\n\n

Heath Borders<\/a>:<\/p>\n

TIL Xcode 14.3 Beta isn’t supported under Rosetta. This means that if your iOS project uses x86 libraries, you won’t be able to run the project on an x86 iOS Simulator on an arm64 mac anymore.<\/p>

You’ll either have to go back to an x86 mac to run your project or you’ll have to add arm64 slices to your libraries.<\/p><\/blockquote>\n\n

Jonathan Grynspan<\/a>:<\/p>\n

New in Xcode 14.3: if you’re using XCTestExpectation<\/code> or XCTWaiter<\/code> from an async Swift function, you’ll get warnings when using wait(for:timeout:)<\/code> because that synchronous function may deadlock. Switch to fulfillment(of:)<\/a> instead for maximum Swiftiness!<\/p><\/blockquote>\n\n

Christian Selig<\/a>:<\/p>\n

\n

If Xcode 15 released and the only feature was it was cured of hallucinating ghost errors I would stand up out of my chair and clap.<\/p>\n<\/blockquote>\n

With the last several releases of Xcode, I’ve seen a lot of fake errors, as well as problems with builds not working properly unless I manually clean the folder first. The Swift compiler still crashes every day.<\/p>\n\n

Nick Lockwood<\/a>:<\/p>\n

PSA: If you’re an Apple dev who hasn’t updated to Ventura for whatever reason, the usual trick of editing the Minimum system version in the Xcode 14.3 Info.plist seems to get it running just fine on Monterey.<\/p><\/blockquote>\n\n

Previously:<\/p>\n