Select Desktop Application as the application type. Select the server technology if any that you want to use with your AIR application. Select the folder in which you want to place your application. The default is the bin folder. Click Next. Flex Builder provides full debugging support for AIR applications. The Flex Builder debugger catches any breakpoints or runtime errors and you can debug the application like any other Flex application.
You can also debug an application from the command line, using the AIR Debug Launcher command-line tool. When your application is complete and ready to be distributed or tested running from the desktop , you package it into an AIR file. Packaging consists of the following steps:. Optionally allowing users to view the source code and then selecting which of your application files to include.
Digitally signing your AIR application using a commercial code signing certificate or by creating and applying a self-signed signature. Open the project and ensure that the application has no compilation errors and runs as expected. If you have multiple projects and applications open in Flex Builder, select the specific AIR project you want to package. Optionally select Enable View Source if you want users to be able to see the source code when they run the application.
You can select individual files to exclude by selecting Choose Source Files. By default all the source files are selected. You can also optionally change the name of the AIR file that is generated. You have several options. You can sign the application using a commercial code signing certificate, you can create and use a self-signed digital certificate, or you can choose to package the application now and sign it later.
Digital certificates issued by certification authorities such as VeriSign, Thawte, GlobalSign, and ChosenSecurity assure your users of your identity as a publisher and verify that the installation file has not been altered since you signed it. Self-signed digital certificates serve the same purpose but they do not provide validation by a third party. You also have the option of packaging your AIR application without a digital signature by creating an intermediate AIR file.
An intermediate AIR file is not valid in that it cannot be installed. AIR provides this capability because in some development environments a particular developer or team handles signing. This practice insures an additional level of security in managing digital certificates. You must list the IDs of any test devices on which you plan to install the application when creating the provisioning profile.
Convert the development certificate and private key to a P12 keystore file. Create the application descriptor using the 2. Use iTunes to place your provisioning profile on your test device. Install and test the application on your iOS device.
Once your AIR app is finished, you can repackage it using a distribution certificate and provisioning profile. It is then ready to submit to the Apple App Store. Adobe AIR. View Help PDF 5. Workflow for creating AIR applications for mobile devices. Compile the application. Package the application as an Android package.
0コメント