@swift-ci smoke test

@swift-ci smoke test

@swift-ci smoke test

@aciidb0mb3r: Is this released in Xcode 11.2? Because I'm still seeing the issue. I have a sample if it helps?

No, this change is not present in Xcode 11.2

Is this going to be released with Xcode 11.3 or we have to wait for Swift 5.2?

How about Xcode 11.3?

Maybe with 11.4?

Is there an update on when this is released / available in Xcode?

This is only done for macOS.

@aciidb0mb3r Any reason not to do this for iOS, as well?

I wish this could be supported in iOS as well. Currently, I am facing cases like delivering Swift packages to ObjC based App target. Without able to directly import the autogenerated swift header in ObjC, it will be very painful to add a Swift adaptor layer in the app.

This is working in iOS project on Xcode 11.4.1 for me.

I've tested it on an old Objective-C project and successfully can use Swift Package manager with it. Here is what I did:

1. Swift Packages - add package dependency, as normal to include my package
2. In an Objective-C .m file, include the module like so:
   @import YourSwiftPackageName;
3. Ensure in your swift package that you have used @objc to expose Swift to your Objective-C
4. Ensure you have used public to expose your Swift in your package to your main project, as it's in another module.
5. Ensure your Swift Package is listed in your targets 'Frameworks, Libraries and Embedded Content'. I note this because I have 2 targets - and it only added them to one of my targets, not both, so I kept getting Module not found errors.

I'm able to add a SwiftPackage into MainTarget Objective-C.m file
But no chance when trying to add it to my Objective-C.h file.
Any idea to solve this ?

I'm unable to use @objc protocols (declared in Swift files in a Swift Package) in Obj. C files in an Xcode project framework that explicitly links to that package.