bitcode

From what I understood, bitcode allows to generate binaries with an intermediary binary format. So it is the step before compiling to an ARM or x64 architecture. It is possible to create "real" .framework file for iOS since iOS 8. However, framework files are compiled for only one architecture by default (emulator, iPhone). When one wants to distribute a .framework file, it is better to provide a file compatible with the iOS emulator and also deployable to an iPhone. Different examples of scripts can be found to create such a fat file using lipo . However, would it be possible to only

I need to release a framework with bitcode enabled which turns out as a hassle. I set 'Enable Bitcode' in the project's settings to 'YES' and it builds cleanly for both a real device and a simulator. I wanted to test the library so I integrated it to a new app I created for this purpose but now it only build for simulators. When I try to build for a real device I get: ld: '/path/to/Framework.framework/Company(File.o)' does not contain bitcode. You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), obtain an updated library from the vendor, or disable bitcode for this target.

I am preparing an app for ad hoc distribution via Test Flight. I have stepped through (successfully) all of the preparatory steps in this Ray Wenderlich article already ( https://www.raywenderlich.com/48750/testflight-sdk-tutorial ), and I feel confident that the certificate, App ID, and Provisioning Profile are all created correctly and in proper working order. I am on the step in which you archive the project in Xcode. I have selected these settings during the archive process: I choose to Export : I choose "Save for Ad Hoc deployment" since our plan is to use Test Flight to distribute the

Environment: XCode 7.0.1 Module: Objective-C Bundle Type: Framework Hi, I am trying to create a framework to support armv7, armv7s, arm64, i386 and x86_64. I am using aggregate to make the fat library. Inside the aggregate script, i am running two xcodebuild commands 1. for armv7, armv7s and arm64 and 2. for i386 and x86_64 architectures. Also, I have set Enable Bitcode=YES and Other C Flags=-fembed-bitcode under target build settings. As a precautionary mesasure, i am adding ENABLE_BITCODE=YES and OTHER_CFLAGS="-fembed-bitcode" options to the xcodebuild command My xcode build commands are as

Recently i downloaded xcode 7 beta and facing the error: -fembed-bitcode is not supported on versions of iOS prior to 6.0 Is there any work around to fix this issue with out changing deployment target? Thanks in advance. Found this recently, which seems to imply that you need to enable bitcode for each framework. "Xcode 7 has a ENABLE_BITCODE option to embed bitcode in apps, app extensions, and frameworks. The option is turned on by default for iOS and is mandatory for watchOS projects submitted to the store. When bitcode is enabled for a target, all the objects, static libraries and user

I have built an iOS game with Unity. I uploaded it to the App Store (with bitcode enabled). The IPA is about 200 mb. On iTunes Connect, it shows my build size to be about 30mb for each device (which I was very happy to see). But when I added the build to TestFlight, I notice that while downloading via TestFlight, it shows the size to be 170mb. Quite contrary to this question ( TestFlight showing my app size is 4 times less than the actual size ) the size of my app on TestFlight is many times the actual supposed sizes shown on iTunes Connect. Also, iTunes Connect says: TestFlight variants

I'm developing an embbeded framework for iOS. In order to make an universal fat (with simulator and device slices), I created an aggregate target with a script that uses xcodebuild and lipo commands to generate it, as many people does. With XCode 7.x I had to add an user-defined settings with BITCODE_GENERATION_MODE=bitcode in order to enable it, but this has stop working since the last XCode 7.3 release. I've tried everything I found in the internet like add OTHER_CFLAGS="-fembed-bitcode" , but anything works as before... I have seen this in the build log: ENABLE_BITCODE is always NO, no