Problem: App Store rejects app containing Rust with bitcode error #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There is a python program used by Apple (included inside the Xcode.app bundle) which verifies a program's bitcode as part of rebuilding it. It includes a check that each bitcode object has valid clang parameters included as part of its XML xar header. The Rust compiler sensibly chooses not to emit any clang parameters, since it is not clang. Unfortunately this means any Rust-emitted bitcode will not pass app store verification. Locally, it produces an error like this one: ``` error: Clang option verification failed for bitcode 0038 (argument -emit-obj is required) ``` Through App Connect, it produces an error like this one: ``` ITMS-90562: Invalid Bundle - The app cannot be processed because options not allowed to be embedded in bitcode are detected in the submission ``` Solution: Patch Rust so that it will embed exactly the same clang cmdline that Xcode/clang will when emitting Bitcode. This patch is relatively brittle and not upstreamable in this form, but it serves well to demonstrate the problem and is likely to be a workable solution for now for anyone who wants to ship code.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is a python program used by Apple (included inside the Xcode.app bundle) which verifies a program's bitcode as part of rebuilding it. It includes a check that each bitcode object has valid clang parameters included as part of its XML xar header.
The Rust compiler sensibly chooses not to emit any clang parameters, since it is not clang. Unfortunately this means any Rust-emitted bitcode will not pass app store verification.
Locally, it produces an error like this one:
Through App Connect, it produces an error like this one:
Solution: Patch Rust so that it will embed exactly the same clang cmdline that Xcode/clang will when emitting Bitcode.
This patch is relatively brittle and not upstreamable in this form, but it serves well to demonstrate the problem and is likely to be a workable solution for now for anyone who wants to ship code.