The Xcode version doesn’t really matter because, if necessary, you can re-sign using the codesign
tool. That tool is built in to macOS, not part of Xcode, and thus it’s the macOS version that’s key.
You will have problems using macOS 10.14 for this. Presumably you want to distribute your product independently, which means Developer ID signing, which means notarisation. The recommended tool for that, notarytool
, does not run on 10.14. It should, however, run on 10.15.
IMPORTANT notarytool
is bundle inside modern versions of Xcode, versions of Xcode that won’t run on 10.15. However, it’s fine to extract the tool from Xcode and copy it to 10.15. That’s a workflow we specifically support.
The other thing to watch out for is the code signing version. In macOS 11 we enhanced code signature security by switching to DER entitlements and provisioning profiles. iOS 15 — and it’s corresponding child platforms like iPadOS, tvOS, and watchOS — all require this new format. See Using the Latest Code Signature Format for the details. If you ever want to deploy to one of those platforms, you’ll need at least macOS 11.
However, AFAIK macOS does not currently require this, so you should be OK for the moment on that side.
Finally, there’s one ‘nuclear’ option: Run a modern version of macOS in a VM on your old version of macOS. It won’t be fast, but you don’t need it to be fast just to run codesign
.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"