From this Apple Developers Forum discussion, user dshirley and bwilson suggest using command line tools otool and grep to check if bitcode sections exist. $ otool -l libName.o | grep __LLVM or $ otool -l MyFramework.framework/Versions/A/MyFramework | grep __LLVM Running the above command, if the library contains bitcode you will see segname __LLVM output.
I am facing the same problem. What my suggestion is just enable this check mark when export for iOS App Store Deployment. If you are exporting an adhoc build then do uncheck it. It will work fast.
Try some tricks -> Clear derived data & reopen xcode. Select proper sign in / certificate, or try to re add account in xcode Make sure if your pods supported bitcode if not then you need to set bitcode to NO (Go to Project Build setting search for bitcode & set it to NO. Hope … Read more
As it was alread written in other answers, otool -l yourlib.a | grep __LLVM is the way to go. An Apple engineer says using otool -l yourlib.a | grep bitcode is not reliable. Searching for a “bitcode” section is not a reliable way to detect if your files contain embedded bitcode. If you want to … Read more
When you build the library normally, with ENABLE_BITCODE=YES, Xcode adds the build flag -fembed-bitcode-marker to any clang invocation, placing an “empty” bitcode in the final o file. So, if you look to the compile action in the build phase, it will look something like: CompileC {build_path}/StaticBitcode/StaticLogger.o StaticBitcode/StaticLogger.m normal armv7 objective-c com.apple.compilers.llvm.clang.1_0.compiler cd {path}/StaticBitcode export LANG=en_US.US-ASCII … Read more
When building static libraries you must add the following for bitcode generation: -fembed-bitcode for a dynamic library you need to additionally link with -fembed-bitcode Note: This command is only available with Xcode7+ In regards to the accepted answer of using -fembed-bitcode-marker You should be aware that a normal build with the -fembed-bitcode-marker option will produce … Read more
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 … Read more
To set this setting in a way that doesn’t get overridden each time you do a pod install you can add this to your Podfile post_install do |installer| installer.pods_project.targets.each do |target| target.build_configurations.each do |config| config.build_settings[‘ENABLE_BITCODE’] = ‘NO’ end end end
Update: Good news everyone! Google Analytics now supports Bitcode with their 3.14 release. You can grab it from their download sources, however its not listed on Cocoapods yet. Google Analytics SDK Download Change Log Original: Google needs to compile their analytics SDK into a bitcode library. However, from previous experience with Google updating their libraries … Read more
Bitcode is a compile-time feature (not a link-time feature) which means that every .o file should contain an extra section called __bitcode when built with bitcode. You can confirm whether your binary is bitcode-compatible by running otool -l (my .o or .a file) | grep __LLVM. When you build normally, Xcode adds the build flag … Read more