You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Additional Detail from JIRA
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
The text was updated successfully, but these errors were encountered: