Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SR-14119] Enable bitcode by default for simulator variants while creating a xcframework #56500

Open
swift-ci opened this issue Jan 28, 2021 · 0 comments
Labels

Comments

@swift-ci
Copy link
Collaborator

Previous ID SR-14119
Radar None
Original Reporter deepesh.vasthimal@checkout.com (JIRA User)
Type Task
Additional Detail from JIRA
Votes 0
Component/s
Labels Task
Assignee None
Priority Medium

md5: 1fef0ac13dbaa8f7f871f159eda13ac0

Issue Description:

When we create a xcframework we get 2 variants of it which are ios-arm64 and ios-x86_64-simulator. The ios-arm64 gets bundle with the app running on devices and also gets into the app store. Where as ios-x86_64-simulator is not bitcode enabled by apple by default. However adding bitcode enabled to ios-x86_64-simulator variants is not restricted but can be done by developers if needed.

The need for bitcode enabled simulator variants of xcframework is required if the ios-x86_64-simulator variant needs to be protected and further processed for code obfuscation, string encryption etc. Every time, when the app is being protected, we extract the bitcode from your .xcframeworks binary files and protect it using LLVM-C++ API (https://llvm.org/docs/LangRef.html). Once it is protected we compile it to get a new binaries

If apply by default allows the bitcode for x86_64-simulator variants of the xcode to happen then we don't have to make any efforts, which will only help the community who is trying to develop xcframeworks which are protected against reverse engineering.

Thanks

Deepesh

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant