Bitcode signature failure in Xcode

Question

I updated Xcode to the last version, and now when I'm trying to compile the project I'm getting an error "Invalid bitcode signature", hovewer, the bitcode for my project is disabled. How can I fix it? What should I change to sign my bitcode correctly?

My Podfile:

source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '8.0'
use_frameworks!

target 'MyProjectName' do

pod 'Realm'
pod 'CorePlot'
pod 'GoogleMaps'

end

I checked already, everything is fine with it.

We need more information. I suspect one of the used dependencies is causing the problem. — shallowThought, Apr 03 '17 at 10:35
When looking for debug help you need to provide the Podfile.lock, not the Podfile. And the exact version of Xcode preferably. — Cœur, Apr 11 '17 at 15:40

score 32 · Answer 1 · answered Apr 09 '17 at 01:21

32

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

answered Apr 09 '17 at 01:21

Vincent

1,386
9
9

1

Thank you! I was banging my head against the wall with XCode 8.3 and 8.3.1 all complaining about "Invalid bitcode signature" until I changed this. – Josh Apr 09 '17 at 20:22
Thanks, I have been trying to work this out for ages - I had bitcode turned off and this error still came up until I set Build Active Architecture to YES – wheeliebin May 05 '17 at 16:22
My savior! Hero without cap! – Teofilo Israel Vizcaino Rodrig Jan 18 '18 at 14:53
How come you don't get the same error when archiving the app for publication ? `Build Active Architecture Only` is still NO for Release mode. – Sébastien Jan 16 '19 at 10:16

score 8 · Answer 2 · answered Oct 21 '17 at 14:37

8

I experienced this error, but it happened only when building for an iOS 10.3 iPad (despite working on an iOS 10.3 iPhone and an iOS 11.0 iPad, and all the iOS 10.3 and 11.0 simulators). Through painful process of elimination (and creating a new project from scratch), I found that my Cocoapods weren't at fault, nor was my code signing settings, nor my AppExtension, nor my tests, nor my 'build for active architecture only' setting, nor any build setting related to the term 'bitcode'.

In my setup, I had a C++ Xcode project nested within my main Swift/iOS Xcode project. Because it was never intended specifically for use in iOS, the "iOS Deployment target" had never been set (it was left on 'default'). Upon setting it explicitly to 10.3, it worked without complaint.

Nested C++ app's project settings (set iOS deployment target to the lowest iOS version you support):

Nested C++ app's target settings (for reference):

answered Oct 21 '17 at 14:37

Jamie Birch

5,839
1
46
60

1

Awesome, tried everything finally got it working. Thanks a lot. – Jas_meet Nov 08 '17 at 07:06
@Jas_meet Glad that I could save someone else from this plight! One of the hardest errors I've ever had to track down (especially given how slow build times are). – Jamie Birch Nov 08 '17 at 14:48
1

I had this same issue... project was working on an iPhone with iOS 10.2 but not one with 10.3.3. Thank you! – stephenspann Jan 23 '18 at 22:25
1

Thanks so much, this saved me. I didn't even realise the app I'm working on had a nested project - it's a cordova app. – elRobbo Oct 17 '18 at 03:27

score 3 · Answer 3 · answered Apr 03 '17 at 10:54

3

If you using pod then please check the version of all libraries, some library may be not supporting in new version , you have to update pod files for that library.

answered Apr 03 '17 at 10:54

Rajeev Singh

198
1
11

score 3 · Answer 4 · answered Sep 07 '17 at 21:20

3

In my case, I was trying to build for a device with an iOS version lower than the deployment target.

answered Sep 07 '17 at 21:20

awph

566
6
15

score 3 · Answer 5 · answered Oct 23 '17 at 17:47

This kind of problem came up when I linked a new static library project to my workspace. In order to solve it I tried to set both the Build Active Architecture Only and the Bitcode settings of the library to NO but no luck. Then I got across the thing that the library's Deployment Target was set to 11.0 as Xcode set the latest value to all new projects. After fixing the setting to 5.0 the problem was solved.

score 2 · Answer 6 · answered Sep 12 '17 at 14:19

On my case problem occured because of I was using a 3rd party static library with different files for each architecture

I fixed the problem by removing binaries of invalid architectures. Instead I added a multi-arch FAT binary for the 3rd party static library

Hope helps

score 1 · Answer 7 · answered Apr 13 '17 at 20:08

1

For my case, the solution was removing a c++ library.

answered Apr 13 '17 at 20:08

Oded Harth

4,367
9
35
62

It's possible that setting the iOS deployment target, rather than removing the C++ library altogether, would have sufficed: https://stackoverflow.com/a/46864401/5951226 – Jamie Birch Oct 21 '17 at 14:39

score 1 · Answer 8 · answered May 26 '17 at 19:54

1

I found that my issue was with using 'Modules'.

Just turned off modules (had to update some header files), but that resolved my issue.

Enable Modules In Settings

answered May 26 '17 at 19:54

LowAmmo

351
2
4

1

Don't know your case but disabling modules is not a good idea – qwerty Sep 12 '17 at 13:44

score 1 · Answer 9 · answered Aug 11 '17 at 01:17

In my case, the widget included in the project was causing the bitcode error.

I changed my pod file from this:

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

target "App Widget" do
    pod 'A'
end

to this:

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

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

score 1 · Answer 10 · answered Oct 24 '18 at 00:13

To fix this issue, most answers recommend a workaround whereby you clean your Xcode workspace/project, close Xcode, delete your Derived Data folder (this is kept in the root directory of your project by default), then finally re-open your project.

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

When the bitcode intermediary representation of your project was released with iOS 9.0, it was done so on the provision that your entire project, including dependencies, either totally agree to use bitcode or not. From my experience, it is vital to work through all of your Pods and included Libraries/Frameworks and ensure they all use the same setting; either Yes or No. By default, this selection is Yes.

If a single dependency does not match the intended bitcode setting, this error can be thrown.

When sanity checking your dependencies and overarching project, it is important to note that there is a Use Bitcode setting for both the Project and the Target settings, so be sure to check both perspectives of the Build Settings.

score 0 · Answer 11 · answered Nov 15 '17 at 09:36

0

I was adding static library . I created fat binary of the same library including all architectures and included in my project. This resolved my issue

answered Nov 15 '17 at 09:36

sonali

165
3
9

score 0 · Answer 12 · answered Jan 17 '18 at 11:44

0

In my case, I am Using Cordova Project. While building it with Xcode had the same issue and Resolved by Removing and Adding the IOS platform.

cordova platform remove ios

cordova platform add ios

answered Jan 17 '18 at 11:44

RAJESH KUMAR ARUMUGAM

1,560
21
35

score 0 · Answer 13 · answered Apr 03 '18 at 19:08

0

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

answered Apr 03 '18 at 19:08

Kartik 123

1,032
1
7
5

jiexishede · Answer 14 · 2018-12-03T03:15:53.810

0

Targets -> Build Settings ->Build Active Architecture Only

Debug -> YES Release -> NO to YES

I face the same problem only on archiving the app.

Who can tell me the reason? You can teach all developers. It's awesome.

edited Dec 03 '18 at 03:15

answered Nov 21 '18 at 11:48

jiexishede

2,473
6
38
54

score 0 · Answer 15 · answered Feb 09 '19 at 07:07

0

This solution work for me. First, try to remove all pod using terminal command pod deintegrate and then reinstall pod using terminal command pod install.

answered Feb 09 '19 at 07:07

Ashish

706
8
22

score 0 · Answer 16 · answered Feb 13 '19 at 22:41

0

This can also occur when building for the simulator if including a framework built for ARM only (and I assume vice-versa as well).

answered Feb 13 '19 at 22:41

ion

179
1
5

Bitcode signature failure in Xcode

16 Answers16

Linked

Related