Release Notes for Flash Player 28 and AIR 28

Welcome to the Flash Player and AIR 28 release notes!

 

February 6, 2018

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

 

January 9, 2018

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

 

December 12, 2017

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

Announcements

Android AIR Runtime Play Store Availability
Adobe will be unpublishing the shared AIR Runtime from the Google Play Store for all devices running Android 4.0 or below on March 13th, 2018.  AIR applications that require the shared runtime will not be able to be able to access the required download from the Play Store from these older systems.  We recommend impacted developers convert and republish their applications to use the captive runtime before March 13th.
 
App Transport Security
With macOS 10.11, Apple has introduced App Transport Security (ATS) which mandates that applications use secure network connections over HTTPS only. Because this is a significant change, Apple has provided applications an override via NSAllowsArbitraryLoads which will allow insecure connections.
 
With AIR SDK 27, all AIR applications built for macOS will automatically have the NSAllowsArbitraryLoads key set as true in their info.plist file. This is a temporary solution. Apple may reject your application during the review process or disable the usage of NSAllowsArbitraryLoads in future OS updates. We recommend using secure network connections over HTTPS in your applications.
 
Android AIR Shared Runtime
Starting with AIR 26, packaging of shared runtime applications for Android has been disabled. With this change, published applications will always have a captive copy of the runtime included in their installation package irrespective of the target the developer has selected (that is, apk or apk-captive-runtime). This change allows us to focus our testing and engineering on captive installations, by far the most popular option for Android.

Fixed Issues

February 6, 2018

Flash Player

  • [Mac] Recorder will be stuck with message "Uploading...X%" while uploading the video using RTMPS protocol. (FP-4198740)
  • Assorted security and functional fixes

 

January 9, 2018

Flash Player

  • Assorted security and functional fixes

 

December 12, 2017

Flash Player

  • [Mac] Flash Player NCP is not launched from system preferences when NPAPI Flash Player is installed
  • [Windows]Playback issues are observed while playing the DRM content on Chrome.
  • Memory leak is observed when running a Stage3D application using Baseline_Constrained profile(FP-4198562)
  • File upload dialog becomes unresponsive on Chrome when using the Scratch editor (FP-4198254)
  • The volume slider is not visible while playing the video from https://www.vudu.com/movies/#!content/74336/CHUD-2-Bud-The-Chud in fullscreen mode.

AIR

  • AIR runtime quits unexpectedly after graphics.readGraphicsData is called.(AIR-4198466)
  • Initiating multiple workers simultaneously causes the application to quit unexpectedly.(AIR-4198267)
  • Anti-aliasing on retina OS X desktop display fails/degrades when Context3D backBuffer is set to 1024x768 or greater.(AIR-4198319)
  • [Android] KeyboardEvent.KEY_DOWN dispatched twice for NEXT button (AIR-4198503)
  • [iOS]Artifacts are observed when child Sprite is near bottom of screen(AIR-4198445)
  • [iOS] ADT to correctly sign dynamic frameworks included packaged with iOS app (AIR-4198407)
  • [iOS] ADT to correctly sign dynamic frameworks (AIR-4198408)
  • [IOS] AIR 23 and newer: Compilation failed while executing: compile-abc - Class (...) could not be found. (AIR-4198225)
  • [iOS] StageWebView does not load nor display local HTML content (AIR-4198420)
  • Improving capabilities.language behavior for Android and iOS
  • [iOS] Launch image issues on iPad Pro
  • [Android] Error #3672: Buffer creation failed when using drawToBitmapData (Context3D) while using VideoTexture (AIR-4198290)
  • [Android] No data from "android.intent.action.SEND" Intent on Android (AIR-4197491)
  • Rotate Image Camera IMAGE Mobile Android/IOS (AIR-4167837)
  • [iOS] Interfaces don't function on iOS when shared between swf's (AIR-4194914)
  • [iOS] Apps created using Flex in AOT mode crashes (AIR-4198266)
  • [iOS] Missing entry for IpadPro10.5Inch - therefore incorrect screen size returned (AIR-4198511)

New Features

Resolution to Adobe AIR applications installation issues

With the release of Flash Player 28, Adobe AIR applications with SHA-1 certificate can be successfully installed after 30th Oct 2017, without the need of re-packaging the AIR application with a new certificate. Refer to our blog post to view the details of Adobe AIR applications installation issue.

Who should use this resolution?

If your developed AIR application fails to install after 30th Oct 2017 and application installation log contains the error: “Package signature validation failed”, it indicates that the application is signed with SHA1 certificate.

The location of the log files for different platforms is mentioned in the article: https://helpx.adobe.com/air/kb/logging-air-2-desktop-application.html 

Resolution:

AIR applications with the above-mentioned issue can be installed using two methods.

 

Using keyboard shortcuts: 

Install the Adobe AIR Runtime

Steps to follow on Windows:

1. Go to C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0

2. While holding the "Ctrl" key,  select the Adobe AIR Application Installer.exe -> Right click on it -> Run as Administrator. Do not take your finger off the "ctrl" key until you see the window open up.

3. Select and open the AIR application to be installed.

Steps to follow on Mac:

1. Go to /Applications/Utilities

2. While holding the "command" key,  double click on the Adobe AIR Application Installer.  Do not take your finger off the "command" key until you see the window open up.

3. Select and open the AIR application to be installed.

The Adobe AIR Application should be installed successfully.

 

Using the new -ignoreExpiredCertificateTimestamp directive while launching AIR Application installer using Command Prompt/Terminal

Install the Adobe AIR Runtime 

Steps to follow on Windows:

1. Open a command prompt as Administrator.

2. Run the following command:

“C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR Application Installer.exe” - ignoreExpiredCertificateTimestamp

3. Window opens up.

4. Select and open the AIR application to be installed.

Steps to follow on Mac:

1. Open Terminal.

2. Run the following command:

/Applications/Utilities/Adobe\ AIR\ Application\ Installer.app/Contents/MacOS/Adobe\ AIR\ Application\ Installer/ -ignoreExpiredCertificateTimestamp

3. Window opens up.

4. Select the AIR application to be installed.

Adobe AIR Applications gets installed successfully.

Swift based ANE Support in AIR (iOS/tvOS)

Starting AIR 28, developers will be able to use Swift based ANE for iOS/tvOS. Developers can also use iOS/tvOS based Dynamic Frameworks while packaging the application for respective iOS/tvOS platforms. Dynamic Frameworks signing will be done while packaging the application.

Steps to create Swift ANE and packaging application:

1. Along with the existing necessary resources for ANE creation, AS developers also need to include dynamic frameworks (relevant .framework files) during ANE creation command. The platform.xml also needs to mention the dynamic frameworks as shown below.

<?xml version="1.0" encoding="utf-8" ?>
 
<platform xmlns="http://ns.adobe.com/air/extension/28.0">
 
<linkerOptions>
 
<option>-rpath @executable_path/Frameworks</option>
 
</linkerOptions>
 
<packagedDependencies>
 
<packagedDependency><dynamic_swift_framework_path></packagedDependency>
 
</packagedDependencies>
 
</platform>

2. Sample ANE packaging command

adt -package -target ane <ane_file> <extesionxml_file> -swc <swc_file> -platform iPhone-ARM -platformoptions <platformxml_file> -C iPhone-ARM/ . -platform appleTV-ARM -platformoptions <tvOS_platformxml_file> -C appleTV-ARM/ .
  • iPhone-ARM folder contains dynamic_swift_framework_file as mentioned in package dependencies in platform_xml, Objective C Static library (.a) built for iOS and library.swf file.
  • appleTV-ARM folder contains dynamic_swift_framework_file for tvOS as mentioned in package dependencies in tvOS_platform_xml, Objective C Static library (.a) built for tvOS and library.swf file.

 

3. Sample IPA Packaging command

adt -package -target <target> -provisioning-profile <path-to-profile> -storetype pkcs12 -keystore <path-to-certificate> -storepass <password> <ipa_file> <appxml_path> <swf_path> Frameworks -extdir extension

Where the <dynamic_frameworks_and_Swift_Dependencies_path> folder, or subfolders inside it contain Swift Frameworks and its dependencies as mentioned below. These Swift dylibs can be found at /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos for iOS

<dynamic_swift_framework>

  • libswiftCore.dylib 
  • libswiftCoreGraphics.dylib 
  • libswiftCoreImage.dylib 
  • libswiftDarwin.dylib 
  • libswiftDispatch.dylib 
  • libswiftFoundation.dylib 
  • libswiftObjectiveC.dylib 
  • libswiftQuartzCore.dylib 
  • libswiftUIKit.dylib

 

For Xcode 9 and Swift 4 support, AS Developers also need to add 3 more swift dependencies as below from iphoneos folder from Xcode.

  • libswiftCoreFoundation.dylib 
  • libswiftMetal.dylib 
  • libswiftos.dylib

Note - Default MinimumOSVersion values for iOS is 8.0 and for tvOS is 9.0.

iOS SDK Upgrade

AIR Runtime is now built with iOS 11 SDK, which enables AIR developers to use ANEs built with iOS 11 APIs without using the –platformSDK switch while packaging with ADT. With iOS 11 SDK, Apple has mandated inclusion of  a few icons in the application. Follow the steps below to incorporate them:

Note: You need to have a Mac machine having Xcode 9.

Launch Xcode 9.

  1. Select File -> New Project -> Single View App (iOS). Fill Product Name, Organization Name and Organization Identifier (no specific names required).
  2. Save the project.
  3. Click Assets.xcassets -> AppIcon -> Drag and drop App store icon of size 1024 * 1024 (1024pt, 1x).
Assets.xcassets

4. Drag and drop iPad App icon of size 76x76 (76pt, 1x) & 152x152 (76pt, 2x).

5. Drag and drop iPad Pro App icon of size 167x167 (83.5pt, 2x).

6. Drag and drop iPhone App icon of size 120x120 (60pt, 2x).

7. Drag and drop iPhone App icon of size 180x180 (60pt, 3x).

Icon Sizes

8. In the drop-down select Generic iOS Device as the build target.

9. Build the project ( Product -> Build).

10. Right-click on your ‘.app’ -> Show in finder.

11. Right-click on your ‘.app’ -> Show package contents.

12. Now copy Assets.car and package with AIR application.

 

All these icons except store icon (1024*1024) need to be packaged along with the application using the icon tags in the app.xml. Refer https://help.apple.com/xcode/mac/current/#/dev4b0ebb1bb for adding icons in assets.car file.

Note - If you are targeting iOS 11 as the minimum supported OS in the application descriptor, the generated IPA will be 64bit only.

Localization of permission purpose strings on iOS

Starting AIR 28, developers can provide localized purpose strings for the permissions required in the application. Developers are required to package an XML file called purposeStrings.xml in the application. The format of this XML file should adhere to the following. A sample xml file is available in AIR SDK at SDK/samples/purposeStrings-sample.xml. Use the below mentioned command to package a sample application using the purposeStrings.xml file.

adt  -package -target <target> -provisioning-profile <provisioning profile> -storetype pkcs12 -keystore <certificate> -storepass <password> <name of the ipa> <application xml> <swf file> purposeStrings.xml

Note:

  • With iOS 11 Apple has added few new cocoa keys which should be included in your application descriptor file, see Information Property List Key Reference | Cocoa Keys.
  • If your application uses CameraRoll.addBitmapData and is being packaged using AIR 28, you need to add the cocoa key NSPhotoLibraryAddUsageDescription in your application descriptor.
  • Applications using Geolocation might not show permission dialog if packaged using AIR 28. To fix this you need to add new cocoa keys in application descriptor as per the usage, for more details refer to Apple's developer documentation.

Android SDK Upgrade

Beginning AIR 28, Android SDK has been upgraded in the AIR Runtime. Here is the list of version numbers of the tools upgraded in AIR 28. There have been significant changes in the tools used to build the runtime. Raise your issues on AIR user forums if you observe any performance or functional issues.

Tool Version
Android SDK Platform 25 ver 3 (Android 7.1.1)
Android SDK build tools 26.0.1
Android SDK tools 26.0.2
Android SDK platform tools 26.0.0
Android NDK 15.1.4119039
Android Support Repository 47.0.0

Android TV Support

With AIR 28, Android TV support for AIR Android applications comes with more stability and improvements.

Developers can develop captive runtime applications that are also compatible with Android TV. Use swf-version 31 or greater and namespace 20.0 or greater to access this feature. The two tags mentioned below need to be added to the app.xml file to support Android TV applications.

1. <supportsAndroidTV></supportsAndroidTV>

Value for the <supportsAndroidTV> tag can be either "true" or "false". If this tag is not added, then the default value will be "false".

<supportsAndroidTV>true</supportsAndroidTV>: Application is supported on Android TV and it will reflect on the home screen of Android TV after the installation.

<supportsAndroidTV>false</supportsAndroidTV>: Application is not supported on Android TV and it will not be shown on the home screen of the Android TV. However, it will be reflected in the downloaded apps inside Settings of the device.

2.<banner></banner>

This is the tag where the user can give the banner image path. Application Banners represent your app or game on the home screens of TV devices and serve as a way for users to launch the app. The specific requirements for a banner image are 320 x 180 px, .png,xhdpiresource. In case the developer does not provide the banner image with <supportsAndroidTV>true<supportsAndroidTV> tag, a default banner image will reflect on the home screen of  Android TV. SDK tools should be updated to version 24.0.0 or higher. In order to access new APIs for TV devices, you must create a project or modify an existing project that targets Android 5.0 (API level 21) or higher. Applications can only be packaged with –targetapk-captive-runtime for Android TV. Android TV support is available from AIR SDK 20.0 or higher, and so the namespace needs to be added accordingly inapp.xmlfile.

Sample snippet - Make the below changes in app.xml file parallel to <containsVideo> tag:

<android>
 
        <manifestAdditions><![CDATA[
 
<manifest android:installLocation="auto">
 
.
 
..
 
.
 
</manifest>
 
]]></manifestAdditions>
 
<supportsAndroidTV>true</supportsAndroidTV>
 
<banner>"path of the banner image (320x180 px, .png file)"</banner>
 
</android>

Support for embed bitcode in iOS/tvOS

ADT supports a new option -embedBitcode to add bitcode in your iOS and tvOS applications. For more information about Bitcode, see the App Distribution Guide.

Switch details:
Name of the switch: -embedBitcode
Values(iOS): yes or no. Defaults to no
Values(tvOS):yes or no. Defaults to no(yes for ipa-app-store target as it is a mandatory requirement by Apple)
Usage: -embedBitcode yes
Order: Just before the code signing options
 
Example ADT packaging command:
<AIRSDK>/bin/adt -package -target <target type> <other options> -embedBitcode yes -provisioning-profile <SampleProvisioning.mobileprovision> -storetype pkcs12 -keystore <SampleCertificate.p12> -storepass <password> Example.ipa Example-app.xml Example.swf

Notes:

  • Embedding bitcode enables AIR developers to upload their tvOS applications to the App Store where bitcode is required.
  • Embedding bitcode in your application increases both application size and packaging time.
  • Embedding bitcode requires that all your ANEs also include bitcode. If not present, adt can throw packaging errors such as the following:

ld: bitcode bundle could not be generated because '/var/folders/d3/yxwv5yn5715fk31lq36lnk780000gn/T/805ef2d4-5fe2-4ec9-a773-a3cc39845fa1/lib.nativeExtension.systemVersion.a(systemVersion.o)' was built without full bitcode. All object files and libraries for bitcode must be generated from Xcode Archive or Install build for architecture arm64

Compilation failed while executing : ld64

Apple TV support (Beta Quality)

We have made some enhancements to tvOS support. For more information, see the Release Notes specific to this feature. AIR Runtime is now built with tvOS 11 SDK, which enables AIR developers to use ANEs built with tvOS 11 APIs without using the –platformSDK switch of ADT.

AIR Desktop - Audio Device Manager ActionScript API

The Audio Device Manager ActionScript API was added in Flash Player 27. This functionality is now enabled in AIR starting from AIR 28 for Desktop only. This API provides the functionality of selecting audio output devices. AIR app developer should build their own UI to list the available audio devices in a system and select the device for playback.

When an AIR app is launched, the audio output will play through the system default device. The user can change the audio output device. The selection is valid only for the current session of the AIR app. On-relaunch of the app, the audio will play through system default device.The developer is responsible for the storage of the user selection if it is required.

The audio device selected in one AIR application does not affect the audio from the other AIR applications or Flash Player instances.

The User Invoked Action(UIA) restriction is applicable when an external SWF/HTML which is hosted over the network is loaded by the AIR application. The UIA check implies that the audio device can be changed by user interaction only. If the externally loaded SWF/HTML tries to change the audio output device without any user invoked action, then AIR runtime throws an error "IllegalOperationError" with error code 2176.

More information about the Audio Device Manager API is available at https://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/media/AudioDeviceManager.html

Sample Snippet :

//Access system available audio device names

var status_ta:TextField = new TextField();
status_ta.width = 200;
addChild(status_ta);
var audio_device_manager:AudioDeviceManager = AudioDeviceManager.audioDeviceManager;
var audio_output_device_array:Array = audio_device_manager.deviceNames;
var selected_audio_device:String = audio_output_device_array[audio_device_manager.selectedDeviceIndex];
status_ta.text = "The default device is: "+selected_audio_device+"\n"+"\n";
status_ta.text += "You have "+audio_output_device_array.length+" device(s) available."+"\n"+"\n";
for (var i = 0; i<audio_output_device_array.length; i++) {
    status_ta.text += "["+i+"] "+audio_output_device_array[i]+"\n";
}


//Select an audio output device
var audio_device_manager:AudioDeviceManager = AudioDeviceManager.audioDeviceManager;
audio_device_manager.selectedDeviceIndex = desired_audio_output_index;


// Monitor audio output change
function audioOutputChangeHandler(evt:AudioOutputChangeEvent):void
{
    if (evt.reason == AudioOutputChangeReason.USER_SELECTION) {
        [do something]
    } else if (evt.reason == AudioOutputChangeReason.DEVICE_CHANGE) {
        [do something]
    }
}

AIR Desktop - Support for selection of GPU preference in multi-GPU system

Till AIR 27, there was no option in AIR to set the preference for use of either of the GPU types. It uses the default GPU type as set by the OS: integrated GPU on Windows and the discrete GPU on Mac OS X. 

With AIR 28, developers can set a preference for the use of the specific GPU type, in the AIR application descriptor by adding the "<gpuPreference>" element in the application descriptor as follows:

 

<application>

<gpuPreference>(discrete|integrated)</gpuPreference>

</application>

 

The AIR application developer can set the preference for the discrete GPU for better performance, or the integrated for better battery life. This feature is supported only on devices that are equipped with both an integrated GPU and a discrete GPU, and with OSes that support GPU switching functionality.

Merk:

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

Released Versions

Deliverable Released Version
Flash Player Windows for Internet Explorer - ActiveX 28.0.0.161
Flash Player Windows for Firefox - NPAPI 28.0.0.161
Flash Player Windows for Chromium - PPAPI 28.0.0.161
Flash Player Mac for Safari and Firefox - NPAPI 28.0.0.161
Flash Player Mac for Chromium - PPAPI 28.0.0.161
Flash Player Win 8 & 10 for Internet Explorer & Edge 28.0.0.161
Flash Player Mac for Google Chrome 28.0.0.161
Flash Player Windows for Google Chrome  28.0.0.161
Flash Player ChromeOS 28.0.0.161
Flash Player Linux for Google Chrome 28.0.0.161
Flash Player Linux for Chromium - PPAPI 28.0.0.161
Flash Player Linux for Firefox - NPAPI 28.0.0.161
AIR Desktop Win Runtime 28.0.0.127
AIR Desktop Mac Runtime 28.0.0.127
AIR SDK & Compiler Windows 28.0.0.125
AIR SDK & Compiler Mac 28.0.0.125
AIR SDK Windows 28.0.0.125
AIR SDK Mac 28.0.0.125

Known Issues

AIR
  • GESTURE_PAN event is not triggered on Mac.( AIR-4198492)
  • [Android] Stage shift offset error on StageText focus (AIR-4198421)
  • [Android] Camera miniature display at top-left corner when StageVideo video playback (AIR-4130641)
  • Flash Builder quits unexpectedly on High Sierra when "Export release build" is selected from the Project menu.
  • [Android] unable to load files from File.desktopDirectory on Android 7 and above (AIR-4198491)

Security Enhancements

Security Bulletin Impacted Deliverables
APSB18-03 Adobe Flash Player

Authoring Guidelines

Authoring for Flash Player 28

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

  • Download the new playerglobal.swc for Flash Player 28
  • 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 28 SDK.  To do this, unzip the AIR 28 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 Files\Adobe\Adobe Flash Builder 4.7 (64Bit)\eclipse\plugins\com.adobe.flash.compiler_4.7.0.349722\AIRSDK\
  • 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=39" to the 'Additional compiler arguments' field.
    • This ensures the outputted SWF targets SWF version 39.  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 28 build in your browser.

Authoring for AIR 28 Update to the AIR 28 namespace

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

Reporting a Bug

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!

System Requirements

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

For the latest AIR system requirements please review the document here 

Runtime Version(s) History

Release Date Runtime Version Security Enhancements
February 6, 2018 Flash Player (Win, Mac, Linux) 28.0.0.161 APSB18-03
January 9, 2018 Flash Player (Win, Mac, Linux) 28.0.0.137 APSB18-01
December 12, 2017 Flash Player (Win, Mac, Linux) 28.0.0.126
AIR Runtime 28.0.0.127
AIR SDK 28.0.0.125
APSB17-42
November 14, 2017 Flash Player (Win, Mac, Linux) 27.0.0.187 APSB17-33
October 25, 2017 Flash Player (Win, Mac, Linux) 27.0.0.183  
October 16, 2017 Flash Player (Win, Mac, Linux) 27.0.0.170 APSB17-32
October 10, 2017 Flash Player (Win, Mac, Linux) 27.0.0.159
AIR SDK Win 27.0.0.132
APSB17-31
September 12, 2017 Flash Player (Win, Mac, Linux) 27.0.0.130
AIR SDK and Runtime Win 27.0.0.124
AIR SDK and Runtime Mac 27.0.0.128
APSB17-28
August 8, 2017 Flash Player (Win, Mac, Linux) 26.0.0.151 APSB17-23
July 11, 2017 Flash Player (Win, Mac, Linux) 26.0.0.137
AIR Runtime 26.0.0.127
APSB17-21
June 16, 2017 Flash Player (Win, Mac, Linux) 26.0.0.131  
June 13, 2017 Flash Player (Win, Mac, Linux) 26.0.0.126
Flash Player (ActiveX Win 8/10) 26.0.0.120
AIR SDK and Runtime 26.0.0.118
APSB17-17
May 9, 2017 Flash Player (Win, Mac, Linux) 25.0.0.171 APSB17-15
April 20, 2017 Flash Player (Mac) 25.0.0.163  
April 11, 2017 Flash Player (Win, Mac, Linux) 25.0.0.148 APSB17-10
March 14, 2017 Flash Player (Win, Mac, Linux) 25.0.0.127
AIR SDK and Runtime 25.0.0.134
APSB17-07
February 14, 2017 Flash Player (Win, Mac, Linux) 24.0.0.221 APSB17-04
January 10, 2017 Flash Player (Win, Mac, Linux) 24.0.0.194 APSB17-02
December 13, 2016 Flash Player (Win, Mac, Linux) 24.0.0.186
AIR SDK and Runtime 24.0.0.180
APSB16-39
November 8, 2016 Flash Player (Win, Mac, Linux) 23.0.0.207
Flash Player (NPAPI Linux) 11.2.202.644
APSB16-37
October 26, 2016 Flash Player (Win, Mac, Linux) 23.0.0.205
Flash Player (NPAPI Linux) 11.2.202.643
APSB16-36
October 11, 2016 Flash Player (Win, Mac, Linux) 23.0.0.185
Flash Player (NPAPI Linux) 11.2.202.637
Flash Player (ESR) 18.0.0.382
APSB16-32
September 13, 2016 Flash Player (Win, Mac, Linux) 23.0.0.162
Flash Player (NPAPI Linux) 11.2.202.635
Flash Player (ESR) 18.0.0.375
AIR SDK and Runtime 23.0.0.257
APSB16-29
APSB16-31
July 14, 2016 Flash Player (Win ActiveX) 22.0.0.210  
July 12, 2016 Flash Player (Win, Mac, Linux) 22.0.0.209
Flash Player (NPAPI Linux) 11.2.202.632
Flash Player (ESR) 18.0.0.366
APSB16-25
June 16, 2016 Flash Player (Win, Mac, Linux) 22.0.0.185
Flash Player (NPAPI Linux) 11.2.202.626
Flash Player (ESR) 18.0.0.358
AIR SDK and Runtime 22.0.0.153
APSB16-18
APSB16-23
May 12, 2016 Flash Player (Win, Mac, Linux) 21.0.0.242
Flash Player (NPAPI Linux) 11.2.202.621
Flash Player (ESR) 18.0.0.352
AIR SDK and Runtime 21.0.0.215
APSB16-15
April 21, 2016 Flash Player (Mac NPAPI) 21.0.0.226  
April 12, 2016 AIR SDK and Runtime 21.0.0.198  
April 8, 2016 Flash Player (Google Chrome) 21.0.0.216  
April 7, 2016 Flash Player (Win, Mac, Linux) 21.0.0.213
Flash Player (NPAPI Linux) 11.2.202.616
Flash Player (ESR) 18.0.0.343
APSB16-10
March 23, 2016 Flash Player (Win, Mac, Linux) 21.0.0.197  
March 10, 2016 Flash Player (Win, Mac, Linux) 21.0.0.182
Flash Player (NPAPI Linux) 11.2.202.577
Flash Player (ESR) 18.0.0.333
AIR SDK and Runtime 21.0.0.176
APSB16-08
February 9, 2016 Flash Player (Win, Mac, Linux) 20.0.0.306
Flash Player (NPAPI Linux) 11.2.202.569
Flash Player (ESR) 18.0.0.329
AIR SDK and Runtime 20.0.0.260
APSB16-04
January 19, 2016 Flash Player (Win, Mac, Linux) 20.0.0.286  
January 1, 2015 Flash Player ActiveX (Win 7) 20.0.0.270  
December 28, 2015 Flash Player (Win, Mac, Linux) 20.0.0.267
Flash Player (NPAPI Linux) 11.2.202.559
Flash Player (ESR) 18.0.0.324
AIR SDK and Runtime 20.0.0.233
APSB16-01
December 8, 2015 Flash Player (Win, Mac, Linux) 20.0.0.228
Flash Player (NPAPI Win & Mac) 20.0.0.235
Flash Player (NPAPI Linux) 11.2.202.554
Flash Player (ESR) 18.0.0.268
AIR SDK and Runtime 20.0.0.204
APSB15-32
November 10, 2015 Flash Player (Win, Mac, Linux) 19.0.0.245
Flash Player (NPAPI Linux) 11.2.202.548
Flash Player (ESR) 18.0.0.261
AIR SDK and Runtime 19.0.0.241
APSB15-28
October 16, 2015 Flash Player (Win, Mac, Linux) 19.0.0.226
Flash Player (PPAPI ChromeOS) 19.0.0.225
Flash Player (NPAPI Linux) 11.2.202.540
Flash Player (ESR) 18.0.0.255
APSB15-27
October 13, 2015 Flash Player (Win & Mac) 19.0.0.207
Flash Player (PPAPI Linux) 19.0.0.207
Flash Player (NPAPI Linux) 11.2.202.535
Flash Player (ESR) 18.0.0.252
AIR SDK and Runtime 19.0.0.190
APSB15-25
September 21, 2015 Flash Player (Win & Mac) 19.0.0.185
Flash Player (PPAPI Linux) 19.0.0.185
Flash Player (NPAPI Linux) 11.2.202.521
Flash Player (ESR) 18.0.0.241
AIR SDK and Runtime 19.0.0.190
APSB15-23
August 11, 2015 Flash Player (Win & Mac) 18.0.0.232
Flash Player (PPAPI Linux) 18.0.0.233
Flash Player (Linux) 11.2.202.498
Flash Player (ESR) 18.0.0.228
AIR SDK and Runtime 18.0.0.199
APSB15-19
July 16, 2015 Flash Player (Linux NPAPI) 11.2.202.491
Flash Player (ESR) 13.0.0.309
APSB15-18
July 14, 2015 Flash Player 18.0.0.209
APSB15-18
July 8, 2015 Flash Player 18.0.0.203
Flash Player (PPAPI Linux) 18.0.0.204
Flash Player (ESR) 13.0.0.302
Flash Player (Linux NPAPI) 11.2.202.481
Flash Player 17.0.0.191
AIR SDK and Runtime 18.0.0.180
APSB15-16
June 23, 2015 Flash Player 18.0.0.194
Flash Player (ESR) 13.0.0.296
Flash Player (Linux NPAPI) 11.2.202.468
Flash Player 17.0.0.190
APSB15-14
June 9, 2015 Flash Player (Win & Mac) 18.0.0.160
Flash Player PPAPI (Mac) 18.0.0.161
Flash Player (Linux) 11.2.202.466
Flash Player (ESR) 13.0.0.292
AIR SDK and Runtime (Win) 18.0.0.144
AIR SDK and Runtime (Mac) 18.0.0.143
APSB15-11
May 12, 2015 Flash Player (Win & Mac) 17.0.0.188
Flash Player (Linux) 11.2.202.460
Flash Player (ESR) 13.0.0.289
AIR SDK and Runtime 17.0.0.172
APSB15-09
April 14, 2015 Flash Player (Win & Mac) 17.0.0.169
Flash Player (Linux) 11.2.202.457
Flash Player (ESR) 13.0.0.281
AIR SDK and Runtime 17.0.0.144
APSB15-06
March 12, 2015 Flash Player (Win & Mac) 17.0.0.134
Flash Player (Linux) 11.2.202.451
Flash Player (ESR) 13.0.0.277
AIR SDK and Runtime 17.0.0.124
APSB15-05
February 12, 2015 AIR Desktop Runtime (Win) 16.0.0.273
AIR SDK (Win & Mac) 16.0.0.292
 
February 5, 2015 Flash Player (Win & Mac) 16.0.0.305
Flash Player (Linux) 11.2.202.442
Flash Player ESR (Win & Mac) 13.0.0.269
APSB15-04
January 27, 2015 Flash Player (Win & Mac) 16.0.0.296
Flash Player (Linux) 11.2.202.440
Flash Player ESR (Win & Mac) 13.0.0.264
APSB15-03
January 22, 2015 Flash Player (Win & Mac) 16.0.0.287
Flash Player (Linux) 11.2.202.438
Flash Player ESR (Win & Mac) 13.0.0.262
APSB15-02
Janurary 13, 2015 Flash Player (Win & Mac) 16.0.0.257
Flash Player (Linux) 11.2.202.429
Flash Player ESR (Win & Mac) 13.0.0.260
AIR Android 16.0.0.272
AIR Desktop Runtime 16.0.0.245
AIR SDK 16.0.0.272
APSB15-01
December 9th, 2014 Flash Player (Win & Mac) 16.0.0.235
Flash Player (Linux) 11.2.202.425
Flash Player ESR (Win & Mac) 13.0.0.259
APSB14-27
December 9th, 2014 Flash Player (Win & Mac) 15.0.0.246 APSB14-27
November 11th, 2014 Flash Player (Win & Mac) 15.0.0.223
Flash Player (Linux) 11.2.202.418
Flash Player ESR (Win & Mac) 13.0.0.252
AIR Android 15.0.0.356
AIR Desktop & SDK 15.0.0.356
APSB14-24
September 23rd, 2014 Flash Player (Windows ActiveX) 15.0.0.167 APSB14-22
September 9th, 2014 Flash Player (Win & Mac) 15.0.0.152
Flash Player (Linux) 11.2.202.406
Flash Player ESR (Win & Mac) 13.0.0.244
AIR Android 15.0.0.252
AIR Desktop & SDK 15.0.0.249
APSB14-21
August 12th, 2014 Flash Player (ActiveX, Mac NPAPI) 14.0.0.176
Flash Player (Win NPAPI) 14.0.0.179
Flash Player (PPAPI) 14.0.0.177
AIR Android 14.0.0.179
AIR Desktop & SDK 14.0.0.178
APSB14-18
July 8th, 2014 Flash Player Desktop (Win & Mac) 14.0.0.145
Flash Player Desktop (Linux) 11.2.202.394
Flash Player ESR (Win & Mac) 13.0.0.231
AIR (SDK & Android Runtime) 14.0.0.137
APSB14-17
June 10th, 2014 Flash Player Desktop (Win & Mac) 14.0.0.125
Flash Player Desktop (Linux) 11.2.202.378
Flash Player ESR (Mac & Win) 13.0.0.223
AIR (SDK & Runtime) 14.0.0.110
APSB14-16
May 13th, 2014 Flash Player Desktop (Win & Mac) 13.0.0.214
Flash Player Desktop (Linux) 11.2.202.359
Flash Player Enterprise (Mac & Win) 13.0.0.214
AIR (SDK & Runtime) 13.0.0.111
APSB14-14

Dette produktet er lisensiert i henhold til Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Innlegg på Twitter™ og Facebook dekkes ikke av Creative Commons-vilkår.

Juridiske merknader   |   Regler for personvern på nettet