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 … Read more
Here the solution for the issue. Create a new header file and name it like “your project name-Bridging-Header.h“. The file must be saved to your project folder Select your xcode project -> select your build target -> select build settings -> click the “all” option at the top -> search for Swift Compiler – General … Read more
YES. You can mix Swift, C, C++, Objective-C & Objective-C++ files in the same Xcode project. C // Declaration: C.h #ifndef C_h #define C_h #ifdef __cplusplus extern “C” { #endif void hello_c(const char * name); #ifdef __cplusplus } #endif #endif /* C_h */ // Definition: C.c #include “C.h” #include <stdio.h> void hello_c(const char * name) … Read more
The reason of your issue is, the Xcode build settings still holds the path to auto generated Bridging Header file. You cannot get any build errors because of the header file (ProjectName-Bridging-Header.h) still exist in your project directory. How to resolve: Click on your project target, Go to Build Settings tab (choose all instead of … Read more
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).
Be careful to add the file to the folder that your error is complaining! I’ve made the same mistake, if you create the file from Xcode, it will go to the folder: Project->Project->Header.h And Xcode is looking for Project->Header.h That means you need to put the file inside your project folder (ProjectName->ProjectNameFolder)! Hope that helps … Read more