-
-
Notifications
You must be signed in to change notification settings - Fork 197
Provide Extensibility to Include iOS Native Extensions in NativeScript Apps #4393
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
Comments
Hello, I also run into this issue then by following the post nativescript-ios-imessages, I'm able to add the share extension into iOS project by adding the application source code and write the extension's view controller in Nativescript However, I would like to reuse a module / function from the main application target to do the sharing task without recoding the function (or create a native code extension) because I have already coded all the logic code in js with some Nativescript plugins. Hence, I would like to suggest that NativeScript-Cli could also support the share extension written in As I see, @KristianDD is currently implementing the iOS extension support for |
Hi @tdhman , The other issue is that extensions have strict limitations to which APIs they can access. Same restrictions apply to frameworks embedded inside the extension target. Reference here. Will update you once we have more information on the status of this feature. |
Logged a separate issue for research of embedding NativeScript framework in iOS App Extensions. Closing this issue as the feature it describes is already finished and released. |
Is your feature request related to a problem? Please describe.
As a user, I would like to add App Extensions to my NativeScript application for iOS. For example, I would like to use Share extension, Today widget, etc.
More information for the extensions can be found here: https://developer.apple.com/app-extensions/
Describe the solution you'd like
Allow using native iOS Extensions in NativeScript app, i.e. place their source code (Objective-C) under source control, for example in
App_Resources
directory.parent to #4391
parent to #3965
The text was updated successfully, but these errors were encountered: