You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the section "Using an Embedded Framework to Share Code".
To sum up, in order to compile the app extension without the warning "“linking against dylib not safe for use in application extensions”, which would make the app review fail, we need to be able to set the flag "APPLICATION_EXTENSION_API_ONLY" to YES. That is telling whoever is using the framework that the framework is using extension safe APIs.
So the change is just setting the flag to YES in the project settings, because the library is already not using any unsafe APIs. This makes the library available to use from a Today Widget for example which is quite great since it's such a simple change.
The text was updated successfully, but these errors were encountered:
We are using the library from an app extension, but there's a caveat with using a framework from an app extension, as explained in this Apple link:
https://developer.apple.com/library/ios/documentation/General/Conceptual/ExtensibilityPG/ExtensionScenarios.html
In the section "Using an Embedded Framework to Share Code".
To sum up, in order to compile the app extension without the warning "“linking against dylib not safe for use in application extensions”, which would make the app review fail, we need to be able to set the flag "APPLICATION_EXTENSION_API_ONLY" to YES. That is telling whoever is using the framework that the framework is using extension safe APIs.
So the change is just setting the flag to YES in the project settings, because the library is already not using any unsafe APIs. This makes the library available to use from a Today Widget for example which is quite great since it's such a simple change.
The text was updated successfully, but these errors were encountered: