Description
Overview
iOS App Extensions feature enables adding extension via NativeScript plugins or with adding extensions folder inside App_Resources/iOS/.
The extension should be created and developed inside Xcode. Once the user is happy with the result, the folder containing the extension should be copied inside App_Resources/iOS/extensions. The an extension.json should be added. This file describes the SDK frameworks used in the extension and the assetcatalogCompilerAppiconName. For example:
{
"frameworks": ["NotificationCenter.framework"],
"assetcatalogCompilerAppiconName": "AppIconExtension"
} In the example above you should have an .xcassets catalog with AppIconExtension.appiconset inside the extension folder.
Each folder inside App_Resources/iOS/extensions is considered a separate extension and the folder name is considered the extension name.
Known issues
- The extensions inside NativeScript application support only
Automaticcode signing. Any provision configuration insideApp_Resources/iOS/build.xcconfigwill be ignored. And the application build will most probably fail. - Currently including multiple extensions using the same SDK framework is not supported.
- Local frameworks (not SDK ones) will not be included in the build of the extension
Discussion
Please, don't report problems here. Instead, open a new issue and link it to this one.
Let's use this discussion for suggestions and improvement ideas. We would love to hear from you!