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
Using RK in Extensions #124
Comments
Let me research that, I didn't try it before. |
Looks like from quick tests its just a case of
Assuming the frameworks don't use anything not allowed in extensions? |
I think ReactiveKit is good to go. I can't think of any instance where Bond uses extension unsafe APIs, but I need to double check. |
It seems its ok once the target is set (Both RK and Bond) |
Great to hear that! :) |
Did this get merged though? Still seeing the issue from Bond & ReactiveKit |
Isn't this the setting that you set on app extension target?
|
I could definitely be mistaken, but AFAIK it asserts that this dependancy doesn't use extension-unsafe API calls. By default this is set to YES on a new app extension target, and linking this with ReactiveKit/Bond triggers a warning - I think ReactiveKit/Bond need to set that flag too. For reference I searched around and a bunch of other libs have merged the same issue: bignerdranch/CoreDataStack#115 |
I'd like to use RK in the iMessage app (extension) I'm building but I get the following:-
linking against a dylib which is not safe for use in application extensions: ....
for both RK and Bond.
Any ideas?
The text was updated successfully, but these errors were encountered: