iOS: Support for Extensions #785
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
|
Nice! |
Shchvova
approved these changes
Mar 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding the ability for iOS Apps to support appx files in their apps. This could be used to support any of the following extensions via the plugin system:
Widgets, Intents, iMessage, etc
https://developer.apple.com/app-extensions/
Note that my main use for this at the moment is to support Rich Notification Extensions for an upcoming Personal Plugin for OneSignal for Corona Sim.
I will write some basic docs for this in Corona Native/ Corona Sim guides for how to support this.
I updated the signing script to sign the Appx/Extensions if there are any plugins; include them appropriately.
Thanks,
Scott