Getting "file not found" in Bridging Header when importing Objective-C frameworks into Swift project

Question

I have a Swift project for which I'm trying to import ObjC-based frameworks. The framework is located in a directory under the project's path and is referenced by the project in Xcode. It's also added to the "Link Binary with Libraries" in the project's 'Build Phases' page.

However, for some reason, I can't seem to include the framework in the Bridging-Header file. I get the following error:

BridgingHeader.h:5:9: error: 'Parse/Parse.h' file not found
#import <Parse/Parse.h>
        ^
<unknown>:0: error: failed to import bridging header 'BridgingHeader.h'

Things I've checked:

The "Install Objective-C Compatibility Header" is set to "YES".
The Header Search Paths includes the path to the frameworks.

I'm sure I'm missing something, so if anyone has any clues, that would be great.

i forgot to put library path in Header Search Paths, in this case question helped :D — Aishwat Singh
– Aishwat Singh, Commented Jun 25, 2016 at 8:55

Dia Kharrat · Accepted Answer · 2015-01-19 17:32:39Z

94

Found a solution:

The "Objective-C Bridging Header" setting (aka SWIFT_OBJC_BRIDGING_HEADER) must be set at the Target level, and NOT the Project level. Be sure to delete the setting value at the Project level.

(to me, it seems like an Xcode bug, since I don't know why it fixes it).

edited Jan 19, 2015 at 17:32

answered Jan 18, 2015 at 6:26

Dia Kharrat

6,0463 gold badges34 silver badges44 bronze badges

Sign up to request clarification or add additional context in comments.

9 Comments

Jojodmo Over a year ago

This is really weird, I had the same error and it turns out I had the header defined at the Project level. Even though I already had it defined at the Target level, I had to remove it from the Project level in order to allow for third-party Frameworks to be added. It defiantly seems like it's a Xcode bug.

Davlat Mirmanov Over a year ago

@MarcoAlmeida, if you have tests target, try to remove "Objective-C Bridging Header" setting from that too. It should help.

Mike K Over a year ago

Hey there! Have the same issue here :( Although it is not resolved with the described above method...

nacho c Over a year ago

How can I do it set it?

Oliver Eichhorn Over a year ago

This worked for me in Xcode 9.2. Still not fixed after that many years...

|

jamesthakid · Accepted Answer · 2016-02-12 16:37:13Z

62

I have the same issue. I changed all my imports from #import "HMSegmentedControl.h" to #import <HMSegmentedControl/HMSegmentedControl.h> for example.

edited Feb 12, 2016 at 16:37

answered Feb 12, 2016 at 11:13

jamesthakid

1,26510 silver badges12 bronze badges

3 Comments

NaXir Over a year ago

To work with cocoapods this is necessary. In Bridging header never import a pod as #import "abc.h" user #import <abc/abc.h> Thumbs up.

Mashhadi Over a year ago

In my case I converted #import <ios-qr-encoder/UIImage+MDQRCode.h> to #import "UIImage+MDQRCode.h" and it worked

Itai Spector Over a year ago

You are the king

Rainer Schwarze · Accepted Answer · 2015-04-27 18:02:31Z

30

I had to add my lib directory in User Header Search Paths:

test target settings - user header search path

In my case the lib directory contains the .a-library file and some header files. These are included in the bridging header file. However, the swift compiler wouldn't find them. Only when I added ${PROJECT_DIR}/lib to the User Header Search Path it built the test target.

(I am using Xcode 6.2 on Mavericks 10.9.5)

answered Apr 27, 2015 at 18:02

Rainer Schwarze

4,7451 gold badge29 silver badges51 bronze badges

3 Comments

bizz84 Over a year ago

I could resolve this issue by adding Pods/* to the Header Search Paths of the main target. Interestingly, I did not have this problem before adding Swift frameworks as dependencies to my target. Xcode 7 beta 6.

Chris Livdahl Over a year ago

This was exactly what worked for me. I have a framework included in my project that contains library (.a). I had to create a search path to the headers for the library in the User Header Search Paths.

thibaut noah Over a year ago

Also had to import Pods/library folder, thank you so much !

Dan Jackson · Accepted Answer · 2015-03-06 23:30:04Z

17

We encountered the same error message, with a completely different cause.

Setup:

App target, all Obj-C code
Unit Test target with a single swift test case & a bridging header referring to app code

When we added the second swift test case, after a clean (or on a team mate's machine), we saw this error when building the unit test target.

It was fixed by adding a dummy Obj-C class to the unit test target.

answered Mar 6, 2015 at 23:30

Dan Jackson

4513 silver badges5 bronze badges

4 Comments

user463112 Over a year ago

Thank you. This absolutely worked despite making absolutely no sense.

clozach Over a year ago

I was able to delete the dummy Obj-C class afterwards. My guess is that a side effect of this solution is the creation of a test-target-specific bridging header, which in turn (I suspect) causes Xcode to ignore the host application's bridging header.

clozach Over a year ago

Addendum to above: after doing a clean build, I started getting a segmentation fault 11 during compile. After some trial and error, it appears that the dummy .m file has to be present, but it can be empty. Madness.

neoneye Over a year ago

Adding a dummy objc class to my test target, fixed it for me!

Ankit Goel · Accepted Answer · 2015-09-02 11:20:35Z

5

If using cocoapods, try reinstalling the pods by running the following command.

pod install

answered Sep 2, 2015 at 11:20

Ankit Goel

6,5154 gold badges38 silver badges48 bronze badges

1 Comment

Mete Over a year ago

This helped me since I'd recently created a new Configuration that wasn't compiling (the same file not found issue), while the other configurations (Debug and Release) were. pod install seems to be required for any new configurations added...

Nicoara Talpes · Accepted Answer · 2017-02-23 11:09:43Z

5

This error appeared when installing with Cocoapods the library CocoaImageHashing. The problem was that the search paths were wrong. So at the Target level, in Build Settings -> Search Paths -> Header Search Paths, the paths were corresponding to non existing folders, for example "${PODS_ROOT}/Headers/Public/CocoaImageHashing", when the folder structure Headers/Public/ did not exist. I added the path ${PODS_ROOT}/CocoaImageHashing and the error disappeared.

answered Feb 23, 2017 at 11:09

Nicoara Talpes

7202 gold badges13 silver badges29 bronze badges

Comments

rgkobashi · Accepted Answer · 2019-02-08 06:43:41Z

5

This happened to me after adding/renaming current configurations and it makes sense.

Every configuration makes use of Configurations Set generated by cocoapods so these things needs to match.

So if you add/rename configurations, these will need to use the right configuration sets, and for that running pod install will do it.

answered Feb 8, 2019 at 6:43

rgkobashi

2,70822 silver badges27 bronze badges

Comments

Yas Tabasam · Accepted Answer · 2015-04-28 16:20:21Z

4

Well its little strange but I guess you have to add a resource to your "Copy Bundle Resources" phase of your test target to make it load all headers from your main app target. In my case, I added main.storyboard and it took care of the error.

enter image description here

answered Apr 28, 2015 at 16:20

Yas Tabasam

10.6k9 gold badges50 silver badges53 bronze badges

Comments

Iulian Onofrei · Accepted Answer · 2017-02-10 16:09:04Z

4

This somehow did the trick for me:

Clean project
Clean build folder
Restart Xcode

edited Feb 10, 2017 at 16:09

Iulian Onofrei

9,85611 gold badges73 silver badges118 bronze badges

answered Aug 4, 2016 at 15:11

Hlung

14.4k6 gold badges77 silver badges93 bronze badges

3 Comments

Nico Over a year ago

Do come with generic answers not hit & try trics.

Hlung Over a year ago

This particular hit & try trick requires very less effort so it shouldn't hurt to try while you think of other solutions. ;)

Robert Schmid Over a year ago

Sadly, this particular hit & try trick is too often the correct answer.

BennyTheNerd · Accepted Answer · 2017-05-29 16:29:22Z

4

(Updated as of May 27, 2017)

Xcode 8. Swift Project - importing Objective C.

Things to know:

Bridging header file MUST be saved within the project's folder. (i.e. not saved at the same level that .xcodeproj is saved, but instead one level further down into the folders where all your swift and objective c files are saved). It can still find the file at the top level, but it will not correctly link and be able to import Objective C files into the bridging header file
Bridging header file can be named anything, as long as it's a .h header file
Be sure the path in Build Settings > Swift Compiler - General > Objective C Bridging Header is correctly pointing to you bridging header file that you made
IMPORTANT: if you're still getting "not found", try to first empty your bridging header file and erase any imports you currently have written there. Be sure that the bridging header file can be found first, then start to add objective c imports to that file. For some reason, it will kick back the same "not found" error even if it is found but it doesn't like the import your trying for some reason
You should not #import "MyBridgingHeaderFile.h" in any of your objective C files. This will also cause a "file not found" error

edited May 29, 2017 at 16:29

answered May 29, 2017 at 16:19

BennyTheNerd

4,0101 gold badge27 silver badges16 bronze badges

2 Comments

Amjad Husseini Over a year ago

All these points are checked and still have the same issue :( Any further points should be taken into consideration?

Mohammad Allam Over a year ago

@AmjadHusseini try to clean your project files then clear the derived data of your project then restart xCode. that worked with me

DaSilva · Accepted Answer · 2016-07-13 22:44:22Z

3

If helps anyone.

In my case my obj-c files were added has a reference folder (the blue folders in xcode) and the header couldn't find them. Just added the files, not the folder, from the finder to xcode and solved.

answered Jul 13, 2016 at 22:44

DaSilva

1,3581 gold badge19 silver badges42 bronze badges

Comments

fisher · Accepted Answer · 2014-12-30 16:14:25Z

2

I had the same problem. For me the reason was that I was using the same bridging-header for both my App and my Today Extension. My Today Extension does not include Parse, but because it was defined in the bridging-header it was trying to look for it. I created a new bridging-header for my Today Extension and the error dissapeared.

answered Dec 30, 2014 at 16:14

fisher

1,32616 silver badges30 bronze badges

1 Comment

Dia Kharrat Over a year ago

Doesn't sound like the same issue I have. I don't have a Today extension. In my case, I'm using a bridging header for the app, and the Parse framework is included in the app dependencies. The error also occurs for other frameworks, not just Parse.

James · Accepted Answer · 2016-02-19 15:34:10Z

2

My framework was working before and suddenly stopped working, and none of these answers were working for me. I removed the framework in Build Phases > Link Binary With Libraries, and re-added it. Started working again.

answered Feb 19, 2016 at 15:34

James

1,1083 gold badges11 silver badges29 bronze badges

Comments

Binh Le · Accepted Answer · 2016-05-16 10:31:49Z

2

I had an issue and fixed it after spending 2 hours to find. My environment as below:

cocoapod 0.39.0

swift 2.x

XCode 7.3.1

Steps:

project path: project_name/project_name/your_bridging_header.h
In Swift section at Build Setting, Objective-C Bridging Header should be: project_name/your_bridging_header.h
In your_bridging_header.h, change all declarations from .h to #import
In class which is being used your_3rd_party. Declare import your_3rd_party

answered May 16, 2016 at 10:31

Binh Le

3632 silver badges10 bronze badges

2 Comments

NaXir Over a year ago

Your answer is correct just add @jamesthakid answer in third point to make it more clear. Worked for me thanks.

Chris Gunawardena Over a year ago

What exactly do you mean by "change all declarations from .h to #import" ?

Peterses · Accepted Answer · 2021-07-27 07:06:50Z

2

If you are using Cocoapods, try:

Quit Xcode
pod deintegrate
pod install

For me, this solved the weird issue.

answered Jul 27, 2021 at 7:06

Peterses

9377 silver badges15 bronze badges

Comments

iMaddin · Accepted Answer · 2016-09-16 19:35:50Z

1

I had just duplicated an existing scheme and added another configuration to the project. I had to add a configuration with the same name to the framework's project in order for it to also build in the same DerivedData/($AppName)/Build/Products/($CONFIGURATION_NAME) folder. Otherwise the .framework file doesn't get created and therefore can't be imported.

answered Sep 16, 2016 at 19:35

iMaddin

9921 gold badge14 silver badges23 bronze badges

Comments

Rikh · Accepted Answer · 2017-01-18 08:18:11Z

1

I ran into the same issue today when trying to use a pod written in Objective-C in my Swift project, none of the above solutions seemed to work.

In the podfile I had use_frameworks! written. Commenting this line and then running pod installagain solved this issue for me and the error went away.

answered Jan 18, 2017 at 8:18

Rikh

4,2223 gold badges17 silver badges40 bronze badges

Comments

Julian · Accepted Answer · 2018-03-22 14:28:44Z

1

I had a similar issue with pods. Basically trying to run my UI tests, Xcode complained about missing pods. Solution to this was much simpler than any described above:

go to project file (main not a target)
click on the "Info" tab (most left)
set proper pod configuration for UI tests target ("Configurations" section right under "Deployment Target")

Working!

I found it in a thread: https://github.com/CocoaPods/CocoaPods/issues/2695

Sounds a bit like a bug for cocoa pods but I can see reasons why it might be tricky case.

answered Mar 22, 2018 at 14:28

Julian

9,3475 gold badges50 silver badges65 bronze badges

Comments

Madavaram Ramesh · Accepted Answer · 2019-02-05 14:12:54Z

1

Clean project,Clean build folder,Restart Xcode. i just remove path at project goto > Build Settings > Search the keyword. Swift Compiler - General -> Objective-C Bridging header worked for me.

answered Feb 5, 2019 at 14:12

Madavaram Ramesh

475 bronze badges

Comments

nja · Accepted Answer · 2018-02-09 13:15:42Z

0

I had similar problem and only one solution worked out for me. I tried everything suggested, and I knew that I set my bridging header fine, because I had some other lib working.

When I copied library (drag and drop) into the project, without Cocoapods, only after that I could import headers without errors.

I used facebook/Shimmer library.

answered Feb 9, 2018 at 13:15

nja

2985 silver badges13 bronze badges

Comments

Michal Shatz · Accepted Answer · 2018-06-14 11:22:17Z

0

In my case I just had to quit the simulator...

answered Jun 14, 2018 at 11:22

Michal Shatz

1,4162 gold badges20 silver badges31 bronze badges

Comments

ronatory · Accepted Answer · 2019-08-06 07:32:54Z

August 2019

In my case I wanted to use a Swift protocol in an Objective-C header file that comes from the same target and for this I needed to use a forward declaration of the Swift protocol to reference it in the Objective-C interface. The same should be valid for using a Swift class in an Objective-C header file. To use forward declaration see the following example from the docs at Include Swift Classes in Objective-C Headers Using Forward Declarations:

// MyObjcClass.h
@class MySwiftClass; // class forward declaration
@protocol MySwiftProtocol; // protocol forward declaration

@interface MyObjcClass : NSObject
- (MySwiftClass *)returnSwiftClassInstance;
- (id <MySwiftProtocol>)returnInstanceAdoptingSwiftProtocol;
// ...
@end

Genki · Accepted Answer · 2022-03-15 19:31:34Z

0

Adding this to "Other Swift Flags" worked for me:

-Xcc -fmodule-map-file=$(GENERATED_MODULEMAP_DIR)/<YourSwiftModuleImportedFromObjC>.modulemap

Reference: https://developer.apple.com/forums/thread/120152

answered Mar 15, 2022 at 19:31

Genki

3,2052 gold badges31 silver badges46 bronze badges

Comments

Vishal Desai · Accepted Answer · 2022-07-23 08:10:31Z

0

By setting User Header Search Paths to your bridge file with recursive worked for me.

answered Jul 23, 2022 at 8:10

Vishal Desai

175 bronze badges

Comments

rami · Accepted Answer · 2023-01-15 11:55:24Z

0

For me, it happened after renaming the project. All I had to do is renaming the path from:

Build Settings > Framework Search Paths

to match the new project name.

answered Jan 15, 2023 at 11:55

rami

1792 silver badges11 bronze badges

Collectives™ on Stack Overflow

Getting "file not found" in Bridging Header when importing Objective-C frameworks into Swift project

25 Answers 25

9 Comments

3 Comments

3 Comments

4 Comments

1 Comment

Comments

Comments

Comments

3 Comments

2 Comments

Comments

1 Comment

Comments

2 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

25 Answers 25

9 Comments

3 Comments

3 Comments

4 Comments

1 Comment

Comments

Comments

Comments

3 Comments

2 Comments

Comments

1 Comment

Comments

2 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related