Package AIR Application Dialog
Use this dialog to specify packaging options and to package your AIR applications (Desktop and Mobile) according to the specified options.
The upper part of the dialog
Use the available checkboxes to select the build configurations for which you want to create the application packages.
Included in the list are the Desktop and Mobile-targeted build configurations whose output type is Application.
The build configurations are grouped by Flash modules.
Select the packaging options for Desktop and Mobile (Android and iOS) applications, and click Package.
Note that the availabilities of the options depend on the selected build configurations and their settings (e.g. on whether packaging for Android and iOS is enabled in the selected Mobile-targeted build configurations).
|Desktop application package||Select one of the following: |
- installer (*.air). Select this option to create a digitally-signed installer file or a number of such files (one for each of the selected Desktop-targeted build configurations).
- native installer. Select this option to create a native application installer or a number of native installers for the operating system that you are using.
- captive runtime bundle. Select this option to create a captive runtime bundle or a number of bundles for the operating system that you are using.
- unsigned package (*.airi). Select this option to create an unsigned AIR intermediate file or a number of such files.
|Android package type (*.apk)|| Select one of the following target types for the Android package or packages: |
- release. For the AIR runtime to be packaged, select the Captive runtime option. See the discussion of the captive runtime option.
- debug over USB port. If necessary, change the port suggested by IntelliJ IDEA.
- debug over network.
|iOS package type (*.ipa)|| Select one of the following target types for the iOS package or packages: |
- test without debugging. If necessary, select the Fast packaging option.
If this option is selected, the ActionScript bytecode is interpreted and not translated to machine code. As a result, packaging is performed faster but code execution is slower.
In technical terms, the
ipa-test-interpreter target is used instead of
See the discussion of the corresponding targets in Adobe AIR documentation.
- debug over network. If necessary, select the Fast packaging option. (The
ipa-debug-interpreter target will be used instead of
- ad hoc distribution.
- Apple App Store distribution.
|Package||Click this button to package your applications.|
Last modified: 11 October 2017
Language and Framework-Specific Guidelines: