If you need to import any other custom files, add your custom imports outside the section managed by Swiftify. This section collects imports from all Objective-C source files and the PCH (precompiled header) file and excludes any imports for files already converted to Swift (so, if you convert MyViewController class to Swift, the corresponding import will be automatically deleted from this section). Your bridging header will be called something like `ProjectName-Bridging-Header.h`, open it and you’ll find a section that is automatically inserted, and updated, by Swiftify: //. The Objective-C bridging header file is automatically added to your project, and updated while you gradually convert your project to Swift.

Press a toolbar button to generate bridging header files at a later time.

Open a project and confirm the prompt to generate bridging header files.

These bridging header file(s) are generated when you take any of these actions in the Advanced Project Converter: The Advanced Project Converter automatically generates Objective-C and Swift bridging header files so that you can use Objective-C code from Swift and vice versa. This way you avoid the need to import the Swift Bridging Header from every Objective-C file that depends on Swift code. The easiest way to expose your Swift code to Objective-C is by importing the Swift Bridging Header file ( ProjectName-Swift.h, which is automatically generated by Xcode) from the Precompiled Header file.

Read more on this topic in the Apple’s documentation: Importing Objective-C into Swift. The Objective-C declarations are automatically available from any Swift file within that target, without any import statements! Use classes and other declarations from your custom Objective-C code with the same Swift syntax you use for system classes. Xcode offers to create this header when you add a Swift file to an existing Objective-C app or an Objective-C file to an existing Swift app: Inside this file, you import all the Objective-C classes that you need to be exposed (note that these Objective-C classes must be public).

To access Objective-C code using Swift within the same target, you'll need an Objective-C bridging header file. It is recommended to read this article before, or during, migrating your Objective-C project to Swift and prior to reading this article. Expose Swift code to Objective-C, you'll need to import the Swift Bridging Header file, created by Xcode.Expose Objective-C code to Swift, you’ll need an Objective-C Bridging Header file.In a mixed-language project (a project which has both Objective-C and Swift), you’ll most likely want to expose the Objective-C code to Swift and vice versa.

Use swift code in objective c