Release notes for users of Adobe AIR 2.5

 Release notes for users of Adobe®  AIR® 2.5

 The Adobe AIR runtime powers many popular desktop applications, including video players, enterprise applications, games, and productivity tools. Prior to running these applications, the user must install Adobe AIR.

This document contains system requirements, installation instructions, known issues, and other information about using AIR 2.5.


System requirements

Supported languages

What's new in AIR 2.5

AIR Installers Troubleshooting

Tips and tricks

Known issues and limitations

AIR Knowledge Base


System requirements

 AIR runtime system requirements 







Minimum: Intel® Pentium® III 1GHz or faster processor Recommended: Pentium 4 2GHZ or faster 

Intel Core™ Duo 1.83GHz or faster processor. 

Minimum: Intel® Pentium® III 1GHz or faster processor Recommended: Pentium 4 2GHZ or faster  

ARMv7 processor with Vector FPU Minimum 550Mhz OpenGL ES2.0 H.264 & AAC H/W Decoders 

Operating System 

Microsoft® Windows® XP Home, Professional, or Tablet PC Edition with Service Pack 2 or 3 (including 64 bit editions), Windows Server® 2003, Windows Vista® Home Premium, Business, Ultimate, or Enterprise (including 64-bit editions) with Service Pack 1, or Windows 7  (including 64 bit editions)

Mac OS 10.4, 10.5 or Mac OS 10.6 (Snow Leopard) 

Fedora Core 12, Ubuntu 9.10, openSUSE 11.2

Android 2.2


Minimum: 512MB RAM; Recommended: 1GB RAM 

Minimum: 512MB RAM; Recommended: 1GB RAM 


256MB RAM 

Note: Windows 2000 and Mac PowerPC are not supported as of AIR 2. Users can install and run AIR 1.5 applications, but will not be able to install or update to AIR 2 or later releases. Mac OS 10.4 running on an Intel processor is supported for running AIR 2 applications, but is not supported as development environment with the AIR SDK, version 2 or later.


Additional requirements for Linux distributions

Supported desktop environments


Package management systems

RPM or Debian

Minimum GTK+ version


Window managers 

Metacity (default for GNOME) and KWin (default for KDE)


Support for transparency in AIR applications requires a compositing window manager and additional X server extensions. The following are supported: Compositing window managers: Beryl, Compiz, Compiz-fusion X server extensions: Composite, Render, Shape

Flash Player

Seamless (badge) installation from the web requires Flash Player or later


Supported languages

 Adobe AIR 2.5 installation and runtime user experience supports the following languages:

  • Chinese Simplified
  • Chinese Traditional
  • Czech
  • Dutch
  • English
  • French
  • German
  • Italian
  • Japanese
  • Korean
  • Polish
  • Brazilian Portuguese
  • Russian
  • Spanish
  • Swedish
  • Turkish

What's new in AIR 2.5

AIR 2.5 now supports applications for Android, in addition to Windows, Mac OS, Linux, and iOS. 


  • StageWebView that simulate what StageWebView will look like on a mobile
  • CSS Shadow support that allow you to create shadow effects to both text and HTML borders
  • CSS font-face support is enabled for OpenType and TrueType fonts
  • H.264 Video Hardware Decoding for Desktop


  • CameraUI  Still Picture and Video
  • Mapping Android specific tags from app-xml to Android Manifest
  • NetworkInfo  support
  • Read from Camera Roll
  • Custom URI
  • Camera Video Capture
  • Microphone
  • StageWebView 
  • Android Permissions tag in application descriptor
  • cacheAsBitmapMatrix
  • Hardware accelerated rendering
  • Application versioning changes
  • Debugging an AIR application on Android
  • Keyboard events for Menu, Back and Search keys
  • 36x36 size icon
  • Certificate Validity
  • GPS
  • Accelerometer
  • Multitouch/Gestures
  • Screen Dimming
  • SMS/TEL URI Schemes
  • SSL Certificate dialog
  • Virtual Keyboard
  • CameraRoll 
  • Screen Orientation

AIR installers troubleshooting

Please refer to the following tech note for installer troubleshooting:

Tips and tricks

Installer logs for AIR 2 application and runtime installation

In AIR 2 and later versions, installation logs are created by default in a log file. The file is named "Install.log" on Linux and Windows. The file is named "system.log" on Mac OS. This log file is cumulative meaning that a new log is appended at the end of the existing log file whenever an attempt, successful or unsuccessful, is made to install or update the AIR runtime or an AIR application. The size of the log file is limited to 0.5MB and will be truncated when exceeding this size.

The location of this file differs from platform to platform:

*On Windows XP: C:\Documents and Settings\<username>\Local Settings\Application Data\Adobe\AIR\logs\Install.log

*On Windows Vista/ Windows 7: C:\Users\<username>\Appdata\Local\Adobe\AIR\logs\Install.log

*On Mac OS X: /private/var/log/system.log (console application)

*On Linux: /home/<username>/.appdata/Adobe/AIR/Logs/Install.log

Known issues and limitations

AIR 2.5 do not include an update to AIR for iOS but future release will add updated support for the iOS platform. 


  • In AIR 2.5, navigateToURL is now able to bring Firefox window to the front on Windows platforms when the window is maximized and is obscured by another window on top of it. However, please be aware that in order for this to work, the application SWF must be compiled and published as Flash Player 10 format, and that the AIR application descriptor must use the 2.5 namespace. (1609175)
  • Pressing command+D works incorrectly in Mac File browsers (1835265)
  • HTMLWebBrowser crash when opening a PDF while user hasn't accepted Acrobat User License. This will be fixed when upcoming version of Acrobat/Reader released.  (2605061)
  • Pressing any key doesn't call key_down handler, until you touch/click the gui of attached application. The workaround is to set the focus on the stage. (2691068)
  • Nothing gets displayed when accessing a resource over HTTPS that has an untrusted certificate on Windows OS (2699857)
  • Systemtray icon transparency not working in Ubuntu10.04


  • File.userDirectory.exists == true, even though no SD card is in the device (2720750)
  • CameraUI - launch(MediaType.IMAGE) will fail with ioError if the phone is connected to a computer with USB storage turned on.
  • CameraUI - Launching the camera user interface moves the AIR application to the background and makes it vulnerable to termination when Android runs low on resources. The same behavior is seen in native applications.
  • [CameraUI] - AIR supports only low resolution video recording using CameraUI.
  • H264 1080p video crashes AIR when trying to go into fullscreen mode (2651229)
  • CPU-utilization for H264 baseline 320x240, 480x320 and 640x480 videos needs improvement (2649196)
  • Higher resolution H264 baseline videos like 480x320 and 640x480 (either profile 3.0 or 3.1) have low FPS performance (2649193)
  • When an audio file is playing and the user interacts with the phone the sound breaks and then continue (2645314)
  • Using filters with hardware acceleration enabled causes incorrect rendering or crash in some cases. (2639731)
  • Setting focus on a TextField object doesn't result in the virtual keyboard being displayed. (2622356)
  • Force Stop deletes local shared objects (2623126)
  • Spark/TLF based text fields are not supported.
  • H264 Seeking doesn't work (2664189)
  • Android app can't load TLF Runtime Shared Library (RSL) (2606237)
  • [StageWebView] Complete event triggered on redirect (2651500)
  • navigateToURL does not launch custom URI (2661688)
  • App doesn't get throttled when Screen is locked (2611491)
  • setting focus on TextField doesn't pop up keyboard (2622356)
  • File.userDirectory.exists reports true even if the sdcard is not present in the device (2719879)
  • [StageWebView] Can't load local image file (2705471)
  • App does not dim out if the video being played is paused. (2615888)
  • Saving a very large bitmap data (4000x2000 size) using CameraRoll.addBitmapData() causes crash (2712034)
  • max value returned by maxTouchPoints is 2.
  • If a RESIZE event is registered with the stage upon application startup, it will be dispatched only when stage.scaleMode is set to StageScaleMode.NO_SCALE.
  • Orientation change event is not dispatched (however application stage will rotate correctly) whenever application rotates "from upSideDown" or "to upSideDown".
  • Runtime error when using SwiftKey custom Android keyboard with any AIR application (2729775)

AIR Knowledge Base

 For additional information on known issues, please visit the Adobe AIR support web site





Adobe logo

Sign in to your account