I\'m integrating Swift code into a large Objective-C project, but I\'m running into problems when my Swift code refers to Objective-C classes. For example, suppose I have:>
This is a little silly, but it sounds like your "workaround" is what Apple intended, at least for now. From the interoperability guide:
If you use your own Objective-C types in your Swift code, make sure to import the Objective-C headers for those types prior to importing the Swift generated header into the Objective-C
.mfile you want to access the Swift code from.
In this devforums thread, someone mentioned they already filed a bug in Radar. You probably should too.