[Tracking] iOS App Extensions

Beginne mit dem Lesen der Abschnitte „Overview“ und „Known issues“ dieses Tracking-Issues. Es nennt keine Implementierungsdateien, Tests oder einzelne abgegrenzte Änderung; nutze das aufgeführte Verhalten der Extension und die ungelösten Einschränkungen bei Signierung, Framework und mehreren Extensions, um ein konkretes Folge-Issue zu definieren. Erledigt wäre dies erst mit einer separat abgegrenzten Verbesserung und einer expliziten Validierung.

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 Automatic code signing. Any provision configuration inside App_Resources/iOS/build.xcconfig will 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!