CODEWITHSUNDEEP
swiftxcodebridging-header
Dia Kharrat
Dia Kharrat

Reputation: 6016

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

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:

  1. The "Install Objective-C Compatibility Header" is set to "YES".
  2. 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.

Upvotes: 110

Views: 130756

Answers (25)

rami
rami

Reputation: 180

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.

enter image description here

Upvotes: 0

Vishal Desai
Vishal Desai

Reputation: 17

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

Upvotes: 0

Genki
Genki

Reputation: 3195

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

Upvotes: 0

Peterses
Peterses

Reputation: 937

If you are using Cocoapods, try:

  1. Quit Xcode
  2. pod deintegrate
  3. pod install

For me, this solved the weird issue.

Upvotes: 2

ronatory
ronatory

Reputation: 7324

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

Upvotes: 0

rgkobashi
rgkobashi

Reputation: 2698

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.

Upvotes: 5

Madavaram Ramesh
Madavaram Ramesh

Reputation: 47

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.

Upvotes: 1

Michal Shatz
Michal Shatz

Reputation: 1416

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

Upvotes: 0

Julian
Julian

Reputation: 9337

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:

  1. go to project file (main not a target)
  2. click on the "Info" tab (most left)
  3. 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.

Upvotes: 1

nja
nja

Reputation: 288

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.

Upvotes: 0

BennyTheNerd
BennyTheNerd

Reputation: 4010

(Updated as of May 27, 2017)

Xcode 8. Swift Project - importing Objective C.

Things to know:

  1. 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
  2. Bridging header file can be named anything, as long as it's a .h header file
  3. 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
  4. 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
  5. You should not #import "MyBridgingHeaderFile.h" in any of your objective C files. This will also cause a "file not found" error

Upvotes: 4

Nicoara Talpes
Nicoara Talpes

Reputation: 720

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.

Upvotes: 5

Hlung
Hlung

Reputation: 14338

This somehow did the trick for me:

  • Clean project
  • Clean build folder
  • Restart Xcode

Upvotes: 4

Rikh
Rikh

Reputation: 4232

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.

Upvotes: 1

iMaddin
iMaddin

Reputation: 992

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.

Upvotes: 1

DaSilva
DaSilva

Reputation: 1358

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.

Upvotes: 3

Binh Le
Binh Le

Reputation: 363

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:

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

Upvotes: 2

James
James

Reputation: 1108

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.

Upvotes: 2

jamesthakid
jamesthakid

Reputation: 1265

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

Upvotes: 62

Ankit Goel
Ankit Goel

Reputation: 6505

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

pod install

Upvotes: 5

Yas Tabasam
Yas Tabasam

Reputation: 10625

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

Upvotes: 4

Rainer Schwarze
Rainer Schwarze

Reputation: 4755

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)

Upvotes: 30

Dan Jackson
Dan Jackson

Reputation: 451

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.

Upvotes: 17

Dia Kharrat
Dia Kharrat

Reputation: 6016

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).

Upvotes: 91

fisher
fisher

Reputation: 1296

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.

Upvotes: 2

Related Questions