Xcode 16.2
The Command Line Tools package now supports using the
swift testcommand to build and run package tests written with Swift Testing.[…]
Sometimes running parallel Tests on macOS run destinations never finishes.
[…]
macOS projects that use hardened runtime but no sandboxing may run into timeout errors when attempting to preview if the project is complex enough.
[…]
Simulator process launch may stall for around 3-5 minutes per runtime as GateKeeper scans the simulator dyld shared cache.
[…]
Memory leaks can occur when calling async functions bridged from Objective-C and building in the Swift 6 language mode.
Workaround: Pass
-checked-async-objc-bridging=offto the Swift compiler using “Other Swift Flags” in Xcode build settings.
“Swift Assist is coming later this year,” said Apple in June. It’s now December [11th], so that means we’re only a few weeks from seeing it in action – Xcode 16.3 beta 1, presumably?
Previously:
Update (2024-12-23): Daniel Jalkut:
However, when I add this value to OTHER_SWIFT_FLAGS (either in the Xcode build settings interface, or in an .xcconfig file), it yields a build error:
error: Driver threw unknown argument: '-checked-async-objc-bridging' without emitting errors.
This happens for me, too.
Update (2025-01-07): robinkunde:
It’s a frontend option, so you need to prefix it with
-Xfrontend. Example:swift -Xfrontend -checked-async-objc-bridging=off main.swift
Do you reckon anyone at uses anything remotely like a release build of Xcode day-to-day?
The test navigator does this on every project that I run tests on, on every Mac I have access to with every 16.x release and beta of Xcode.
