According to the documentation, Xcode is supposed to be able to build for macOS 10.13 and up. However, this does not seem to be the case in practice; my testers on 10.14.6 have reported random crashes when trying to test my app when built with Xcode 15 beta. I've isolated the code that crashes to a simple test case, and posted it on GitHub Issues, but it seems to have attracted no attention:
I've reproduced the bug in Xcode 15 beta 5, beta 6, and beta 7.
What's more, I decided to spin up a macOS 10.13 VM in UTM to see what would happen there. On 10.13 it doesn't even launch:
dyld: Library not loaded: @rpath/libswiftCore.dylib
Referenced from: /Users/csrstka/Desktop/crashtest
Reason: image not found
Abort trap: 6
It seems that Xcode 15 is not correctly including the embedded Swift libraries for use on macOS versions older than 10.15. On macOS 10.14.6, it seems there are embedded Swift libraries in /usr/lib/swift, but they are apparently buggy and not compatible with modern Swift code. The net result is that although it claims to be able to build for 10.13, the effective minimum target is 10.15, and this should either be fixed before release, or the documentation should be updated to reflect the change.
Command line tools don’t have embedded Swift libraries; the user has to install the “command line support for Swift” package from Apple or something if their OS predates ABI stability. But the crashes on OSs that do have /usr/lib/swift are indeed concerning.
We're seeing this crash on 10.13 for a macOS desktop app. The app uses a Swift Module that's been compiled with 10.13 support but causes the app to crash at launch with this error requires version 45.0.0 or later, but libswiftAppKit.dylib provides version 1.0.0
Any idea what needs to be done other than asking users to install Swift 5 runtime support? This same app worked just fine when compiled with Xcode 14.
I can confirm that it still happens with Xcode 15.0. I got alerted after receiving a negative review for my App Store app after publishing an update built with Xcode 15.0, which I thought still supported macOS 10.13. Why does it take so long to fix this issue?