I have asked this question on the Apple forum and an Apple engineer answered that I should build against the latest SDK and hunt down the bug which admittedly feels wrong since it’s not there when building against the older SDK so I wouldn’t even know where to start looking. So I have to assume it has something to do with the version of macOS that is used to build against. When he switches back to the official release version the issue returns immediately. When a user reported a bug with a release build now we sent him a debug build which was built on macOS 10.14.6 and Xcode 11 (targeting the 10.14 SDK) and the issue is gone.

With the latest version of Xcode this doesn’t seem to be possible anymore so we thought we’d just do it the “official” way then: targeting the most recent macOS SDK and only setting the deployment target. 3,353 3 14 39 Add a comment 5 Answers Sorted by: 84 The solution is very simple. In the last years and with older versions of Xcode we have always installed older macOS SDKs (using publicly available scripts) and used them to build against as we have run into several issues when building against the latest SDK version and only setting the deployment target to an older version. We’re using a 2018 Mac mini running macOS 10.15.7 for the release builds with Jenkins.

We have a macOS app that supports macOS 10.12 and later.

Xcode older versions