Added unit testing target to Xcode - failed to import bridging header won't go away

Question

I added a new Test target to my Xcode project. My project has Swift code and Objective-C code, and has a bridging header. Upon either adding the bridging header to UnitTesting's build settings, or doing import MyTarget, I'm getting the error:

failed to import bridging header

I've tried:

Adding the bridging header to project, unit testing and main target's build settings.
Changing defines modules to Yes.
Moving the bridging header file to the root folder.

I've also tried making a sample project, which built and worked fine. Taking everything I have over into a clean new project isn't an option at this point.

Did you get any progress with this? I have the same problem... — Manuel M., Mar 06 '15 at 10:27
@ManuelM. add `${SDKROOT}/usr/include/libxml2` to project's Header Search Paths. Let me know if that works for you. — Andrew, Mar 06 '15 at 12:29
@swalkner it got solved with further versions of Xcode. Eventually it worked. I don't really know what I did different, sorry. I think I added some needed Frameworks in the bridging-header. — Manuel M., Oct 21 '15 at 11:34
Possible duplicate of [Issue testing and using Cocoapods in a Swift project](http://stackoverflow.com/questions/25495225/issue-testing-and-using-cocoapods-in-a-swift-project) — deoKasuhal, Apr 19 '16 at 22:36

score 55 · Answer 1 · edited Jun 15 '20 at 18:42

55

If you use CocoaPods as package manager, must set search path etc. Give a simple way,

Try adding this in your Podfile:

target 'YourProductTests' do
    inherit! :search_paths
    # Pods for testing
end

and pod install

It works for me.

If the above solution does not work for you, try setting manually:

Click your Test target -> Build Setting-> tab: All & Combined -> Swift Compiler -Code Generation -> Objective-C Bridging Header : add your xxx-bridging-header
Check "Search Path", set up value of Framework Search Path, Header Search Paths, Library Search Path according to your main target. Maybe some search path lose here, manually add again.

edited Jun 15 '20 at 18:42

shim

9,289
12
69
108

answered Jul 28 '16 at 08:14

Victor Choy

4,006
28
35

Second option worked for me. Wasn't using CocoaPods. – Mark Jun 13 '19 at 05:02
This works. is this thing documented anywhere ? how can i find more about why we have to use `inherit! : search_paths` – Awais Fayyaz Feb 26 '20 at 07:48
cannot thank you enough for this solution! worked like a charm! – Mahesh De Silva Sep 02 '21 at 09:42

score 21 · Answer 2 · answered Feb 07 '19 at 11:52

21

@Victor Choy solution works for me, but I had to move test target inside product target like so:

target 'YourProduct' do

   # Pods for product

   target 'YourProductTests' do
      inherit! :search_paths
      # Pods for product testing
   end
end

This did not work for me:

target 'YourProduct' do
   # Pods for product
end

target 'YourProductTests' do
   inherit! :search_paths
   # Pods for product testing
end

answered Feb 07 '19 at 11:52

mkkrolik

1,200
14
21

Yes., ur solution is worked. If u know reason, pls do comment – McDonal_11 Sep 09 '20 at 18:29

score 10 · Answer 3 · answered May 24 '18 at 11:03

I faced the same problem. I did the following and the issue of 'Failed to import bridging header' is solved.

Steps:

Select your project -> Build settings -> Search for 'Defines module' -> give 'YES'
Copy Objective-C bridging header path
Select your test target -> Build setting -> Swift compiler - General -> Objective-C bridging header -> Give Bridging header path.
Make sure 'Header Search Paths' of test targets contains all the headers in ios Targets. Add them if any of the headers are missing.
Build.

Reference: Refer this link.

Unfortunately that link is obsolete. – ThomasW Jul 18 '20 at 03:21 — ThomasW, Jul 18 '20 at 03:21

score 7 · Answer 4 · answered Jun 18 '20 at 18:22

This may be useful for someone: if the Unit Test target is added to an existing project which already includes CocoaPods and some Objective-C library pods.

Below steps solved the Failed to import bridging header issue.

Select your Project -> Build Settings -> Search for 'Defines module' -> give 'YES'
Copy Objective-C Bridging Header Path from 'YourProduct' target and paste it in the 'YourProductTests' target's bridging header path.
Podfile should have 'YourProductTests' target inside 'YourProduct' and should include the _inherit! :search_paths_ like below

...

target 'YourProduct' do
   # Add Pods for your product here...

   target 'YourProductTests' do
      inherit! :search_paths
      # Pods for product testing, if any
   end
end

Then perform 'pod install' from the root folder of the project. This fills the Header Search Paths for 'YourProductTests'.
As a last step verify that both 'YourProduct' and 'YourProductTests' target's Header Search Paths should be similar.

score 6 · Answer 5 · answered May 23 '15 at 17:12

At this point, I've never had to import MyTarget to get unit tests to work in Swift.

Common Solutions

I assume you tried it, but it wasn't clear if you added your bridging header to your app target and test target at the same time?
Another option, that may not be ideal, is to add a bridging header in your test target so that you actually have 2 bridging headers. They should look the same and would be a good test.
If using $(SRCROOT) to reference your bridging header path, ensure it is being evaluated to correct path.
If all else fails, you should do file diff of your .xcodeproj with the one of your working project and match any relevant values that might be different.

The bridging header system isn't perfect, but here are a few issues I've run into.

score 1 · Answer 6 · answered Oct 23 '22 at 16:29

For me, on a project without Cocoapods, I had one place, indistinguishable from other similar tests, where this warning would just not go away. I had a bridging header for the tests, but it was empty.

What cleared it for me, was going to the tests target > Build Settings > Objective-C Bridging Header and hit the delete key (should clear the link to the header file).

Added unit testing target to Xcode - failed to import bridging header won't go away

6 Answers6

Linked