If you still have trouble downloading adobe flash player 11.4.0 apk or any other file, post it in comments below and our support team or a community member will help you! If no files were found or matches are not what you expected just use our request file feature. Adobe® Flash® Player is a lightweight browser plug-in and rich Internet application runtime that delivers consistent and engaging user experiences, stunning audio/video playback, and exciting gameplay.

Release Date: 10/8/12. Crashes when navigating to/from Flash content in Internet Explorer(3328165).

Unable to package an application using an ANE on iOS, which doesn't not implement the finalizer function. (3325320). Packaging fails with null pointer exception, when packaging an IPA using only the default implementation in the ANE on iOS. (3325321). Database data is wiped out for every launch on iOS Simulator. Release Date: 10/8/12 As of 9/19/12 iOS6 SDK is no longer in Beta.

ActionScript Workers. With the introduction of Workers to ActionScript and the Flash Runtime, Flash Developers can now offload certain tasks like high-latency operations and long-running computations to 'Background Workers'. These Background Workers run concurrently in order to leverage more machine resources and avoid things like UI freezes. Note: To fully leverage ActionScript Workers and be able to debug workers, the next version of Flash Builder is required.

This next version of Flash Builder will be made available through public beta in the August timeframe. Note: Shared memory support (ByteArray.shareable) has been moved to a forthcoming release of Flash Player. Sandbox Bridge support. Sandbox bridging allows specific ActionScript objects or functions to be exposed between SWF-to-SWF cross-domain communication.

This feature is already available in AIR and is being ported to Flash Player in this release. Licensing support: Flash Player Premium Features for Gaming (Flash Player).

With the introduction of Premium Features for gaming we now allow non-ActionScript workflows to target Flash Player. This release supports Premium Features license control of the XC APIs (the combined use of the domain memory API and Stage 3D hardware acceleration API) in Flash Player. These APIs are used by some third party tools such as Unity and Adobe’s Project 'Alchemy' C/C compiler. For more information, please visit. Stage3D 'constrained' profile for increased GPU reach. The Flash Player will gate the use of hardware acceleration based on the date of your video card's driver.

In previous releases, we gated support to drivers older than January 1, 2008. In this release, we will be changing the gating to apply to drivers older than January 1, 2006.

Content using wmode=direct (or renderMode=direct for AIR) should be hardware accelerated on graphics card driver date newer than 1/1/2006 when possible. This applies to Stage3D and StageVideo StageVideo APIs. In addition to that, we added a new profile for Stage3D called 'constrained' profile, allowing your content to run hardware accelerated on the previously blacklisted Intel® GMA chipsets.

See below for more details about this new profile and how to leverage it. LZMA support for ByteArray. In addition to zlib compression of ByteArray, we are introducing an additional compression type based on LZMA to compress data inside a ByteArray through ByteArray.compress and ByteArray.uncompress.

Compressed texture with alpha support for Stage3D (Flash Player and AIR). Transparent images are now supported for compressed textures (ATF file format). StageVideo attachCamera/Camera improvements. This feature exposes a new method on StageVideo objects that allows the Actionscript code to direct the video stream from the camera to a StageVideo object thus leveraging the GPU for rendering instead of the rasterizer. This allows the player to be much faster when processing a video stream from the camera when GPU acceleration is available.

DXT Encoding. This feature enables encoding of uncompressed textures into the DXT format during runtime, so that the texture can be uploaded to the GPU as a compressed DXT texture. Available on desktop for both Flash Player 11.4 and AIR 3.4 Deprecated Carbon APIs for AIR. As of Mac OS X 10.8, Carbon APIs will no longer be supported by Apple. Hence these APIs and other deprecated code is being removed from AIR in this release to be in parity with Mac OSX 10.8. Direct AIR deployment using ADT.

This new feature enables the developer to deploy an AIR application on iOS devices without having to use iTunes or XCode. Please note that iTunes 10.5.0 or greater must be installed on the user's machine to be able to use this feature.

IOS Push Notifications. This feature will use APNS (Apple Push Notification Service) and a provider (third party server which will communicate with the APN) to generate notifications. A new package, flash.notifications has been introduced. The delivery of push notifications is completely dependent on Apple Push Notification Service and APNS does not guarantee the delivery of push notifications. Apple also recommends subscribing to push notifications every time an application is launched. Every time the client app subscribes to push notifications, the APNS provides a token-id to the client app and this token-id should be sent to the third party server or provider that will be sending the remote notifications.

Ambient AudioPlaybackMode. With AIR 3.4, users will have the option of one more AudioPlaybackMode i.e. AMBIENT other than VOICE and MEDIA. This new AudioPlaybackMode will allow the users to force their application to honor the 'hardware mute switch' present in iphone(s) /ipad(s). The strongest use case of this Ambient playbackmode is in the game apps where the user of the app will have the option to silence the game sound and also can listen to the music of any other app in background. In Ambient mode, audio respects the hardware mute switch only on iOS devices. On Android TM devices, the Ambient mode will be just like the Media mode. Exception Support in Native Extensions for iOS.

A native extension for iOS can now use both C and Objective-C exceptions. It is up to the extension to catch all the exceptions thrown in its code. The runtime will not catch the exceptions thrown by extensions. ADT option to list the attached mobile devices.

A new option, '-devices' has been added in ADT to list the attached iOS/Android TM devices. Users can avail this option instead of using adb for listing the Android TM devices and idb for listing the iOS devices. Please note that iTunes 10.5.0 or greater must be installed on the user's machine to be able to use this feature. ADT option to resolve ANE symbol conflicts on iOS.

As application developers may use multiple native extensions obtained from various resources, a common symbol name in the 2 ANEs may give a packaging error saying there’s a duplicate symbol in the object files, or a crash at runtime. To circumvent this issue, a new ADT option, -hideAneLibSymbols, has been introduced, which can be specified at the time of packaging the application. It can take the values – yes or no, where yes hides the library symbols of each ANE from other ANEs. When code is executing within the context of a non-primordial worker (i.e. The background), some flashruntime API behavior will be different from that of Actionscript code that executes in the main thread.

The following APIs will behave differently when used from within a background worker. Non-functional APIs The following APIs will not be available from within a background worker. Any attempt to construct an instance of any of these will throw an IllegalOperationError with the message 'This feature is not available within this context,' the errorID will be the same in all instances, allowing developers to key off of this value. The client application can store in its bundle the alert message strings translated for each localization it supports. The provider specifies the loc-key and loc-args properties in the aps dictionary of the notification payload.

When the device receives the notification, it uses the aps dictionary properties to find and format the string localized for the current language which it then displays to the user. Localized strings must reside in the file called Localizable.strings in the appropriate.lproj folder. Each entry in this file has a key and a localized string value, the string can have format specifiers for the substitution of of variables values. When an application asks for a particular string, it gets the resource that is localized for the language currently selected by the user. In order to receive localized remote notifications, an AIR application must have localized key value pairs in Localizable.strings file in the /lproj folder inside the ipa. To add the Localizable.strings in the ipa, the developer just needs to add the respective.lproj folder in the adt command as follows: adt -package -target ipa-app-store -provisioning-profile -storetype pkcs12 -keystore -storepass app.xml sample.swf en.lproj es.lproj fr.lproj Please note that lproj folder needs to be present in the current directory to let the adt merge the files in appropriate lproj folder. If the lproj folder is given as a/b/c/en.lproj,then adt adds this as a/b/c/en.lproj and hence localized key value pairs won’t be accessible to the application. ADT option to list the attached mobile devices You can use the following command to get information about the attached iOS/Android TM devices.

Authoring for Flash Player 11.4 To use the new Flash Player, you will need to target SWF version 17 by passing in an extra compiler argument to the Flex compiler: -swf-version=17. Directions are below. If you are using the Adobe Flex SDK:. Download the new playerglobal.swc for Flash Player 11.4. Download Flex 4.5.1 SDK (4.5.1.21328) from the Flex 4.5 SDK table.

Install the build in your development environment. In Flash Builder, create a new ActionScript project: File - New - ActionScript project.

Open the project Properties panel (right-click and chose 'Properties'). Select ActionScript Compiler from the list on the left. Use the 'Configure Flex SDK's' option in the upper right hand corner to point the project to Flex build 21328. Configure your project to target SWF version 17. Open the project Properties panel (right-click and chose 'Properties'). Select ActionScript Compiler from the list on the left.

Add to the 'Additional compiler arguments' input: -swf-version=17. This ensures the outputted SWF targets SWF version 17. If you compile on the command-line and not in Flash Builder, you need to add the same compiler argument. Ensure you have installed the new Flash Player 11.4 build in your browser.

Authoring for AIR 3.4 Update to the AIR 3.4 namespace You must update your application descriptor file to the 3.4 namespace in order to access the new AIR 3.4 APIs and behavior. If your application does not require the new AIR 3.4 APIs and behavior, you are not required to update the namespace. However, we recommend all users start using the AIR 3.4 namespace even if you are not yet taking advantage of the new 3.4 capabilities. To update the namespace, change the xmlns attribute in your application descriptor to.

Please submit a bug to the Flash Player and Adobe AIR. Flash Player and AIR may leverage your graphics hardware to decode and play H.264 video.

There may be video issues that can only be reproduced with your particular graphics hardware and driver. When reporting an issue involving video, it is essential to note your graphics hardware and driver, along with your operating system and browser (when using Flash Player), so that we can reproduce and investigate issues. Please be sure to include this information as described in. Note: Due to the high volume of email we receive, we are unable to respond to every request. Thank you for using Adobe® Flash Player® and AIR® and for taking the time to send us your feedback!