Xcode 6 / Beta 4: using bridging headers with framework targets is unsupported
I just upgraded to Xcode 6 Beta 4 and have a framework that I created for Live Views in Beta 2. Due to another swift bug, I needed to use some Obj-C code. When upgrading though, I get the following error:
error: using bridging headers with framework targets is unsupported
I have not seen anything in the release notes, or found any other migration path. Has anyone else seen this and arrived at a solution?
I realize that Beta 3 eliminated the need for frameworks for live views, but it makes sense in my case if I can get it to work. I can remove it though as a fallback, but would prefer to use a framework if they are not totally broken in Beta 4.
Answer
As the error states, bridging headers are not allowed in Frameworks. The Importing Code from Within the Same Framework Target section of the Mix & Match apple documentation hints at this. As they say, you need to "In your umbrella header file, import every Objective-C header you want to expose to Swift".
However, I discovered that you may also need to make those specific headers public as well. This answer reviews why and how to do that: Swift compiler error: "non-modular header inside framework module".
So, do this:
- Remove your bridging header file.
- Remove references to the bridging header file in the build settings for the framework
- Add the necessary headers to your umbrella file ([ProductName].h)
- Make the included files public in the framework's "Headers" section of its "Build Phases".
- Clean and rebuild.
Note: The "umbrella header file" is a file (named [ProductName].h) that generally represents all public headers of a framework. It is usually just a list of #import statements to other headers contained in the framework. In Xcode, if you open UIKit.h, you will see a good example of an umbrella file.