On Sep 16, 2015, at 12:35 PM, Jens Alfke < email@hidden> wrote:
I decided to search for “bitcode” in the doc viewer in Xcode 7, to see what I could find.The top hit is “Uploading your app to iTunes Connect” (which I can’t link to because the doc viewer sucks.)Searching for “bitcode” on that page, I find:To include bitcode, ensure that “Include bitcode” is checked (bitcode is enabled by default).
Apps you upload to iTunes Connect that contain bitcode will be compiled and linked on the App Store. Including bitcode allows the App Store to apply updates to your app without requiring you to create a new version and resubmit it to App Review.
• For iOS apps, bitcode is optional.
• For watchOS apps, bitcode is required. If you uncheck this box, only the bitcode for the enclosed iOS app is removed.
• For Mac apps, bitcode is not supported and this checkbox doesn’t appear.
So this is documented and not hard to find.
This is a classic Apple documentation mistake: it's in the wrong document. As a developer of OS X applications that use the Accessibility API, I am acutely aware that Apple won't let me put my products in the Mac App Store. As a result, I am in the habit of almost never reading documentation about how to put applications in the Mac App Store or how to use iTunes Connect.
The surprisingly lengthy and emphatic warnings in the Xcode 7 Release Notes about the necessity, without qualification, of using bitcode for Xcode 7 development convinced me that this was definitive documentation. As we all know, for the last few years many new features are documented ONLY in the release notes. It simply did not occur to me that I should read the iTunes Connect documentation -- which is utterly irrelevant to my products -- because that is where Apple would tell me that I do not need to pay any attention to the Xcode 7 Release Notes about bitcode.
But, anyway, thanks for the reference. Now I can contact my customers and tell them, with confidence and egg on my face, Never mind, you don't have to worry about bitcode when you use my frameworks, after all.
|