Even still, you have to #import it and if Xcode complains that it isn’t available you either don’t have Defines Module set to YES, or you named the header incorrectly (it is productModuleName-Swift.h, where productModuleName is your product module name), or (and here’s the irritating part) you added a Swift file to your project prior to setting Defines Module to YES.

That is, the compiler creates it as a temporary file prior to compiling your Objective-C.

What others have pointed out in the Stackoverflow post referenced early is that unlike the the Objective-C bridging header the Swift bridging header is not a file you can see in your project, but is automatically generated in the build chain.

The declaration on a Swift class isn’t good enough – inherit from NSObject The Header File.

You have to #import in every Objective-C class you plan to use your Swift classes in.

For a complete overview see Apple’s documentation, but here’s what I’ve found to be true: There are rules around what’s required to get Swift objects living in harmony in your Objective-C code. If Xcode asks whether or not you want to create a bridging header, you can if you like, but it’s not strictly required for what we’re trying to accomplish (Swift in Objective-C not the other way around, which is what the bridging header is for). In our case it is testing.Ĭreate your Swift file with Xcode File – New – File. To find it go to your target’s (not the project) build settings and again search for Packaging. Go to your project build settings page and type Packaging in the search field and then set Defines Module to YES.ĭid you even know you had a product module name? I didn’t. Your project’s (not the target) build settings need to have the flag Defines Module set to YES. If you have already added Swift files and are scratching your head why things won’t work (namely that your -Swift.h can’t be found), delete them from your project and just start over and follow these steps: Update Your Project Build Settings Let’s start off the basic rule: Don’t add any Swift files to your project without reading this first. I’d love to say it was easy and painless, but the reality is it was a pain in the ass (read this Stackoverflow thread to see why!).

Since there’s plenty of Objective-C bridging header tutorials out there already, I thought I’d share my experience with the reverse direction: adding Swift code to an existing Objective-C project. Swift is new and shiny and we want to start off playing with Swift first and then mix in some Objective-C when we have to (which if you are using popular frameworks such as AFNetworking, Parse, etc., you have to quickly). It’s clear from the Swift tutorials out there (including ours), that folks ask the question “How do I include Objective-C frameworks in my Swift project?” more often than “How do I include Swift code in my Objective-C project?” That’s understandable.

Use swift code in objective c