You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Linux: LC_BUILD_VERSION sdk is the deployment target, apps run in iOS compatibility mode (no Liquid Glass) #456
On Linux, apps built with xtool dev build (SwiftBuild backend) get the deployment target written as the SDK version in LC_BUILD_VERSION:
LC_BUILD_VERSION platform 2 minos 16.0.0 sdk 16.0.0 # built against iPhoneOS27.1.sdk
iOS reads that sdk field as the SDK the app was built with. An app "built with" an SDK older than 26 runs in compatibility mode on iOS 26+: the old tab bar, navigation bars and controls instead of Liquid Glass. The same code built with Xcode 26 gets the iOS 26 design. (App Store processing also rejects such a build with ITMS-90725.)
Minimal repro: a SwiftUI app with platforms: [.iOS("16.0")] and a TabView, built with xtool dev build: sdk 16.0.0, old-style tab bar on device.
Cause
SwiftBuild links the app with swiftc -emit-executable -sdk <iPhoneOS.sdk> .... On Linux the Swift driver hands the SDK to clang as --sysroot. clang's Darwin driver reads SDKSettings.json (and so the SDK version it passes to the linker as -platform_version) only from -isysroot or SDKROOT. Without SDK info it falls back to the deployment target:
Setting SDKROOT in the build environment (in BuildSettings) is not an option: it also applies to host builds, and the package manifest link then fails (swiftrt.o looked up under the iPhoneOS SDK).
Proposed fix
The ld64.lld trampoline written by xtool setup already sits between the driver and the linker. When -platform_version <platform> <min> <sdk> has sdk == min (clang's fallback), it can put back the version of the bundle's SDK for that platform (iPhoneOS27.1.sdk → 27.1). A different, explicit SDK version is kept. PR to follow.
Environment
Host OS: Linux (Arch, x86_64), in a container
iOS device version: iOS 27
Swift version: 6.4.1 (swift-6.4.1-RELEASE)
SDK version: iPhoneOS27.1.sdk (Xcode 27.1 RC)
xtool: built from main-based source (joshuaswarren/xtool @ 7cc56c3, via omarchy-apple-dev). The trampoline and BuildSettings code involved are the same on xtool-org/xtool main (5318ebc).
Duplicate of #351, sorry for the noise: I missed it when searching. It's already fixed on main by #452 (854767c), which isn't in a tag yet. The xtool I tested with (joshuaswarren/xtool @ 7cc56c3) predates that fix, so the last line of the description is wrong: current main doesn't have this bug. Closing, and I won't open the PR I mentioned.
Correction to my closing comment: #452 is on pre/2.x (2.0.0-beta), not on main. main (1.x, 5318ebc) still records the deployment target as the SDK version: the 1.x build path doesn't have the BuildCoordinator that #452 changes. The discussion stays in #351.
Activity
c4software commentedon Nov 19, 2026
Duplicate of #351, sorry for the noise: I missed it when searching. It's already fixed on main by #452 (854767c), which isn't in a tag yet. The xtool I tested with (joshuaswarren/xtool @ 7cc56c3) predates that fix, so the last line of the description is wrong: current main doesn't have this bug. Closing, and I won't open the PR I mentioned.
c4software commentedon Nov 19, 2026
Correction to my closing comment: #452 is on
pre/2.x(2.0.0-beta), not onmain.main(1.x, 5318ebc) still records the deployment target as the SDK version: the 1.x build path doesn't have theBuildCoordinatorthat #452 changes. The discussion stays in #351.