I have tried all of the above steps mentioned in the answers but nothing worked for me, the problem was basically with the deployment target version for the project and in the podfile. In my project deployment target was 10.0 while in my podfile it was 11.0.
Optional values of non-Objective-C types aren’t bridged into Objective-C. That is, the first three properties of TestClass below would be available in Objective-C, but the fourth wouldn’t: class TestClass: NSObject { var nsNumberVar: NSNumber = 0 // obj-c type, ok var nsNumberOpt: NSNumber? // optional obj-c type, ok var doubleVar: Double = 0 // bridged … Read more
The module name comes from the Product Module Name build setting: The SWIFT_MODULE_NAME setting is apparently hidden, but you can see its derivation by looking at Xcode.app/Contents/PlugIns/Xcode3Core.ideplugin/Contents/SharedSupport/Developer/Library/Xcode/Plug-ins/XCLanguageSupport.xcplugin/Contents/Resources/Swift.xcspec: … { Name = “SWIFT_MODULE_NAME”; Type = String; DefaultValue = “$(PRODUCT_MODULE_NAME)”; CommandLineArgs = ( “-module-name”, “$(value)”, ); }, …
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