Re: App refuses to find Framework's Objective-C Generated Header: whats wrong?
Re: App refuses to find Framework's Objective-C Generated Header: whats wrong?
- Subject: Re: App refuses to find Framework's Objective-C Generated Header: whats wrong?
- From: David Hoerl <email@hidden>
- Date: Fri, 14 Oct 2016 13:08:32 -0400
Looking back at your original post, I see I thought your were getting an error from the @import, so you replaced that with an #import. You actually said you did both.
I probably could take the @import MyFramework out - I keep hoping Xcode
will wakeup and do the right thing...
In that case, the question is: are you declaring all of the classes and methods that are used across the framework boundary as “public” or “open”? Omitting the access specifiers would produce exactly the behavior you describe, since the default access is “internal”.
They are all public and @objc - without that they don't make it into the
bridging header.
A co-worker who is writing a Swift 3 only app was able to import the
framework into his app and access the classes without any trouble at all.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden