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  lt Parse Parse h gt             lt unknown gt  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

User · Answer

This somehow did the trick for me    Clean project Clean build folder Restart Xcode

User · Answer

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

User · Answer

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  amp  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

User · Answer

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

User · Answer

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

User · Answer

I had to add my lib directory in User Header Search Paths     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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

I have the same issue  I changed all my imports from   import  HMSegmentedControl h  to   import  lt HMSegmentedControl HMSegmentedControl h gt  for example

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

If using cocoapods  try reinstalling the pods by running the following command   pod install

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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

User · Answer

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  lt MySwiftProtocol gt  returnInstanceAdoptingSwiftProtocol          end

User · Answer

In my case I just had to quit the simulator

User · Answer

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

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

Examples related to swift

Examples related to xcode

Examples related to bridging-header