-
Notifications
You must be signed in to change notification settings - Fork 576
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mark classes and methods unavailable for extensions #290
Mark classes and methods unavailable for extensions #290
Conversation
@@ -143,7 +143,7 @@ - (BFTask *)followRedirects:(NSURL *)url { | |||
}]; | |||
} | |||
|
|||
- (BFTask *)appLinkFromURLInBackground:(NSURL *)url { | |||
- (BFTask *)appLinkFromURLInBackground:(NSURL *)url NS_EXTENSION_UNAVAILABLE_IOS("") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had to add this here on top of adding it to the method definition in the BFAppLinkResolving
protocol otherwise it would still complain.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! This does help solve some compilation problems.
Hey Felix, looks like this is failing some Travis tests... |
@nlutsenko Ok just did 👍 |
* mark classes and methods unavailable for extensions * Add BFVoid macro. * Update BFTask.taskWithDelay to use BFVoid. * Update xctoolchain to latest. * Update projects to Xcode 8.2. * Use Xcode 8.2 for Travis-CI. * Remove automatic exception catching. (BoltsFramework#294)
This is mostly relevant to when using cocoapods, as of version
1.1.0
you can no longer have a Podfile with a different subspec for the app target and extensions, i.e:So the solution is to use
pod 'Bolts'
for both targets.In order to do that some methods/classes need to be marked as unavailable so the app is compilable.