Adobe® Flex 4.6 SDK Release Notes

Welcome to the Adobe Flex 4.6 SDK release.

About Flex

Flex SDK includes the Flex framework (also known as the Flex class library), Flex command-line compilers, the Flex debugger, the ASDoc utility, and the debugger version of Adobe® Flash® Player and Adobe® AIR® runtimes. Use the Flex SDK to develop, compile, and deploy Flex applications that connect to XML and SOAP web services or connect to various server technologies such as PHP, Adobe® ColdFusion®, Java, and .NET using a server technology such as BlazeDS. Flex applications can be built and configured to target browsers via the Flash Player runtime and desktops or mobile devices via the AIR runtime.

What's Supported

This Flex 4.6 SDK build is and contains:

  • Flash Player
  • TLF
  • OSMF

We strongly suggest you DO NOT overlay different AIR, AIR SDK or Flash Player versions into Flex 4.6 SDK or Flash Builder 4.6. Development, debugging and deployment workflows are only certified with the AIR and Flash Player versions packaged within the products.

Install Your Software

Installation instructions

The Flex SDK installation is delivered as a ZIP file and contains the Flex framework, Adobe AIR framework, and command-line tools, such as the mxmlc command-line utility, Adobe AIR command-line utility, the ASDoc utility, the Flex command-line debugger, and the debugger version of Flash Player.

Uninstall current Flash Player

You should use Flex SDK with the latest version of the debug Flash Player 11. Prior to installing the Flex SDK, you should uninstall your current Flash Player.

Windows–Plugin-based browsers

Run the appropriate uninstaller available from this Tech Note.


Run the appropriate uninstaller available from this Tech Note.


Manual removal (for users who installed the plug-in via Install script):

  • Delete the binary and the flashplayer.xpt file in directory /home/<user>/.mozilla/plugins/

RPM removal:

  1. As root, enter the following command: 

    # rpm -e flash-plugin
  2. Click Enter and follow the prompts.

Install the Flex SDK

  1. Download Flex SDK ZIP file from the Adobe Website or the Adobe Open Source site.

  2. Create a directory to contain Flex SDK.

  3. Extract the Flex SDK ZIP file to this directory. The Flex SDK contains the following directories:

    • /ant — Contains Flex Ant Tasks.
    • /asdoc — Contains helper files for the ASDoc tool that creates HTML documentation from your MXML and ActionScript source code.
    • /bin — Contains the mxmlc, compc, asdoc, and fdb utilities. The bin directory also contains the jvm.config file, which specifies Java settings that you can modify, if necessary.
    • /frameworks — Contains compiled framework classes, configuration files, and framework source code.
    • /lib — Contains JAR files used by the utilities.
    • /runtimes — Contains installers for the Adobe AIR runtime inside the air directory and installers for debug versions of Flash Player 11 inside the player directory.
    • /samples — Contains sample applications.
    • /templates — Contains HTML templates for Flash Player detection and browser integration and inside the air folder, a sample Adobe AIR application.xml file.
  4. Ensure that the Java Runtime Environment (JRE) is installed on the computer and that the java_home/bin directory is defined in the system path. JRE 1.5,or 1.6 is required.

  5. Install the appropriate debug Flash Player from the install_root/runtimes/player/platform directory.

  6. (Optional) When the Flash Player installation finishes, restart your computer to ensure that the updated Flash Player browser plug-in is enabled.

Compatibility Issues

There have been some changes made in Flex 4.5 SDK that alter certain behaviors compared to Flex 4. To get the full list of issues, please refer to the Flex Backwards Compatibility document. In most cases, you can maintain Flex 4 (or even Flex 3) behavior by using the compiler argument, -compatibility-version.

Using the Data Visualization Components with Flex SDK

As of Flex 4, the data visualization components are part of the full SDK distribution.

Using Automated Testing with Flex SDK

As of Flex 4, automated testing support is part of the full SDK distribution.

Known Issues and Notable Changes

This section contains selected known issues and notable changes since the previous release. For a complete list of Flex issues and their status, see the public bugbase. The public bugbase lets you search for known issues, comment on them and add new bugs.

Tip: Use Filters to customize your search.

Flex SDK 4.6 does not support the BlackBerry Tablet OS. Due to conflicts in the embedded AIR version and AIR 3.1 that Flex 4.6 requires, projects exported for BlackBerry will not be compatible.


  • The new default skins for TextInput and TextArea cannot be used with embedded fonts. StageText uses a native text control both for text display and text entry. These native controls cannot use embedded fonts directly.
  • StageText does not support fractional alpha values. So, they will likely not look as intended when placed inside semi-transparent containers.
  • Native TextInput fields cannot be clipped by other Flex content and are rendered in a layer above the Stage.
  • Components that use StageText-based skin classes will always appear to be on top of other Flex components.
  • Flex popups and drop-downs may be obscured by any visible native text fields.
  • Native text fields' relative z-order cannot be controlled by the Flex application.

  • StageText does not support links or html markup. Only plain text is supported.
  • Text in StageText is always selectable.
  • Currently transitions cause redraw issues with StageText. 
  • StageText does not support programmatic control of scroll position at this time.
  • The default value for Application.resize for SoftKeyboard  is false.


  • Zoom and Flip view transitions may incorrectly position the views during a view transition.
  • View transitions used inside a SplitViewNavigator may incorrectly clip the ActionBar during the animation.
  • The inherited styles of a navigator will change when a navigator is displayed in a callout. This may result in the first navigator looking different when it is shown inside a callout. A workaround is to set all styles that are incorrectly inherited on the ViewNavigator. 
  • Performance problems may arise when animating both view navigators at the same time.
  • During a view transition, layout is disabled, so other animations dependent on layout cannot run during a view transition.


© 2011 Adobe Systems Incorporated. All rights reserved.

Adobe, AIR, Flash Builder, Flex and LiveCycle are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.

iPhone and iOS are trademarks of Apple Inc., registered in the U.S. and other countries. 




This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy