Building Adobe AIR Applications
Building Adobe AIR Applications
Building Adobe AIR Applications
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
BUILDING ADOBE <strong>AIR</strong> APPLICATIONS<br />
Signing <strong>AIR</strong> applications<br />
Signing workflow for updates<br />
1.0<br />
C1<br />
<strong>AIR</strong> version earlier than 1.5.3 <strong>AIR</strong> version 1.5.3 or later<br />
Clean install<br />
Orginal PUB ID No<br />
Has certificate<br />
matched?<br />
1.0<br />
C1<br />
expired?<br />
Remove<br />
Yes Yes<br />
Has certificate<br />
expired?<br />
No<br />
Yes<br />
C2<br />
Install<br />
Migrate an <strong>AIR</strong> application to use a new certificate<br />
To migrate an <strong>AIR</strong> application to a new certificate while updating the application:<br />
1 Create an update to your application<br />
2 Package and sign the update <strong>AIR</strong> file with the new certificate<br />
3 Sign the <strong>AIR</strong> file again with the original certificate using the -migrate command<br />
An <strong>AIR</strong> file signed with the -migrate command can also be used to install a new version of the application, in addition<br />
to being used to update any previous version signed with the old certificate.<br />
Note: When updating an application published for a version of <strong>AIR</strong> earlier than1.5.3, specify the original publisher ID in<br />
the application descriptor. Otherwise, users of your application must uninstall the earlier version before installing the<br />
update.<br />
Use the ADT -migrate command with following syntax:<br />
2.0<br />
Users must<br />
uninstall the<br />
older version to<br />
install the<br />
updated version.<br />
Publish update<br />
Create an updated version of your application.<br />
Sign the application with the new certificate C2.<br />
Apply migration signature to the application with<br />
the original certificate C1<br />
using the adt -migrate command.<br />
adt -migrate SIGNING_OPTIONS<br />
air_file_in<br />
air_file_out<br />
SIGNING_OPTIONS The signing options identify the private key and certificate with which to sign the <strong>AIR</strong> file.<br />
These options must identify the original signing certificate and are described in “ADT code signing options” on<br />
page 170.<br />
air_file_in The <strong>AIR</strong> file for the update, signed with the new certificate.<br />
air_file_out The <strong>AIR</strong> file to create.<br />
Note: The filenames used for the input and output <strong>AIR</strong> files must be different.<br />
No<br />
Expiration<br />
period<br />
< 180 days?<br />
Yes<br />
No<br />
Legends:<br />
1.0 Old application<br />
C1 Old certificate<br />
2.0 New application<br />
C2 New certificate<br />
The following example demonstrates calling ADT with the -migrate flag to apply a migration signature to an updated<br />
version of an <strong>AIR</strong> application:<br />
Last updated 7/8/2013<br />
190
Change language