1. Flash Player For Mac Downloads
2. Flash Player For Mac Update
3. Adobe Flash Player For Mac
4. Flash Player For Mac
5. Adobe Flash Player

Adobe Flash Player for Mac is the high performance, lightweight, highly expressive component that delivers powerful and consistent user experiences across various versions of the Mac OS, different browsers, and countless mobile devices.

Welcome to the Flash Player and AIR 30 release notes!

August 14, 2018

In today's scheduled release, we've updated Flash Player with important bug fixes and security updates.

July 10, 2018

In today's scheduled release, we've updated Flash Player with important bug fixes and security updates.

June 7, 2018

In today's scheduled release, we've updated Flash Player and AIR with important bug fixes, security updates, and new features.

How to update Flash Player

Current Flash Player customers who have enrolled in the 'Allow Adobe to install updates (recommended)' update mechanism will be automatically updated to the latest version of Flash Player within 24 hours after release.

Users who have selected 'Notify me to install updates' will receive an update notification dialog within 7 days from release date. Please note that Windows users will need to restart their system or log out and in to activate the update notification dialog.

The latest version of Flash Player can always be downloaded and installed by simply visiting https://get.adobe.com/flashplayer

Customers using Google Chrome or Windows 8.x/10 Internet Explorer or Microsoft Edge will receive updates through the Google and Microsoft update mechanisms.

How to contact us

We hope you enjoy this release. If you encounter any problems, please let us know by posting issues to our public bug database. For installation or usage help, please visit our community forums for assistance.

Adobe Bug Database - https://tracker.adobe.com/
Flash Player Forums - http://forums.adobe.com/community/flashplayer
AIR Forums - http://forums.adobe.com/community/air

August 14, 2018

• Flash Player quits unexpectedly when changing the audio output through system sound panel (FP-4198866)
• Assorted security and functional fixes

July 10, 2018

Flash Player

• Assorted security and functional fixes

June 7, 2018

Flash Player

• Host cannot promote Participants into Host or Presenter role in a Connect Meeting.
  

Flash Player For Mac Downloads

AIR

• ETC2 with Alpha textures when used in starling are not rendered in Android
• Apple store REJECTION - AIR SDK using non-public APIs (AIR-4198623)
• Error installing ad-hoc application on device using ad-hoc provisioning
• Error with App Upload to Apple app store for missing NSLocationAlwaysUsageDescription and NSLocationWhenInUseUsageDescription keys
• ADT to correctly sign dynamic frameworks included packaged with iOS app (AIR-4198407)
• Echo during video conference (AIR-4198549)
• iphone8 and iphonex, map using atf the etc2 map will appear maze or color variegated.(AIR-4198515)
• [Swift ANE] Dynamic framework signing issue
• ATFViewer does not get launched.
• Runtime.apk showing incorrect version on devices.
• Packaging an application for iOS using dynamic framework gives NullPointerException when packaging with distribution certificate (AIR-4198408)
• ADT to correctly sign dynamic frameworks included packaged with iOS app (AIR-4198407)
• iOS app uploading to AppStore via iTunes shows WARNING ITMS-90722: 'Certificate Expired” ( AIR-4198649 ,AIR-4198650)

With AIR 30, the C++ Compiler has been upgraded to Standard C++14 in the AIR Runtime. For more information, please refer to https://isocpp.org/wiki/faq/cpp14.

Flash Player For Mac Update

For AIR 30, the NDK for Android has been upgraded to Android NDK, Revision 16b (December 2017). More information is available at https://developer.android.com/ndk/downloads/revision_history.

Significant changes have been made in the tools used to build the runtime, but this should not affect any functionality on Android or iOS. If you encounter any performance or functional issues, please raise them on the AIR developer forums and our bug tracker.

In response to a class of recently disclosed vulnerabilities in popular CPU hardware related to data cache timing (CVE-2017-5753, CVE-2017-5715, CVE-2017-5754), known popularly as Spectre and Meltdown, we are disabling the ‘shareable’ property of the ActionScript ByteArray class by default. Administrators can turn this feature back on using the following MMS properties:

EnableInsecureByteArrayShareable

Short Description:
Allows Administrators to override the Flash Player 30 and above default behavior of restricting the “shareable” property of the ActionScript ByteArray API class.

Detailed Description:
EnableInsecureByteArrayShareable = [0,1] (0=false, 1=true)

This setting will allow Administrators to override the Flash Player 30 and above default behavior of restricting the “shareable” property of the ActionScript ByteArray API class. Shared ByteArrays are used to share data between threads with ActionScript “Workers.” Shared ByteArrays are an advanced feature of the ActionScript API set and not commonly used in the vast majority of published Flash content. For increased security, we recommend administrators leave this feature disabled.

EnableInsecureByteArrayShareableDomain

Short Description:
Allows Administrators to override the Flash Player 30 and above default behavior of restricting the “shareable” property of the ActionScript ByteArray API class on a per-domain basis.

Detailed Description:
EnableInsecureByteArrayShareableDomain = domain name or IP address

By default, Flash Player 30 and above will no longer allow the “shareable” property of the ActionScript ByteArray API class. The EnableInsecureByteArrayShareableDomain settings provide exceptions to that rule. Administrators can create a “white list” of approved domain names or IP addresses to which the EnableInsecureByteArrayShareable setting will apply. If the active security context is in the list of domains and IP addresses, then access to the sharable ByteArray property will be allowed. Otherwise, sharable ByteArray access will be denied.

For domain names, prefixing a * wildcard is allowed. For example, *.adobe.com would allow all Flash content with the “shareable” property to run on www.adobe.com, get.adobe.com, helpx.adobe.com, and so on. Wildcards are not allowed when specifying IP addresses.

For example, the following settings allow SWFs using the shareable ByteArray property to only run on servers at www.mydomain.com and 10.1.1.10:

EnableInsecureByteArrayShareableDomain=www.mydomain.com
EnableInsecureByteArrayShareableDomain=10.1.1.10

For domain names, prefixing a * wildcard is allowed.

Example:

EnableInsecureByteArrayShareableDomain=*.mydomain.com

This would allow all Flash content with the “shareable” property to run on www.mydomain.com, foo.mydomain.com, and so on. Wildcards are not allowed when specifying IP addresses.

EventJitterMicroseconds

Setting this value to 0 disables an important mitigation for Spectre and Meltdown (CVE-2017-5753, CVE-2017-5715, CVE-2017-5754) style attacks, but may improve application performance in some limited circumstances.

TimerJitterMicroseconds

Setting this value to 0 disables an important mitigation for Spectre and Meltdown (CVE-2017-5753, CVE-2017-5715, CVE-2017-5754) style attacks, but may improve application performance in some limited circumstances.

For information on managing the mms.cfg file, please see the Flash Player System Administrator's guide, here: http://www.adobe.com/devnet/flashplayer/articles/flash_player_admin_guide.html

Adobe Flash Player For Mac

Note:

For a full list of features in Flash Player and AIR, including features introduced in previous releases, please review the document here

• ETC2 with Alpha content having LZMA/JPEG-XR compressions have black dots/lines when rendered on Android
• ETC2 Non Alpha ATF are not rendered in ADL
• StageWebView is not able to load punycoded URLs

Flash Player

• Video created using authplay produces jagged-edge-shapes if stage-color is ignored
• Audio output from Firefox is from a separate container in the volume mixer instead of browser

Authoring for Flash Player 30

To use the new Flash Player, you will need to target SWF version 41 by passing '-swf-version=41' as an extra compiler argument to the ASC 2.0 compiler. Detailed directions are below.

• Download the new playerglobal.swc for Flash Player 30
• Download and install Flash Builder 4.7 from Creative Cloud: https://creative.adobe.com/products/flash-builder
• Backup the existing AIR SDK if you need to restore it later then replace the bundled AIR SDK with the AIR 30 SDK. To do this, unzip the AIR 30 SDK to this location:
  • MacOS: /Applications/Adobe Flash Builder 4.7/eclipse/plugins/com.adobe.flash.compiler_4.7.0.348297/AIRSDK
  • Windows: C:Program FilesAdobeAdobe Flash Builder 4.7 (64Bit)eclipsepluginscom.adobe.flash.compiler_4.7.0.349722AIRSDK
• In Flash Builder, create a new project: File -> New -> project.
• Open the project Properties panel (right-click and chose 'Properties').
• Select ActionScriptCompiler from the list on the left.
• Add '-swf-version=41' to the 'Additional compiler arguments' field.
  • This ensures the outputted SWF targets SWF version 41. 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 30 build in your browser.

Flash Player For Mac

Authoring for AIR 30Update to the AIR 30 namespace

Adobe Flash Player

You must update your application descriptor file to the 30 namespace in order to access the new AIR 30 APIs and behavior. If your application does not require the new AIR 30 APIs and behavior, you are not required to update the namespace. However, we recommend all users start using the AIR 30 namespace even if you are not yet taking advantage of the new 30 capabilities. To update the namespace, change the xmlns attribute in your application descriptor to: <application xmlns='http://ns.adobe.com/air/application/30.0'>

Found a bug? Please submit a bug to the Flash Player and Adobe AIR bug database.

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 Instructions for Reporting Video Playback Issues. 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!

For the latest Flash Player system requirements please review the document here

For the latest AIR system requirements please review the document here

Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices | Online Privacy Policy