Bitcode Signing Error in Xcode

Question

I updated Xcode to the latest version, and now when I try to compile the project, I get the error "Invalid bit code signature", hovewer, the bitcode for my project is disabled. How can i fix this? What should I change to sign my bitcode correctly?

My subfile:

source 'https://github.com/CocoaPods/Specs.git' platform :ios, '8.0' use_frameworks! target 'MyProjectName' do pod 'Realm' pod 'CorePlot' pod 'GoogleMaps' end 

I already checked, everything is fine with him.

Answer 1

I'm not sure that I have the same situation. I only have this problem when I tried to test the iPhone device. It turns out that the debug configuration with Build Active Architecture Only is set to NO. After I installed YES, I can check my iPhone.

Answer 2

I experienced this error, but it only happened when I created the iPad iOS 10.3 (despite working with the iOS 10.3 iPhone and iOS 11.0 iPad, as well as all the simulators iOS 10.3 and 11.0). Due to the painful elimination process (and creating a new project from scratch), I found that my Cocoapods were not to blame, nor were there my code signing settings, nor my AppExtension, nor my tests, nor my "build for active architecture" settings or any assembly settings associated with the term "bitcode".

In my installation, I had an Xcode C ++ project embedded in my main Swift / iOS Xcode project. Since it was never intended specifically for use on iOS, the “iOS Deployment Goal” was never set (it remained “default”). By setting it explicitly to 10.3, it worked without complaint.

Nested C ++ application project settings (set the goal of deploying iOS to the lowest version of iOS that you support):

Nested C ++ application target settings (for reference):

Answer 3

If you use pod, please check the version of all libraries, some libraries may not be supported in the new version, you need to update the pod files for this library.

Answer 4

In my case, I tried to create a device with an iOS version below the deployment target.

Answer 5

In my case, the problem arose because I used a third-party static library with different files for each architecture

I fixed the problem by deleting the binaries of the invalid architectures. Instead, I added a multiscreen FAT binary to a third-party static library

Hope helps

Answer 6

This problem arose when I linked a new static library project to my workspace. To solve this problem, I tried to set both Build Active Architecture Only and the Bitcode library settings to NO, but no luck. Then I realized that the Deployment Target platform is set to 11.0, since Xcode sets the last value for all new projects. After fixing parameter 5.0, the problem was resolved.

Answer 7

In my case, the solution deleted the C ++ library.

Answer 8

I found that my problem was using the "Modules".

Just disabled the modules (I had to update some header files), but this solved my problem.

Enable modules in settings

Answer 9

In my case, the widget included in the project caused an error in the bitcode.

I changed the pod file from this:

 target "App" do pod 'A' pod 'B' end target "App Widget" do pod 'A' end 

:

 target "App" do pod 'A' pod 'B' target "App Widget" do pod 'A' end end 

Answer 10

To fix this problem, most answers recommend a workaround, according to which you clear the workspace / Xcode project, close Xcode, delete the Derived Data folder (it is stored in the root directory of your project by default), and then finally reopens your project.

However, the above steps may not work for you. This is a hint that your project structure is wrong.

When an intermediate representation of your bit code for your project was released using iOS 9.0, this was done on the condition that your entire project, including the dependencies, fully agrees to use the bit code or not. In my experience, it is very important to work through all your Pods and enable Libraries/Frameworks and ensure that they all use the same setting; either Yes or No. By default, this selection is Yes .

If one dependency does not match the specified bit code setting, this error can be selected.

When checking the sanity of your addiction and a comprehensive project, it is important to note that there is a Use Bitcode installation for both the project and the target parameters, so be sure to check both perspectives of the build parameters.

Answer 11

Goals → Build Settings → Built-in Active Architecture Only

Debugging → YES Release → NO to YES

I encounter the same problem only when archiving the application.

Who can tell me the reason? You can teach all developers. This is amazing.

Answer 12

I added a static library. I created a live binary copy of the same library, including all architectures and included in my project. This solved my problem.

Answer 13

In my case, I am using the Cordoba Project . Building it with Xcode had the same problem and was resolved by removing and adding the iOS platform.

 cordova platform remove ios cordova platform add ios 

Answer 14

If you are using cocoa pods, do "pod update"