Let’s start off the basic rule: Don’t add any Swift files to your project without reading this first. If you have already added Swift files and are scratching your head why things won’t work (namely that your Your project’s<\/i> (not the target) build settings need to have the flag Defines Module<\/b> set to YES. Go to your project build settings page and type Packaging<\/b> in the search field and then set Defines Module<\/b> to YES.<\/p>\n Did you even know you had a product module name? I didn’t. To find it go to your target’s<\/i> (not the project) build settings and again search for Packaging. Make note of the Product Module Name<\/b>. In our case it is Create your Swift file with Xcode File – New – File<\/b>. 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).<\/p>\n There are rules around what’s required to get Swift objects living in harmony in your Objective-C code. For a complete overview see Apple’s documentation<\/a>, but here’s what I’ve found to be true:<\/p>\n What others have pointed out in the Stackoverflow post referenced early is that unlike<\/b> the the Objective-C bridging header the Swift bridging header<\/i> is not a file you can see in your project, but is automatically generated in the build chain. That is, the compiler creates it as a temporary file prior to compiling your Objective-C. Even still, you have to Trying to use only Unfortunately we cannot compile due to the annoying Changing our class to:<\/p>\n and the compilation proceeds and we can access our Swift class.<\/p>\n From there things proceeded relatively well. Our final test included the following Swift code:<\/p>\n with our delegate header including<\/p>\n and using it in our Objective-C application delegate:<\/p>\n As expected, our output:<\/p>\n If you can't get Swift classes mixed into your Objective-C code on your first attempt, you're aren't an idiot. Future versions of Xcode one would hope will fix the annoying feature of failing to generate a 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. Swift is new and shiny and we want to start off playing with Swift first […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11,5,2],"tags":[],"class_list":["post-980","post","type-post","status-publish","format-standard","hentry","category-apple","category-swift","category-xcodetips"],"_links":{"self":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts\/980"}],"collection":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/comments?post=980"}],"version-history":[{"count":13,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts\/980\/revisions"}],"predecessor-version":[{"id":1124,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts\/980\/revisions\/1124"}],"wp:attachment":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/media?parent=980"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/categories?post=980"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/tags?post=980"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}-Swift.h<\/code> can’t be found), delete them from your project and just start over and follow these steps:<\/p>\nUpdate Your Project Build Settings<\/h2>\n
![\"Screenshot](\"https:\/\/dev.iachieved.it\/iachievedit\/wp-content\/uploads\/2014\/11\/Screenshot-2014-11-26-16.04.46.png\")
<\/a><\/p>\nMake Note of Your Product Module Name<\/h2>\n
testing<\/code>.<\/p>\n![\"Screenshot](\"https:\/\/dev.iachieved.it\/iachievedit\/wp-content\/uploads\/2014\/11\/Screenshot-2014-11-26-16.10.33.png\")
<\/a><\/p>\nCreate Your Swift File<\/h2>\n
The Rules<\/h2>\n
\n
#import <productModuleName-Swift.h><\/code> in every Objective-C class you plan to use your Swift classes in\n@objc<\/code> declaration on a Swift class isn’t good enough – inherit from NSObject<\/code>\n<\/ul>\nThe Header File<\/h3>\n
#import<\/code> it and if Xcode complains that it isn’t available you either don’t have Defines Module<\/b> set to YES, or you named the header incorrectly (it is productModuleName-Swift.h<\/code>, where productModuleName<\/code> is your<\/i> product module name), or<\/b> (and here’s the irritating part) you added a Swift file to your project prior<\/i> to setting Defines Module<\/b> to YES.<\/p>\nThe Swift Class Definition<\/h3>\n
@objc<\/code> as an indicator that you’re going to use the Swift class in Objective-C code results in ARC complaints about alloc<\/code> not being defined. Here’s a screenshot of declaring our Swift class like this:<\/p>\n\nimport Foundation\n\n@objc class SwiftClass {\n \n init() {\n println(\"SwiftClass init\")\n }\n\n}<\/pre>\nNo known class method for selector 'alloc'<\/code> error:<\/p>\n![\"Screenshot](\"https:\/\/dev.iachieved.it\/iachievedit\/wp-content\/uploads\/2014\/11\/Screenshot-2014-11-26-16.26.26.png\")
<\/a><\/p>\n\nimport Foundation\n\nclass SwiftClass : NSObject {\n \n override init() {\n super.init()\n println(\"SwiftClass init\")\n }\n\n}\n<\/pre>\n\nimport Foundation\n\nclass SwiftClass : NSObject {\n \n override init() {\n super.init()\n println(\"SwiftClass init\")\n }\n \n func sayHello() -> Void {\n println(\"hello\");\n }\n \n func addX(x:Int, andY y:Int) -> Int {\n return x+y\n }\n \n \/\/ Make a dictionary\n \/\/ No, this code doesn't protect against values.count > keys.count\n func dictionaryWithKeys(keys:[String], andValues values:[String]) -> Dictionary\n#import
\n- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {\n \n SwiftClass* mySwiftClass = [[SwiftClass alloc]init];\n \n [mySwiftClass sayHello];\n \n int result = [mySwiftClass addX:5 andY:5];\n \n NSLog(@\"5 + 5 is %d\", result);\n \n NSDictionary* dictionary = [mySwiftClass dictionaryWithKeys:@[@\"key1\",@\"key2\",@\"key3\"] andValues:@[@\"val1\",@\"val2\",@\"val3\"]];\n \n NSLog(@\"dictionary = %@\", dictionary);\n \n return YES;\n}\n<\/pre>\n\nSwiftClass init\nhello\n2014-11-26 16:43:28.900 testing[6536:1258140] 5 + 5 is 10\n2014-11-26 16:43:28.928 testing[6536:1258140] dictionary = {\n key1 = val1;\n key2 = val2;\n key3 = val3;\n}\n<\/pre>\nConclusion<\/h2>\n
-Swift.h<\/code> header file if you didn't do things in exactly the right order. In the meantime, follow these steps and definitely pore back over the Stackoverflow<\/a> thread in case you missed something.<\/p>\n","protected":false},"excerpt":{"rendered":"