Reputation: 2024
I imported an Obj-C file into my swift project and Xcode automatically prompted me to create a bridging header file as expected. However, I deleted both the files (moved to trash) to make some changes, but when i try to import the Obj-C file once again, the prompt doesn't come up anymore. What is the reason? I even tested this same scenario in another project, It seems once I delete Xcode's auto created bridging header, It won't bring the prompt up again another time. Why is this?
Upvotes: 88
Views: 170540
Reputation: 1431
Bridge file only prompt once in a project.
If you delete the file by accident, you have to build a new bridge file. It's the same.
Go to File->New File->Header File, and the name should be YourProjectName-Bridging-Header, or else It can't be recognised.
If you are working with react native finally you need to add these lines:
//
// Use this file to import your target's public headers that you would like to expose to Swift.
//
#import <React/RCTBridgeModule.h>
#import <React/RCTViewManager.h>
#import <React/RCTLog.h>
#import <Foundation/Foundation.h>
#import <React/RCTEventEmitter.h>
#import <React/RCTConvert.h>
@interface RCT_EXTERN_MODULE(core, NSObject)
@end
Upvotes: 0
Reputation: 1051
After dealing with this issue around one hour. I found the real issue was folder!
Never Create/Copy folder.
To solve the issue-
First Create a group of any name you like. Then copy Objective-C files into the group (not folder).
Then definitely you will be prompt for Bridging Header File Creation.
Upvotes: 1
Reputation: 6900
If you want to configure it manually simply go to Build Settings and change the selection to ALL from Basic (Default) or customized.
Because empty fields are hidden to make things easier for the average end user, if you miss the prompt to add the bridging-header you may have difficulty finding it manually. Also the search option will not include hidden fields.
Change to All and the Swift Compiler - General section should appear with a child setting of "Objective-C Bridging Header"
Upvotes: 0
Reputation: 1
Upvotes: -4
Reputation: 31311
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 basic), search for Bridging Header. You can see the Xcode generated path entry. Select it and click on delete button.
Also, make sure to delete the Xcode auto generated bridging header file (ProjectName-Bridging-Header.h)
from your Xcode project directory.
Now, try to import the Obj-C file once again. You can see the prompt to create a bridging header file as expected.
Upvotes: 192
Reputation: 586
File -> New File -> Header File
Save it as a YourApp-Bridging-Header
Than go to Build Settings, find "Objective-C Bridging Header" (as previously guys told) and pass way to your Bridging Header as: YourApp/YourApp-Bridging-Header.h Where 'YourApp/' is a name of app. It could contain white space, for example 'Your App/'.
In my case in xCode 7.3.1 it works
Upvotes: 53
Reputation: 427
There are different way of creating Bridging Header in xcode as mention/suggested above. Here I would give you the best and easiest way of creating Bridge.
if you want to keep your header inside one group then use New Group and drag&drop your file in that group.
Never create any folder, or else you will get error due to that.
Upvotes: 11
Reputation: 1611
Bridge file only prompt once in a project.
If you delete the file by accident, you have to build a new bridge file. It's the same.
Go to File->New File->Header File
, and the name should be YourProjectName-Bridging-Header
, or else It can't be recognised.
Upvotes: 6
Reputation: 11597
have a look under your project settings -> build settings, scroll down to the User-Defined
section, see if it has a key called SWIFT_OBJC_BRIDGING_HEADER
and if it has a value. if its there it probably thinks you have one already, in that case just recreate the file with the same name.
Upvotes: 6