Accessibility

Release notes for Adobe AIR developers

Release date: 6/9/2010

System requirements

System Requirements

  Windows® Macintosh® Linux
Processor Minimum 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
Operating System Windows Vista® Home Premium, Business, Ultimate, or Enterprise including 64 bit editions, Windows Vista SP1, Windows XP Tablet PC Edition SP2 and SP3, Windows XP SP2 and SP3, Windows 2003/2008 Server, Windows 7 Mac OS 10.5 or Mac OS 10.6 Fedora Core 12, Ubuntu 9.10, OpenSUSE 11.2
Memory Minimum: 512MB RAM; Recommended: 1GB RAM Minimum 512MB RAM; Recommended: 1GB RAM 1GB RAM

Note: AIR 2 does not support Windows 2000 and Mac PowerPC. Additionally, Mac OS 10.4 is not a supported development environment when using the AIR 2 SDK.

Additional Requirements for Linux Systems

Supported desktop environments GNOME or KDE
Package management systems RPM or Debian
Minimum GTK+ version 2.6
Window managers Metacity (default for GNOME) or KWin (default for KDE)
Transparency 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 of AIR applications from the web requires Flash Player 10.0.15.3 or later

Libraries required to run AIR 2 on Linux

A list of libraries required to run AIR 2 on Linux are listed in the following Adobe Knowledge Base (KB) article: http://kb2.adobe.com/cps/838/cpsid_83888.html

Supported languages

Adobe AIR 2 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

Version information

  • The version of WebKit in AIR 2 is based on the version shipped with Safari 4.0.3.
  • The version of Flash Player included in AIR 2 is 10.1.53.64.
  • libXML version: 2.7.6 on Windows (system libXML on Mac/Linux)
  • SQLite version: 3.6.16

What's new in AIR 2

ADL support for screen size simulation with the mobileDevice profile

ADL provides a new feature to support screen size simulation when the movileDevice profile is specified. Please read details in the section below, "ADL screen size simulation in the mobileDevice profile."

Configurable HTTP Idle timeout

URLRequest.idleTimeout and URLRequestDefaults.idleTimeout let you specify the amount of time (in milliseconds) that a connection will for the server response after a request is sent.

DNS resolution

You can now use the DNSResolver class to look up the following types of resource records:

  • ARecord (IPv4 address for a host)
  • AAAARecord (IPv6 address for a host)
  • MXRecord: mail exchange record for a host
  • PTRRecord: host name for an IP address
  • SRVRecord: service record for a service

Enhanced drag-and-drop support

Using the new FilePromise APIs, it is now possible to drag and drop files that exist on a remote server or that haven't been generated yet. You can copy such files by dragging them out of the AIR application and onto the desktop. This enables new user interaction possibilities for applications like content management systems, online stores, or FTP clients.

Enhanced socket support

New socket properties allow you to access the local address, local port, remote address and remote port.

Enhanced printer interaction

New printing support allows finer control of the way content is printed from an AIR application, including the choice of printer, paper size, and number of copies. New APIs allow a developer to retrieve additional printing information, such as printable area, whether the printer will print in color, and whether the print job is currently active. It is also possible to print without displaying the print dialog.

IME API and IME text input enhancement

There are several new features added in this release to support better text input handling with IME software. The new API enhancements are designed to use with the new Flash Text Engine (FTE).

Increased maximum window size

Large screen displays now can display windows that are 4,096 pixels horizontal x 4,096 pixels wide. It used be 2880 x 2880 in previous version.

Local microphone API

Record audio locally on your device without the need of a server.

Mass storage device detection

Detect when mass storage devices such as cameras and USB flash memory drives are available to synchronize files such as photos, videos, mp3 files or other files.

Native document handlers to open document

Open popular document types like .pdf, .psd, .doc, .ppt, and .mp3 using the native application associated with that file. For example, opening an .mp3 file will launch iTunes on systems where iTunes is the default application for mp3 files.

Native process APIs

Developers can now launch and communicate with native processes using the standard input, output, and error streams. Using the Native Process API, it is now possible to communicate with native libraries built using Java and .NET and also native applications such as "grep" for file searching. You can also create operating system specific installers (native installers). Applications that use the native process API must be deployed using a native installer.

Native installer

You can package an AIR application in a native install program instead of an AIR file. Applications packaged and installed using a native installer have access to platform-specific features such as the Native Process API. See Packaging an AIR application in a native installer.

Nested Transactions

The local SQLite database now provides support for nested transactions.

Network Information

The new NetworkInfo object lets you enumerate the network interfaces on a computer and access the properties of an interface such as whether it is active, the IP address, and the display name.

New Webkit with additional HTML5 and CSS3 support

New capabilities such as CSS transforms, animations, and canvas support are now available. See section "Adobe AIR and AJAX" for additional details.

Socket servers and peer-to-peer networking

Build peer-to-peer applications or local servers that make it easier to communicate with other local applications or remote applications over the network.

TLS/SSL sockets

You can now connect to a server that requires TLSv1 or SSLv3 for socket communications.

UDP networking support

Runtime support for user datagram protocol (UDP) allows developer to build time-sensitive, real-time networking applications such as multi-player games.

Faster JavaScript engine

JavaScript code runs 50% faster without any code changes to the application using the new SquirrelFish Extreme JavaScript engine.

Multitouch and gestures

Build entirely new types of applications using multitouch (Windows 7 only) and Gestures (Windows 7 and Mac OS 10.6). Multitouch is not supported in Windows 7 Starter and Home Basic.

Performance improvements

Applications run faster and use system resources more efficiently.  The CPU usage of idle applications has been reduced, as has overall memory usage. The runtime itself is also smaller.

Cross-platform vector printing (Mac and Win)

Vector printing, already available on Windows, is now available on the MAC.

NOTE: Vector printing is not supported on Linux.

Global error handler

When an unexpected error happens within an application, developers can now capture that event as an exception and present useful information back to the user such as instructions on how to report the issue or restart the application.

IPv6 network support

Support for next generation secure internet protocol.

New Linux .deb & .rpm installers

AIR 2 can be installed using Debian and rpm package installers in addition to the binary installer.

Security improvements

TLS sockets (encrypted sockets) and access to the MAC address are supported. The new File.downloaded property lets you indicate that a file was downloaded from the network and the OS should prompt the user with a confirmation dialog before opening it.

Support for screen readers (Windows only)

Enable applications built using Flash or Flex work with a screen-reader application.

Changes in AIR 2

Windows 2000 and Mac PowerPC are no longer supported

Users with these operating systems will continue to be able to install and run AIR 1.5 applications, but will not be able to install or update to the AIR 2 runtime. These operating systems are not supported when developing AIR applications with the AIR 2 SDK.

Updated AIR 2.0 Namespace

You must update your application descriptor file to the 2.0 namespace in order to access the new AIR 2 APIs and behavior. If your application does not require the new AIR 2 APIs and behavior, you are not required to update the namespace from 1.x based namespace. To update the namespace, change the xmlns attribute in your application descriptor to:

http://ns.adobe.com/air/application/2.0

AIRCore framework changes

There is a new AIRCore framework, which includes the existing service monitoring classes, as well as a couple of additions :

air.net.ServiceMonitor
air.net.URLMonitor
air.net.SocketMonitor
air.net.SecureSocketMonitor
air.desktop.URLFilePromise

The SecureSocketMonitor class is a new addition that takes advantage of the new SecureSocket class available in AIR 2. The URLFilePromise class implements the IFilePromise interface using an HTTP data source. The entire service monitoring framework, plus the new additions, are now packaged in a new library file, aircore.swc and aircore.swf. The original library files, servicemonitoring.swc and servicemonitoring.swf, are still included in the AIR 2 SDK, but use of these files is deprecated. We recommend switching to using aircore.swc in your Flex- and Flash-based applications, and switching to aircore.swf for HTML-based applications.

Return values for HTML <input type="file"> elements vary based on the sandbox type

In an AIR application that uses the AIR 2.0 namespace, the value property of an HTML <input type = "file"> element differs depending on the sandbox of the HTML content. If the document containing the input element is in the application sandbox, the value property is set to the full path of the file chosen by the user (for example, "C:\air\file.txt"). If the document containing the input element is in a non-application sandbox, the value property is set to the file name only (for example, "file.txt").

In an AIR application that uses a namespace of 1.5 or earlier, the value property of an HTML <input type = "file"> element always returns the full path to the file. This is true whether the HTML content is in the application sandbox or in a non-application sandbox.

Installing/Uninstalling Adobe AIR and Installing AIR application

Please refer to the End User release note for information about Installing and Uninstalling Adobe AIR and about Installing AIR applications.

API Versioning

The AIR API versioning scheme is not currently enforced by the ActionScript compiler made available in Flash Professional, Flash Builder, Flash Catalyst, and the Flex SDK. An application using an older AIR namespace (e.g. 1.5) but developed with a tool supporting a newer version of AIR (e.g. 2.0) will be able to successfully reference and compile when using newer APIs. However, when that application is run, attempting to use one of the newer APIs will result in a runtime error or incorrect behavior. To avoid this issue, we recommend updating your application to the latest namespace supported by the authoring tool in use.

Using AIR SDK with Flash Builder and Flash Professional

The AIR 2 SDK can be used on its own to develop HTML-based AIR applications or with the Flex SDK to develop ActionScript or Flex-based AIR applications. The Flex SDK is free, open source, and is available for download from http://opensource.adobe.com/.

How to Overlay the Adobe AIR 2 SDK for Use with the Flex SDK

  1. If you are running Flex Builder, exit the application.
  2. Make a copy of the Flex SDK that you want to overlay the AIR SDK on top of. The following are some examples of Flex SDK folders:
    * Windows Flex Builder 3: c:\Program Files\Adobe\Flex Builder 3\sdks\3.2.0
    * Windows Flash Builder 4:\Program Files\Adobe\Adobe Flash Builder 4\sdks\4.0.0
    * Mac Flex Builder 3: /Applications/Adobe Flex Builder 3/sdks/3.2.0
    * Mac Flash Builder 4: /Applications/Adobe Flash Builder 4\sdks\4.0.0 
    
  3. Download the AIR 2 SDK file for your operating system and save it to the root folder of the Flex SDK you made a copy of in the first step.
    • Windows: AdobeAIRSDK.zip
    • Mac OS: AdobeAIRSDK.tbz2
  4. Extract the contents of the AIR SDK archive and overwrite the existing SDK files.
    • Windows: Right-click on the ZIP file and select "Extract All" or use the decompression tool of your choice.
    • Mac OS: In Terminal, cd to the root folder of the Flex SDK and run this command:
      tar jxvf AdobeAIRSDK.tbz2  

      If you have trouble overwriting files due to file permissions, try this command:

      sudo tar jxvf AdobeAIRSDK.tbz2  

How to Overlay the Adobe AIR 2 SDK for Use with Flash Professional

Flash Professional CS4

If you use Flash Professional CS4 to build Adobe AIR applications, please follow the instructions below to manually update to the AIR 2 SDK.

  1. Update Flash Professional CS4 to the latest update version at http://www.adobe.com/support/flash/downloads.html or select "Help > Updates... " from within Flash CS4.
  2. Quit Flash Professional CS4 if it is open.
  3. Navigate to the Flash CS4 installation folder. The default location on Windows is "C:\Program Files\Adobe\Adobe Flash CS4\" and on Mac OS "/Applications/Adobe Flash CS4/"
  4. Within the "Adobe Flash CS4" folder you should see a folder called "AIK1.5". If this folder is not present repeat step #1.
  5. Rename the folder "AIK1.5" to "AIK1.5 ORIGINAL".
  6. Make a new folder called "AIK1.5"
  7. Download the Adobe AIR 2 SDK and uncompress the contents of the folder to the new "AIK1.5" folder you just created.
  8. Copy the "airglobal.swc" file located within the "Adobe Flash CS4/AIK1.5/frameworks/libs/air/" folder into the "Adobe Flash CS4/Common/Configuration/ActionScript 3.0/AIR1.5/" folder.

Flash CS4 is now configured to use the AIR 2 SDK.

In order to take advantage of the new AIR 2 features, you must update your application descriptor file to use the AIR 2.0 namespace. See the section "Updating Your Application Descriptor Namespace" for additional details on how to update it.

Updating Your Application Descriptor Namespace for Flash CS4

You must manually change the application descriptor generated by Flash Professional CS4 for every new AIR 2 project.

How to locate the application descriptor file for an existing project.

If you have an existing AIR project, navigate to the folder that contains your SWF file and open the application descriptor file. By default, the name of the application descriptor file will be the name of your .swf plus include "-app" in the name. For example, if the .swf file is named mygame.swf, the application's descriptor file will be "mygame-app.xml".

How to locate the application descriptor file for a new project.

For a new project, you will need to do the following steps to create and update the application descriptor file:

  1. Launch Flash Professional CS4.
  2. Select "File > New...".
  3. Select "Flash File (Adobe AIR)" and click "OK".
  4. Select "Flash > Save" and click "OK".
  5. Select "File > AIR Settings..." and click "OK" with the default settings. This will create the application descriptor file.
  6. Navigate to the folder containing your .swf file and locate the .xml file. If the .swf file is named mygame.swf, the application's descriptor file will be "mygame-app.xml".
  7. Open the application descriptor .xml file in a text editor.
  8. Replace the namespace with "http://ns.adobe.com/air/application/2.0" and save the file.

Flash Professional CS5

  1. If you are running Flash Professional CS5, exit the application.
  2. Make a back-up copy of the original 'AIK2.0' folders that were installed with Flash Professional CS5. If you installed into the default path, these folders are located here:
    • Windows: C:\Program Files\Adobe\Adobe Flash CS5\AIK2.0
    • Mac: /Applications/Adobe Flash CS5/AIK2.0
  3. Download the appropriate AIR SDK file for your operating system:
    • Windows: AdobeAIRSDK.zip
    • Mac OS: AdobeAIRSDK.tbz2
  4. Move the AIR SDK archive downloaded in step 3 into the Flash Professional CS5 AIR SDK folder named 'AIK2.0':
    • Windows: C:\Program Files\Adobe\Adobe Flash CS5\AIK2.0[AdobeAIRSDK].zip
    • Mac: /Applications/Adobe Flash CS5/AIK2.0/AdobeAIRSDK.tbz2
  5. Overwrite the existing AIR 2 SDK files in following steps:
    • Windows: Right-click on the ZIP file and select "Extract All" or use the decompression tool of your choice.
    • Mac: In Terminal, cd to the root folder of the SDK and run this command: tar jxvf AdobeAIRSDK.tbz2
      If you have trouble overwriting files due to file permissions, try this command: sudo tar jxvf AdobeAIRSDK.tbz2
  6. Copy and overwrite the "airglobal.swc" file from the "Adobe Flash CS5/AIK2.0/frameworks/libs/air/" folder into the "Adobe Flash CS5/Common/Configuration/ActionScript 3.0/AIR2.0/" folder.

Note: Moving these folders may require administrator authentication depending on your account privileges.

Tips and tricks

Adobe Community Help

Adobe Community Help is Adobe's next generation help experience. It's an AIR application that provides the following features:

  • Access up-to-date definitive reference content online and offline
  • Find the most relevant content contributed by experts from the Adobe community, on and off Adobe.com
  • Comment on, rate, and contribute to content in the Adobe community
  • Download Help content directly to your desktop for offline use
  • Find related content with dynamic search and navigation tools
  • Enjoy content updates and feature enhancements without reinstalling the AIR app

Community Help is installed by default in Creative Suite CS5 and Flash Builder 4. If you're using the AIR SDK separate from those tools, you can install Community Help yourself here: Install Adobe Community Help.

Adobe AIR Documentation

You can find links to all of the AIR documentation on the Adobe Developer Connection.

Adobe AIR Help and Support page

The AIR Help and Support page is a search portal for AIR information from Adobe and the AIR developer community. You'll also find great new articles and tutorials and links to current support issues.

Installer logs for AIR 2 application and runtime installation

In AIR 2, installation logs for the runtime and for individual applications are created by default. 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 the file is truncated when it becomes too large.

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

Mac/Win known issues

  • CSS limitations
    • Currently, using an external font in a style sheet, via the @font-face declaration is not supported.
    • Media device queries are not supported.
    • Unsupported CSS properties:
      • Shadow properties (text-shadow and -webkit-box-shadow) are not supported.
      • Content clipping properties (-webkit-background-clip and -webkit-mask-clip) are only partially supported. Namely, -webkit-background-clip: text; and -webkit-mask-clip:text are not supported. Using them will result in the specified style being applied but with the default value.
    • CSS styling of HTML form controls:
      • Drop-down controls (<select> HTML form element)
        • Changing the background color for the expanded list does not work.
        • Changing the font-color and/or font-family for individual items in the list does not work.
      • Checkboxes and radio buttons (<input type='checkbox' /> and <input type='radio' />)
        • Most CSS properties don't change the actual look and feel of the controls. (This behavior is consistent with the current behavior in the Safari web browser.)
  • Screen reader support
    • Screen reader support is currently available only on the Windows operating system. Screen reading software that is compatible with AIR includes NonVisual Desktop Access (NVDA) and JAWS version 11.
    • Top-level activation and automatic announcement of a screen's contents may not work completely in some cases.
    • Screen reader support is not available for top-level HTML applications and the HTMLloader control. Support is planned in a future release.
    • Focus may switch from an AIR application to the command prompt. Entries in DataGrid ItemRenderers may not be read correctly if a command prompt dialog is open (2365641).
    • When focused on a text field, JAWS 11 may enter "Virtual Cursor" mode and not switch to "Forms" mode when necessary. This can prevent the user from typing into the text field. The workaround is for the user to to tab out of the text field and then tab back into the text field. (2394322)
  • Debugging with Flex Builder or Flash Builder
    • When running or debugging AIR applications with text fields in Flex Builder or Flash Builder on Mac OS, a crash may occur. Some versions of the Flex SDK include outdated nib resource files in the wrong location for the AIR runtime. The workaround is to manually remove the files MainMenu.nib, AuthDialog.nib, and FlashPromptDialog.nib from <sdk folder>/runtime/air/mac/Adobe.AIR.framework/Resources folder. (2460765)
    • When using Flash Builder 4.0, taking a memory snapshot of a large AIR application on Windows may never complete. The workaround is to update Flash Builder to 4.0.1. (2615637)

Non-ASCII URL issue

If an URL contains non-ASCII characters, the application might fail to work properly on Windows if the libraries that the runtime depends on to parse such URLs are not present. If IE 7 is installed, then the necessary libraries are installed and the application should work fine. The problem does not reproduce on Windows Vista and Windows 7. (2477685)

navigateToURL doesn't bring Firefox window to the front as it should

If Firefox is configured as the default browser and a Firefox window is already open in the background, calling navigateToURL doesn't bring the Firefox window to the front on Windows. (1609175)

AIR does not accept high ASCII chars in digital certificate password field

Java versions 1.5 and above do not accept high-ASCII characters in passwords used to protect PKCS12 certificate files. Java is used by the AIR development tools to create the signed AIR packages. When you export the certificate as a .p12 or .pfx file, use only regular ASCII characters in the password.(1908199)

Redundant Mac logo in menu bar on Mac OS 10.6

Mac 10.6 only. When replacing the NativeApplication menu property, the first menu's label always shows mac's logo. The menu functions correctly in other respects. (2442577)

Thai text input problem into AIR HTML

The cursor can move to the wrong position when typing certain Thai characters in HTML content. Text input for languages other than those listed in the supported languages section above is currently not supported. (2486968)

Native Application Installer packaging with unicode file name on Mac

Mac only. Native application installer packaging may fail if the AIR SDK or the files you are packaging are in a path with Unicode-encoded Chinese characters or the <filename> descriptor tag has Unicode-encoded Chinese characters. This is due to an underlying issue Java has with Unicode filenames. (2539439)

Application menu with adl on Mac

Mac 10.6 only. The application menu bar isn't visible when the application is run from command line with adl. The workaround is to switch focus to another application and then return to your app. (2530559)

Windows shortcut (.lnk) files on Windows 7

Some applications on Windows 7 can not be opened using a .lnk file when using file.openWithDefaultApplication. Examples include C:[ProgramData]]\Microsoft\Windows\Start Menu\Programs\Accessories\Sticky Notes.lnk and C:[ProgramData]\Microsoft\Windows\Start Menu\Programs\Administrative Tools\System Configuration.lnk. (2573727)

<IMG> tags won't display ICO files on Mac OS 10.4/10.5

<IMG> tags won't displaying ICO files on Mac OS 10.4/10.5. This limitation does not exist on Mac OS 10.6. (2563698)

EXITING event with Introspector

The EXITING event does not fire properly when Introspector is open in  an HTML-based AIR application. (2559508)

Cannot install 2.0 app over 2.0beta2 app

Users cannot install an 2.0 application over a 2.0beta2 application. Users are shown an error message stating that the AIR file is damaged and to contact the application vendor. A more descriptive error message should be provided in this circumstance. (2559067)

Cannot debug while an installed version of an application is also running

Only a single instance of an AIR application can be running. A workaround is to change the value of the  <id> element in your application descriptor file prior to debugging. (2516616)

Flex 4.0 Spark text and namespace 2.0

Using Flex 4 Spark text components is only supported when using the released version of Flex 4 and AIR 2. Known issues exist in older (beta) versions of Flex 4. The AIR 1.5.x does not support the Spark text components. (2559578)

CPU usage to reach 100%

On certain hardware configurations running Windows XP, the AIR app "theGood Uploader" application can cause CPU usage to reach 100%. (2540843)

Crash using

SecureSocektMonitor

Using both the SecureSocektMonitor and other monitors in the air.net package simultaneously may cause a crash on Mac OS 10.5.8 or later when using a low polling interval, such as 1 ms. The workaround is to use a higher polling interval. (2555669)

Multiple display state events dispatched when calling

NativeWindow.maximize()

On Mac systems, the NativeWindowDisplayStateEvent may get dispatched twice when calling NativeWindow.maximize(). (2564809)

Copying a large amount of files from DVD may be slow

When using the File APIs to copy large amounts of files and data from a DVD, the copying step may experience a sharp slowdown on Mac OS 10.5. The issue is caused by an underlying issue in the OS, which has been fixed in Mac OS 10.6. (2414772)

Printing for transparent text on Windows OS

If you are printing a page containing Flash Text Engine (FTE) text which is transparent and which uses a non-embedded font, the page will not print correctly using the bitmap, vector, or auto print job options. To work around the problem, please embed the font. (2629777)

Timestamping for native installer

ADT currently cannot turn off timestamping for native application installers built on Windows. The '-tsa none' argument will not work when attempting to sign the .exe installer. Typically, developers turn off timestamping while they build and test their applications and they don't have access to the network. The workaround is to not sign the.exe installer in this case. (2628232)

Linux known issues

  • Upgrading to AIR 2 using Debian or rpm packages
    • Upgrading to AIR 2 using Debian or rpm packages is only supported from AIR 1.5.3 onwards. Also, the adobe-certs package, which was a part of AIR 1.5.3 and earlier runtime versions, must be manually removed using the system package manager after upgrading.
    • Runtime versions before AIR 1.5.3 must be uninstalled before AIR 2 can be installed using the Debian or the rpm packages. You can uninstall the AIR runtime by removing the adobeair1.0 and adobe-certs packages using the system package manager.

Native application issue

A native application package created on a computer running OpenSuse 11.2 cannot be installed on older RPM Linux distributions. (2495682)

Badge installation issue with Linux native runtime installations

After installing the runtime using a native package installer, a badge installation may not work and you might see the following error: "Sorry, an error has occurred. The application could not be installed. Try installing it again. If the problem persists, contact the application author. Error #1". This issue is fixed with Flash Player 10.1. The workaround for older versions of Flash Player is to download and save the .air file locally and try installing it using "Adobe AIR Application Installer." After doing so, future badge installations should work as expected.

StorageVolumeChangeEvent event on Linux

  • On Linux, storageVolumeMount event and storageVolumeUnmount event may not get triggered for mount and unmount of network drives. (2363603)
  • On modern Linux distributions, the StorageVolumeInfo object only dispatches storageVolumeMount and storageVolumeUnmount events for physical devices and network drives mounted at particular locations. (e.g. /media and $HOME)

Mailto links issue with Google Chrome

Mailto links do not work if Google Chrome is set as default browser. (2565050)

AIR application name issue with kwallet on KDE

Application name is reported as "anonymous" in the kwallet password dialog which this displayed when an AIR application accesses data in the encrypted local store. (1862087)

Printing on Linux<

  • Only bitmap printing is supported.
  • Page setup dialog options are not supported using the PrintJob class.

Flickering with certain applications

With certain applications like iPlotz, SocialVisor, UVLayer, and Time100, flickering can be observed in the application stage when using these applications. (2487242)

Clipped installation dialog

When installing AIR using the binary installer, the installation dialog at times appears clipped. (2461190)

SSL Authentication dialogs on OpenSuse 11.1

When accessing certain secure sites, a  "SSL Certificate Alert" is displayed.