Release notes for Adobe AIR developers

Release date: 02/11/2010

Getting Started

Welcome to the release notes for AIR 1.5.3. This document contains system requirements, installation instructions, known issues, and other information about using the AIR 1.5.3 runtime. Please refer to the Adobe AIR 1.5.3 release notes for additional information. Please use the Adobe AIR feedback form to report feature requests, bugs or improvements to the release notes.

System requirements

For current Adobe AIR system requirements, please visit

Changes in AIR 1.5.3

Certificate Renewals

Prior to AIR 1.5.3, AIR secured application updates signed with renewed certificates by comparing the publisher ID computed from the old and new certificates. Due to flaws in the definition of publisher ID, many customers found that this mechanism was not compatible with their renewed certificates. This method is now discouraged in favor of using migration signatures.

If you have an existing AIR application, then you should take the following steps to make this transition:

  1. Determine your application's current publisher ID. In an installed application, this is found in the META-INF/AIR/publisherid file.
  2. Add a <publisherID></publisherID> element in your descriptor, and copy your publisher ID into it.
  3. Update your application's namespace to 1.5.3.

If you are creating a new AIR application you should not use the <publisherID> setting.

If you issue an update to your application using the same (i.e., not renewed) certificate as the previous version then no further actions are necessary. When you update an application with a renewed certificate, you must use the old certificate to apply a second, migration signature as follows:

  1. Sign your application first with your new certificate
  2. Apply a migration signature using your old certificate

Your old certificate can be used for up to six months after expiration date for purposes of applying a migration signature. See Changing Certificates in the Adobe AIR documentation for further details on migration signatures.

Finally, please note that:

  • This change in behavior takes effect for applications which use the 1.5.3 (or later namespace). AIR 1.5.3 will continue to apply the previous publisher ID computation to applications specifying older namespaces.
  • Updating the version in your namespace will cause new APIs and behaviors to become visible to your application. For example, if your application previously used the 1.1 namespace, then updating to 1.5.3 will cause all of the new, AIR 1.5 APIs and behaviors to become visible to your application. These changes rarely affect application compatibility, but we recommend validating application behavior with the modified namespace.

Version information

WebKit Version

AIR 1.5.3 includes WebKit version 34190.

Latest Flash Player plug-in

AIR 1.5.3 includes an updated version of the Flash Player plug-in (, which is used when displaying SWF content embedded in HTML. For more information, see

Fixed bugs

Bug # Bug title
2411661 When an intermediate certificate expires, it is no longer possible to sign an application with a renewed certificate (fixed by removing the publisher ID)
2464587 AIR application installer crashes on Linux systems using Phenom processors
2421099 When the Mac Snow Leopard option is enabled to minimize the windows "behind" the application icon in the dock, applications that are maximized do not un-minimize the window
2471920 HTMLLoader: KeyCodes are not transmitted well when using shift key inside an HTMLLoader
2474555 In Linux, AIR applications open links in Firefox even if default browser is set to a different application

Known issues

AIR applications crash on Mac when older resource files are present in Flex Builder 3

Currently there is an issue that may cause your AIR application to crash on the Mac if you do not remove three older resource files that are still included in Flex Builder. To remove these files:

  1. In the Mac Finder, locate your "Adobe Flex Builder 3" applications folder and navigate to "/sdks/3.2.0/runtimes/air/mac/Adobe AIR.framework/Versions/1.0/Resources".
  2. Remove the following files: MainMenu.nib, AuthDialog.nib, and FlashPromptDialog.nib.

Sidecar installation on Windows

When a bundled installation of the AIR runtime is performed from a removable drive or CD/DVD, you may run into an issue if the previous version of the AIR runtime is already installed and the bundled AIR runtime installer is not located at the root of the removable media. To avoid this issue, please make sure the sidecar installer file is deployed at the root of the removal media.

HTML transparent overlays

The current WebKit version does not correctly display transparent overlays that may be associated with Google Maps (GPolyline opacity fails). As a workaround, please change the userAgent property of the HTMLoader object to a value other than "AppleWebKit." By doing so, the client detection code from Google Maps switches to the last fallback for rendering overlays (server rendering).

Encrypted local store

For troubleshooting of encrypted local store issues on Linux, please read

Installing Adobe AIR

Please read AIR 1.5.1 release notes or

Note: Though 64-bit Linux is not supported officially, by installing 32-bit dependencies on it, it can be made to work. Please read here:

Install AIR applications

Please read AIR 1.5.1 release notes.


For overlaying AIR SDK for use with Flex SDK, please read the the following TechNote: How to Overlay the AIR SDK for Use With the Flex SDK.