My solution is : Do not import the ObjC framework in bridging header file, just import the framework in the files in which the framework is needed. just like: import xxxframework
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).
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
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