In today's release, we've updated Flash Player with important functional and critical security fixes.  Current Flash Player customers who have selected the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to the latest version of Flash Player over the next 24 hours. The most recent Flash Player security bulletin can be found here: Security Bulletin (APSB18-08) For complete information please see our release notes. Fixed Issues [Mac]RTMPS Error NetConnection.Connect.CertificatePrincipalMismatch (FP-4198784) [Edge] FP settings panel 'close' button stops responding on zoom. Multiple security and functional fixes Current Flash Player users who have enrolled in the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to Flash Player 29 over the next 24 hours. Users who have selected "Notify me to install updates" will receive an update notification dialog within 7 days from today.  Please note that Windows users will need to restart their system or log out and in to activate the update notification dialog. Customers using Google Chrome will receive updates through the Google update mechanisms.  Customers using Internet Explorer or Microsoft Edge on Windows 8.1 and Windows 10 will receive the update through Windows Update. If you would like to install the update immediately, please use one of the links below: Flash Player 29 Windows for Internet Explorer - ActiveX:  29.0.0.140 Flash Player 29 Windows for Firefox and other Netscape Compatible Browsers - NPAPI: 29.0.0.140 Flash Player 29 Windows for Opera and Chromium Based Browsers - PPAPI: 29.0.0.140 Flash Player 29 Windows for Google Chrome - PPAPI: 29.0.0.140 Flash Player 29 for Internet Explorer on Windows 8.1 (64-bit machine): 29.0.0.140 Flash Player 29 for Internet Explorer on Windows 8.1 (32-bit machine): 29.0.0.140 Flash Player 29 Windows for Internet Explorer and Edge on Windows 10 - ActiveX: 29.0.0.140 Flash Player 29 Mac for Safari, Firefox and other Netscape Compatible Browsers - NPAPI: 29.0.0.140 Flash Player 29 Mac for Opera and Chromium Based Browsers - PPAPI: 29.0.0.140 Flash Player 29 Mac for Google Chrome - PPAPI: 29.0.0.140 Flash Player 29 desktop for Linux (NPAPI): 29.0.0.140 Flash Player 29 desktop for Linux Chromium (PPAPI): 29.0.0.140 If you encounter a problem with broken or missing links, please clear your browser cache and try again.  If the problem persists, please create a new post in our forum or send email to ccampbel@adobe.com or mkumarjh@adobe.com. ... View more

Today we're pleased to announce that the next version of AIR is available for immediate download.  This release of AIR provides bug fixes, security updates, and new features. Below are some of the key features and benefits of AIR 29.  Please see our release notes for full details. 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 today, 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. New Features New SoftKeyboard Types for Android & iOS Starting AIR 29, TextField and StageText enable developers to set two more types of soft keyboard. DECIMAL PHONE Use swf-version 40 or greater and namespace 29.0 or greater to access these newly added keypads.Developers can set a softKeyboard property based on the input expected from the user. For example, if the phone input is expected, a device can use SoftKeyboardType.PHONE to display only phone numbers on the soft keyboard. Valid values are defined as constants in the SoftKeyboardType class: Sample Usage: var tfKeyBoard:TextField=new TextField();  keyBoard.softKeyboard=SoftKeyboardType.DECIMAL; //Setting SoftKeyboard type as DECIMAL    OR    var stKeyBoard:StageText = new StageText();  stKeyBoard.softKeyboardType=SoftKeyboardType.PHONE; //Setting SoftKeyboard type as PHONE  Geolocation Permission on iOS Starting AIR 29, developers requesting Geolocation permission on iOS in their applications will have an option to request for WHEN_IN_USE or ALWAYS permission through a new property locationAlwaysUsePermission. The default value of this property is false. Sample Usage: private var geo:Geolocation = new Geolocation(); geo.requestPermission(); //this would request for WHEN_IN_USE permission OR private var geo:Geolocation = new Geolocation(); geo.locationAlwaysUsePermission= true ; //applicable for iOS11 geo.requestPermission(); //this would request for WHEN_IN_USE and ALWAYS permission Note: 1. On iOS 11 and later if you initially request the WHEN_IN_USE permission, you can request the ALWAYS permission at a later time. The OS allows you to do this just once and any subsequent calls of requestPermission() are ignored by the OS. 2. On iOS 10, the OS allows you to request for permission just once. The requested permission WHEN_IN_USE/ALWAYS depends on the cocoa key added in the application descriptor. Hence, the property locationAlwaysUsePermission does not apply to iOS 10 and below. 3. Developers need to add cocoa keys in their application descriptor as per the level of authorization required by their application. For more details please see https://developer.apple.com/documentation/corelocation/choosing_the_authorization_level_for_location_services/requesting_always_authorization Media AutoPlay for Android and iOS With AIR 29, we have made some changes to the feature "Media AutoPlay for iOS & Android" introduced in AIR 21. Now, a new argument has been added to StageWebView constructor mediaPlaybackRequiresUserAction with a default value true. Setting this argument to false will ensure autoplay of the media inside StageWebView. public function StageWebView(useNative: Boolean = false , mediaPlaybackRequiresUserAction: Boolean = true ) For iOS, setting mediaPlaybackRequiresUserAction property after creating StageWebView will be a no-op, and developers can only set media autoplay through StageWebView constructor. For Android, developers can set media autoplay in, either way, using the property mediaPlaybackRequiresUserAction or through the constructor argument. Android SDK Upgrade With AIR 29, Android SDK has been upgraded in the AIR Runtime. Here is the list of version numbers of the tools upgraded in AIR 29. 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. Android Version 8.1 SDK Platform 27 SDK Tool 26.1.1 Android Build Tool 27.0.3 Platform Tool 27.0.1 Android Support Repository 47.0.0 Android Google Repository 58 LLDB 3.0 Android Emulator 27.0.5 Gradle plugin version for Android 3.0.1 Multidex jar 1.0.2 Combined Windows 32-bit and 64-bit AIR SDK With AIR 29 onwards, a combined AIR SDK for packaging 32-bit and 64-bit captive AIR applications is now available for Windows. Deciding the architecture of AIR applications The process of packaging 32-bit and 64-bit using the combined AIR SDK is different for Adobe Flash Builder and Adobe Animate/adt Packaging using Adobe Animate and adt: With Adobe Animate and adt this process is done by adding an extra tag <architecture> in the application XML. The value of this tag could be either “32” for packaging 32-bit captive AIR applications and “64” for packaging 64-bit captive AIR applications. The tag <architecture> must be added under <application> tag. Here is a sample app-xml: <? xml version = "1.0" encoding = "utf-8" standalone = "no" ?>     < application xmlns = "http://ns.adobe.com/air/application/29.0" >         < id >Sample</ id >         < filename >Sample</ filename >         < architecture >64</ architecture >         < name >Sample</ name >         < versionNumber >0.0.0</ versionNumber >         < initialWindow >             < content >Sample.swf</ content >             < autoOrients >false</ autoOrients >             < fullScreen >false</ fullScreen >             < visible >true</ visible >         </ initialWindow >     </ application > Packaging using Adobe Flash Builder: With Adobe Flash builder this process can be accomplished by adding a Windows environment variable AIR_WIN_ARCH before launching the Adobe Flash Builder. The value of this variable could be 32 and 64 for packaging 32-bit captive AIR applications and 64-bit captive AIR applications respectively. Setting the tag <architecture> will have no effect when the application is packaged using Adobe Flash Builder. The decision will be completely dependent only on the environment variable’s value. The packaging of shared and native AIR application will not be affected by any of the above-mentioned methods. They will continue to be supported as 32-bit applications on Windows. Also, packaging AIR applications on Mac won’t be affected. Enhanced Profile on AIR Desktop The Enhanced profile will be available on AIR for Windows 8.1+ and Mac OS 10.9+ from AIR 29. This profile has been made available on mobile from AIR 26.  It can be used in both requestContext3D and requestContext3DMatchingProfiles methods.  AGAL4 can be used with the Enhanced profile. AGAL4 introduces a new opcode “tld” and new Vertex Sampler register “vs” for fetching texture in a vertex shader.  ‘tld’ requires a level of detail ( LOD ) value for parameter since GPU does not support the automatic calculation of LOD in the vertex shader. Latest version of AGALMiniAssembler is available here: https://github.com/adobe-flash/graphicscorelib/pull/14/commits/a20d4773459b01e86acceac45240a2b4e88f67e3 Vertex Texture Fetch on AIR Desktop With the introduction of new Stage3D profile i.e. ‘ENHANCED’ on the desktop, Vertex Texture Fetch is now available on AIR Desktop too. Vertex Texture Fetch was made available on mobile from AIR 26. It will be available on Desktop AIR 29 (SWF version 40) onwards. The feature will be supported on Windows 8.1+ and Mac OS 10.9+. The feature is dependent on the availability of Enhanced Profile and hence, it will not be supported on Windows 7. Texture Data will be available in Vertex Shader using AGAL4 and Enhanced profile. AGAL 4 introduces a new opcode “tld” and new Vertex Sampler register “vs” for fetching texture in the vertex shader. ‘tld’ is similar to 'tex' opcode used in the fragment shader. But unlike ‘tex’ opcode, ‘tld’ requires a level of detail ( LOD ) value as a parameter since GPU does not support the automatic calculation of LOD in the vertex shader. tld usage: tld dst, src, sampler dst: a destination register for the sampler texture pixel src: a register containing texture coordinate where the pixel is sampled and containing a level of detail indication as an index of mipmap to use. The XY components of the src register: a texture coordinate where a texture pixel is sampled. The z component will be used for indicating the side of the cube map texture if the vertex texture is a cube map. The w component of the src register: an index of mipmap to use, with a value range from 0 to n-1 where n is the total number of the mipmaps. The zero index indicates a mipmap in the highest resolution. The fractional part of src.w is how much a selected mipmap would be interpolated with the next level of the mipmap in lower resolution based on the mipmap filter (mipnearest or miplinear) passed in the shader or set from the setSamplerStateAt() API. Mipnearest uses nearest-neighbor mipmap, while miplinear uses linearly filtered mipmapping. vertex sampler ‘vs’ tld vt0, va0, vs0<2d,linear,miplinear> The above example code fetches texture pixels from the texture bound to vertex sampler 0 (vs0) to a vertex temporary register 0 (vt0) with a texture coordinate provided in a vertex attribute register 0 (va0) and a sampler state(< 2d, linear, miplinear >) provided in the vertex shader. The LOD value is provided in va0.w in the example. A total number of vertex samplers available is 4. The sum of vertex and fragment samplers is restricted to 16. Please note that tld opcode cannot be used inside fragment sampler. To provide a texture for a vertex sampler in the vertex shader, developers must use existing ActionScript API, SetTextureAt(). SetTextureAT(0, texture); The above example code binds 'texture' to the vertex sampler 0 (vs0). Note that this call would set up 'texture' to the fragment sampler in the same index, which is the fragment sampler 0 (fs0) if there is access to fs0 in the fragment shader. A sampler state of the vertex sampler in the vertex shader code could be overridden with the existing AS API, SetSamplerStateAt: SetSamplerStateAt(0, Context3DWrapMode.CLAMP, Context3DTextureFilter.LINEAR, Context3DMipFilter.MIPNEAREST ); Like the SetTextureAt API, the above call would also set up the state of the fragment sampler in the same index, which is the fragment sampler 0 (fs0), if fs0 is used in the fragment shader. Please note, Anisotropic Filtering is not available for texture sampling used in vertex shaders. Vertex Texture Fetch feature is useful for a number of effects like displacement mapping, water simulation, and explosion mapping etc. Application of HIDPI Scaling to non-client areas Support for HiDPI displays on Windows was introduced in AIR version 23. The feature allowed display of AIR contents to render higher quality on HiDPI displays. The feature 'Application of HIDPI Scaling to non-client areas' is an extension to the earlier support for HiDPI scaling, wherein scaling of non-client areas, upon the dynamic change in the DPI value would be supported on AIR Windows. The feature would cover the scaling of the dialog boxes, file browsers and ‘non-client area’ UI components such as title bar, native menu and Windows icons. The feature will be available from AIR 29 onwards and Windows 10 (Redstone 1) Version 1607 onwards. AIR Desktop - Ability to disable/enable vsync on the fly Till AIR 28, frame buffer rendering rate of the AIR Runtime was synchronized to the display device refresh rate. We have provided an enhancement in AIR 29 where a user will have an extra ability to sync or a-sync the display device rate. The synchronization feature can be toggled with the help of a property added to a stage variable “vsyncEnabled”. The “vsyncEnabled” variable is available to toggle between true and false, if and only if an event “VsyncStateChangeAvailabilityEvent”  returns true. On windows 7 machine DisplayContext object, Event.CONTEXT3D_CREATE will be triggered again whenever the vsyncEnabled value is set as true and flickering may be observed.This phenomenon will not be reflected on Windows 8 and above and on Mac machines. AIR Desktop-Increase GPU memory Limits Until AIR 28, maximum GPU memory provided for uploading the Normal and Rectangular textures was 512 MB. With AIR 29 beta, we have enhanced the GPU memory limits to 2048MB. These new limits will be available with the Stage3D profile “Standard_Extended” and "Enhanced". For other profiles, maximum GPU limit will be 512MB. This feature is AIR 64 bit only and will be available for Normal and Rectangular textures. For Cube texture, memory limits will be same as before i.e. 256 MB. AIR Desktop-Increase in Texture Limit (Beta Only) Till AIR 28, maximum texture size supported by AIR is 4096x4096. In AIR 29 (SWF version 40), we have increased the texture limit to 8192x8192 pixels. A new read-only property Context3D::supports8kTexture has been introduced which returns true only if the 8k texture is supported by the hardware. This feature only supports the rendering of Normal and Rectangular textures. Textures such as Cube, Video, Compressed, and Compressed_Alpha will not be supported. The feature is available in AIR 64 for Mac, Windows 8.1 and above. Since 8K textures are quite heavy, it is recommended to upload the textures asynchronously. Fixed Issues AIR apps quit unexpectedly when byte array is attached to domainMemory(AIR-4198585) Flash Builder quits unexpectedly on High Sierra when "Export release build" is selected from the Project menu (Updated BLOG) clipboard.dataForFormat returns null for Custom data in the Clipboard(AIR-4198553). Wireframe feature not working on Directx11(AIR-4198597) Screen turns half black when iOS goes into standby and user resume again for IOS 10+ (AIR-4198539) Bluetooth Headset not working with microphone.getEnhancedMicrophone() on iOS (AIR-4198549) [Android]Incomplete textures are rendered when uploading large textures.(AIR-4198475) Unexpected margin at the top of StageWebView on iOS 11 (AIR-4198537) InvokeEvent.arguments is empty on Android (AIR-4198552) Delay in dispatching TOUCH events on device borders on iOS 11 (AIR-4198551) StageWebView does not load nor display local HTML content (AIR-4198420) Status bar appears when app is in fullscreen and showing soft keyboard on Samsung devices (4189175) Audio stops playing on interruption when SoundMixer.audioPlaybackMode = AudioPlaybackMode.VOICE and SoundMixer.useSpeakerphoneForVoice = false (4189377) NetworkInfo.isSupported returns TRUE on Android even when permissions are missing in application descriptor (AIR-4198485) Stage shift offset error on StageText focus when status bar is hidden on Samsung S8 (AIR-4198421) [iOS] iOS StageWebView viewPort incorrect (y axis shift) (AIR-4198583) Known Issues [Mac]GESTURE_PAN event is not fired.(AIR-4198492) Asynchronous texture upload fails after uploading 5000 texture(AIR-4198527) Download Locations: AIR runtime for Windows: 29.0.0.112 Runtime Download AIR runtime for Macintosh: 29.0.0.112 Runtime Download AIR SDK & Compiler for Windows: 29.0.0.112 SDK & Compiler Download AIR SDK & Compiler for Macintosh: 29.0.0.112 SDK & Compiler Download Note: To provide all the all the necessary tools for our developers in one place and avoid having to download multiple components, we are packaging Adobe AIR 29 SDK and ActionScript Compiler 2.0 in a single SDK called “Adobe AIR 29 SDK & Compiler”. AIR SDK (Compatible with Flex) for Windows: 29.0.0.112 SDK Windows Download AIR SDK (Compatible with Flex) for Macintosh: 29.0.0.112 SDK Macintosh Download Previous versions of the AIR runtime and SDK can be found on the Archived AIR SDK and Runtimes page ... View more

In today's release, we've updated Flash Player with important functional and critical security fixes.  Current Flash Player customers who have selected the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to the latest version of Flash Player over the next 24 hours. The most recent Flash Player security bulletin can be found here: Security Bulletin (APSB18-05) For complete information please see our release notes. Fixed Issues Flash Player settings panel become unresponsive when hardware acceleration is turned off on Firefox. Flash Player quit unexpectedly when "by.blooddy.crypto.Base64" class try to decode BASE64.(FP-4198772) Flash Player Protected mode + Async drawing on Firefox causes the font color to be inverted SecureSocket and RTMPS with OpenSSL is not sending "server_name" SNI headers. Flash Player will not connect via SecureSocket to a server running only TLS1.2. Assorted security and functional fixes Current Flash Player users who have enrolled in the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to Flash Player 29 over the next 24 hours. Users who have selected "Notify me to install updates" will receive an update notification dialog within 7 days from today.  Please note that Windows users will need to restart their system or log out and in to activate the update notification dialog. Customers using Google Chrome will receive updates through the Google update mechanisms.  Customers using Internet Explorer or Microsoft Edge on Windows 8.1 and Windows 10 will receive the update through Windows Update. If you would like to install the update immediately, please use one of the links below: Flash Player 29 Windows for Internet Explorer - ActiveX:  29.0.0.113 Flash Player 29 Windows for Firefox and other Netscape Compatible Browsers - NPAPI: 29.0.0.113 Flash Player 29 Windows for Opera and Chromium Based Browsers - PPAPI: 29.0.0.113 Flash Player 29 Windows for Google Chrome - PPAPI: 29.0.0.113 Flash Player 29 for Internet Explorer on Windows 8.1 (64-bit machine): 29.0.0.113 Flash Player 29 for Internet Explorer on Windows 8.1 (32-bit machine): 29.0.0.113 Flash Player 29 Windows for Internet Explorer and Edge on Windows 10 - ActiveX: 29.0.0.113 Flash Player 29 Mac for Safari, Firefox and other Netscape Compatible Browsers - NPAPI: 29.0.0.113 Flash Player 29 Mac for Opera and Chromium Based Browsers - PPAPI: 29.0.0.113 Flash Player 29 Mac for Google Chrome - PPAPI: 29.0.0.113 Flash Player 29 desktop for Linux (NPAPI): 29.0.0.113 Flash Player 29 desktop for Linux Chromium (PPAPI): 29.0.0.113 If you encounter a problem with broken or missing links, please clear your browser cache and try again.  If the problem persists, please create a new post in our forum or send email to ccampbel@adobe.com or mkumarjh@adobe.com. ... View more

In today's release, we've updated Flash Player with important functional and critical security fixes.  Current Flash Player customers who have selected the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to the latest version of Flash Player over the next 24 hours. The most recent Flash Player security bulletin can be found here: Security Bulletin (APSB18-03) For complete information please see our release notes. Fixed Issues [Mac] Recorder will be stuck with message "Uploading...X%" while uploading the video using RTMPS protocol. (FP-4198740) Assorted security and functional fixes Current Flash Player users who have enrolled in the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to Flash Player 28 over the next 24 hours. Users who have selected "Notify me to install updates" will receive an update notification dialog within 7 days from today.  Please note that Windows users will need to restart their system or log out and in to activate the update notification dialog. Customers using Google Chrome will receive updates through the Google update mechanisms.  Customers using Internet Explorer or Microsoft Edge on Windows 8.1 and Windows 10 will receive the update through Windows Update. If you would like to install the update immediately, please use one of the links below: Flash Player 28 Windows for Internet Explorer - ActiveX:  28.0.0.161 Flash Player 28 Windows for Firefox and other Netscape Compatible Browsers - NPAPI: 28.0.0.161 Flash Player 28 Windows for Opera and Chromium Based Browsers - PPAPI: 28.0.0.161 Flash Player 28 Windows for Google Chrome - PPAPI: 28.0.0.161 Flash Player 28 for Internet Explorer on Windows 8.1 (64-bit machine): 28.0.0.161 Flash Player 28 for Internet Explorer on Windows 8.1 (32-bit machine): 28.0.0.161 Flash Player 28 Windows for Internet Explorer and Edge on Windows 10 - ActiveX: 28.0.0.161 Flash Player 28 Mac for Safari, Firefox and other Netscape Compatible Browsers - NPAPI: 28.0.0.161 Flash Player 28 Mac for Opera and Chromium Based Browsers - PPAPI: 28.0.0.161 Flash Player 28 Mac for Google Chrome - PPAPI: 28.0.0.161 Flash Player 28 desktop for Linux (NPAPI): 28.0.0.161 Flash Player 28 desktop for Linux Chromium (PPAPI): 28.0.0.161 If you encounter a problem with broken or missing links, please clear your browser cache and try again.  If the problem persists, please create a new post in our forum or send email to ccampbel@adobe.com or mkumarjh@adobe.com. ... View more

In today's scheduled release, we've updated Flash Player with important functional and security fixes.  Current Flash Player customers who have selected the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to the latest version of Flash Player over the next 24 hours. The most recent Flash Player security bulletin can be found here: Security Bulletin (APSB18-01) Fixed Issues Assorted security and functional fixes Current Flash Player users who have enrolled in the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to Flash Player 28 over the next 24 hours. Users who have selected "Notify me to install updates" will receive an update notification dialog within 7 days from today.  Please note that Windows users will need to restart their system or log out and in to activate the update notification dialog. Customers using Google Chrome will receive updates through the Google update mechanisms.  Customers using Internet Explorer or Microsoft Edge on Windows 8.1 and Windows 10 will receive the update through Windows Update. If you would like to install the update immediately, please use one of the links below: Flash Player 28 Windows for Internet Explorer - ActiveX:  28.0.0.137 Flash Player 28 Windows for Firefox and other Netscape Compatible Browsers - NPAPI: 28.0.0.137 Flash Player 28 Windows for Opera and Chromium Based Browsers - PPAPI: 28.0.0.137 Flash Player 28 Windows for Google Chrome - PPAPI: 28.0.0.137 Flash Player 28 for Internet Explorer on Windows 8.1 (64-bit machine): 28.0.0.137 Flash Player 28 for Internet Explorer on Windows 8.1 (32-bit machine): 28.0.0.137 Flash Player 28 Windows for Internet Explorer and Edge on Windows 10 - ActiveX: 28.0.0.137 Flash Player 28 Mac for Safari, Firefox and other Netscape Compatible Browsers - NPAPI: 28.0.0.137 Flash Player 28 Mac for Opera and Chromium Based Browsers - PPAPI: 28.0.0.137 Flash Player 28 Mac for Google Chrome - PPAPI: 28.0.0.137 Flash Player 28 desktop for Linux (NPAPI): 28.0.0.137 Flash Player 28 desktop for Linux Chromium (PPAPI): 28.0.0.137 If you encounter a problem with broken or missing links, please clear your browser cache and try again.  If the problem persists, please create a new post in our forum or send email to ccampbel@adobe.com or mkumarjh@adobe.com. ... View more

Today we're pleased to announce that the next version of AIR is available for immediate download.  This release of AIR provides bug fixes, security updates, and new features. Below are some of the key features and benefits of AIR 28.  Please see our release notes for full details. 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. 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. Select File -> New Project -> Single View App (iOS). Fill Product Name, Organization Name and Organization Identifier (no specific names required) Save the project Click Assets.xcassets -> AppIcon -> Drag and drop App store icon of size 1024 * 1024 (1024pt, 1x) Drag and drop iPad App icon of size 76x76 (76pt, 1x) & 152x152 (76pt, 2x) Drag and drop iPad Pro App icon of size 167x167 (83.5pt, 2x) Drag and drop iPhone App icon of size 120x120 (60pt, 2x) Drag and drop iPhone App icon of size 180x180 (60pt, 3x) In the drop-down select Generic iOS Device as the build target Build the project ( Product -> Build) Right-click on your ‘.app’ -> Show in finder Right-click on your ‘.app’ -> Show package contents 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+ "\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. Fixed Issues 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) Known Issues 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) Download Locations: AIR runtime for Windows: 28.0.0.124 Runtime Download AIR runtime for Macintosh: 28.0.0.128 Runtime Download AIR SDK & Compiler for Windows: 28.0.0.124 SDK & Compiler Download AIR SDK & Compiler for Macintosh: 28.0.0.128 SDK & Compiler Download Note: To provide all the all the necessary tools for our developers in one place and avoid having to download multiple components, we are packaging Adobe AIR 27 SDK and ActionScript Compiler 2.0 in a single SDK called “Adobe AIR 27 SDK & Compiler”. AIR SDK (Compatible with Flex) for Windows: 28.0.0.124 SDK Windows Download AIR SDK (Compatible with Flex) for Macintosh: 28.0.0.128 SDK Macintosh Download Previous versions of the AIR runtime and SDK can be found on the Archived AIR SDK and Runtimes page ... View more

In today's scheduled release, we've updated Flash Player with important functional and security fixes.  Current Flash Player customers who have selected the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to the latest version of Flash Player over the next 24 hours. The most recent Flash Player security bulletin can be found here: Security Bulletin (APSB17-42) Fixed Issues [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 Current Flash Player users who have enrolled in the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to Flash Player 28 over the next 24 hours. Users who have selected "Notify me to install updates" will receive an update notification dialog within 7 days from today.  Please note that Windows users will need to restart their system or log out and in to activate the update notification dialog. Customers using Google Chrome will receive updates through the Google update mechanisms.  Customers using Internet Explorer or Microsoft Edge on Windows 8.1 and Windows 10 will receive the update through Windows Update. If you would like to install the update immediately, please use one of the links below: Flash Player 28 Windows for Internet Explorer - ActiveX:  28.0.0.126 Flash Player 28 Windows for Firefox and other Netscape Compatible Browsers - NPAPI: 28.0.0.126 Flash Player 28 Windows for Opera and Chromium Based Browsers - PPAPI: 28.0.0.126 Flash Player 28 Windows for Google Chrome - PPAPI: 28.0.0.126 Flash Player 28 for Internet Explorer on Windows 8.1 (64-bit machine): 28.0.0.126 Flash Player 28 for Internet Explorer on Windows 8.1 (32-bit machine): 28.0.0.126 Flash Player 28 Windows for Internet Explorer and Edge on Windows 10 - ActiveX: 28.0.0.126 Flash Player 28 Mac for Safari, Firefox and other Netscape Compatible Browsers - NPAPI: 28.0.0.126 Flash Player 28 Mac for Opera and Chromium Based Browsers - PPAPI: 28.0.0.126 Flash Player 28 Mac for Google Chrome - PPAPI: 28.0.0.126 Flash Player 28 desktop for Linux (NPAPI): 28.0.0.126 Flash Player 28 desktop for Linux Chromium (PPAPI): 28.0.0.126 If you encounter a problem with broken or missing links, please clear your browser cache and try again.  If the problem persists, please create a new post in our forum or send email to ccampbel@adobe.com or mkumarjh@adobe.com. ... View more

In today's scheduled release, we've updated Flash Player with important functional and security fixes.  Current Flash Player customers who have selected the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to the latest version of Flash Player over the next 24 hours. The most recent Flash Player security bulletin can be found here: Security Bulletin (APSB17-33) Features for Flash Player 27: Support ActionScript API for Audio Device Manager With the release of Flash Player 27, developers can now select the audio output from ActionScript using the new ActionScript API - “AudioDeviceManager”.  It is in sync with Flash Player's audio output settings. A UIA (User Invoked Action) restriction is applied to this API keeping in view user privacy concerns.  The API can only be invoked by a user invoked action.  If it is not invoked by user action, Flash Player throws a runtime error "IllegalOperationError" with error code 2176. Use the AudioDeviceManager class to list down the audio output devices attached to a system using the property, deviceNames().  This returns an array of the attached devices.  The index of the selected device from that array can then be retrieved using the selectedDeviceIndex() property.  A new event introduced with this API, named AudioOutputChangeEvent.AUDIO_OUTPUT_CHANGE is dispatched to ActionScript listeners when the audio output changes.  It is dispatched when the user selects a different audio device from Flash Player's setting UI (Audio Output), content setting (AudioDeviceManager.selectedDeviceIndex), or when adding/ removing the device from the system.  The ActionScript client can check how the audio output change is triggered through “AudioOutputChangeEvent.reason” class. The two reason codes are "AudioOutputChangeReason.USER_SELECTION" and "AudioOutputChangeReason.DEVICE_CHANGE". Here is the general workflow of the API: The content provides a control such as a button that indicates that the user should click to select an audio device. When the user selects the control, a separate UI is presented to the user to handle the click event. It uses the new AudioDeviceManager API to enumerate Audio Output device names, and the UI setup work. When the user selects a device, the content uses the new AudioDeviceManager  API to set the new device in handling the user's selection. Sample Snippet: Access the system available audio device names var audio_device_manager:AudioDeviceManager = AudioDeviceManager.audioDeviceManager; var status_ta:mx.controls.TextArea; status_ta.html = false ; status_ta.setStyle( "fontSize" , 9 ); 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+newline+newline; status_ta.text += "You have " +audio_output_device_array.length+ " device(s) available." +newline+newline; for (var i = 0 ; i&lt;audio_output_device_array.length; i++) {     status_ta.text += "[" +i+ "] " +audio_output_device_array+newline; } 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]      } } Audio device selections made by Flash via AudioDeviceManager API are only valid within the current browser session.  When the browser is closed, the selection will be lost.  User selected audio devices are not persisted within Flash storage, it's the developer's responsibility to save and restore the audio settings if it makes sense for their workflow.  If a user plugs in another default device, ie. a USB headset, Flash content audio will automatically switch to this default device. Known Issues: On Linux, Flash and Non-Flash audio player cannot play audio using the same device at the same time. If audio is switched to a device which is currently playing non Flash content, Flash audio will stop. Flash Player does not properly handle switching between devices with same name. For complete information please see our release notes. Fixed Issues LoadMovie on layers other than 0 causes access violation in C# WinForms (FP-4198533). Flash Player quits unexpectedly before the content is loaded in certain cases. Known Issues EVENT.ACTIVATE not triggered on chrome when a tab is dragged in and out of the Chrome's window(FP-4198532) Flash Player settings panel become unresponsive when hardware acceleration is turned off on Firefox Current Flash Player users who have enrolled in the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to Flash Player 27 over the next 24 hours. Users who have selected "Notify me to install updates" will receive an update notification dialog within 7 days from today.  Please note that Windows users will need to restart their system or log out and in to activate the update notification dialog. Customers using Google Chrome will receive updates through the Google update mechanisms.  Customers using Internet Explorer or Microsoft Edge on Windows 8.1 and Windows 10 will receive the update through Windows Update. If you would like to install the update immediately, please use one of the links below: Flash Player 27 Windows for Internet Explorer - ActiveX:  27.0.0.187 Flash Player 27 Windows for Firefox and other Netscape Compatible Browsers - NPAPI: 27.0.0.187 Flash Player 27 Windows for Opera and Chromium Based Browsers - PPAPI: 27.0.0.187 Flash Player 27 Windows for Google Chrome - PPAPI: 27.0.0.187 Flash Player 27 for Internet Explorer on Windows 8.1 (64-bit machine): 27.0.0.187 Flash Player 27 for Internet Explorer on Windows 8.1 (32-bit machine): 27.0.0.187 Flash Player 27 Windows for Internet Explorer and Edge on Windows 10 - ActiveX: 27.0.0.187 Flash Player 27 Mac for Safari, Firefox and other Netscape Compatible Browsers - NPAPI: 27.0.0.187 Flash Player 27 Mac for Opera and Chromium Based Browsers - PPAPI: 27.0.0.187 Flash Player 27 Mac for Google Chrome - PPAPI: 27.0.0.187 Flash Player 27 desktop for Linux (NPAPI): 27.0.0.187 Flash Player 27 desktop for Linux Chromium (PPAPI): 27.0.0.187 If you encounter a problem with broken or missing links, please clear your browser cache and try again.  If the problem persists, please create a new post in our forum or send email to ccampbel@adobe.com or mkumarjh@adobe.com. ... View more

In today's release, we've updated Flash Player with an important functional fix impacting Flex content and recommend those users impacted update.  Current Flash Player customers who have selected the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to the latest version of Flash Player over the next 24 hours. The most recent Flash Player security bulletin can be found here: Security Bulletin (APSB17-32) Features for Flash Player 27: Support ActionScript API for Audio Device Manager With the release of Flash Player 27, developers can now select the audio output from ActionScript using the new ActionScript API - “AudioDeviceManager”.  It is in sync with Flash Player's audio output settings. A UIA (User Invoked Action) restriction is applied to this API keeping in view user privacy concerns.  The API can only be invoked by a user invoked action.  If it is not invoked by user action, Flash Player throws a runtime error "IllegalOperationError" with error code 2176. Use the AudioDeviceManager class to list down the audio output devices attached to a system using the property, deviceNames().  This returns an array of the attached devices.  The index of the selected device from that array can then be retrieved using the selectedDeviceIndex() property.  A new event introduced with this API, named AudioOutputChangeEvent.AUDIO_OUTPUT_CHANGE is dispatched to ActionScript listeners when the audio output changes.  It is dispatched when the user selects a different audio device from Flash Player's setting UI (Audio Output), content setting (AudioDeviceManager.selectedDeviceIndex), or when adding/ removing the device from the system.  The ActionScript client can check how the audio output change is triggered through “AudioOutputChangeEvent.reason” class. The two reason codes are "AudioOutputChangeReason.USER_SELECTION" and "AudioOutputChangeReason.DEVICE_CHANGE". Here is the general workflow of the API: The content provides a control such as a button that indicates that the user should click to select an audio device. When the user selects the control, a separate UI is presented to the user to handle the click event. It uses the new AudioDeviceManager API to enumerate Audio Output device names, and the UI setup work. When the user selects a device, the content uses the new AudioDeviceManager  API to set the new device in handling the user's selection. Sample Snippet: Access the system available audio device names var audio_device_manager:AudioDeviceManager = AudioDeviceManager.audioDeviceManager; var status_ta:mx.controls.TextArea; status_ta.html = false ; status_ta.setStyle( "fontSize" , 9 ); 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+newline+newline; status_ta.text += "You have " +audio_output_device_array.length+ " device(s) available." +newline+newline; for (var i = 0 ; i&lt;audio_output_device_array.length; i++) {     status_ta.text += "[" +i+ "] " +audio_output_device_array+newline; } 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]      } } Audio device selections made by Flash via AudioDeviceManager API are only valid within the current browser session.  When the browser is closed, the selection will be lost.  User selected audio devices are not persisted within Flash storage, it's the developer's responsibility to save and restore the audio settings if it makes sense for their workflow.  If a user plugs in another default device, ie. a USB headset, Flash content audio will automatically switch to this default device. Known Issues: On Linux, Flash and Non-Flash audio player cannot play audio using the same device at the same time. If audio is switched to a device which is currently playing non Flash content, Flash audio will stop. Flash Player does not properly handle switching between devices with same name. For complete information please see our release notes. Fixed Issues Flash Player crash after logging into VMWare Vsphere web client (FP-4198653) Known Issues EVENT.ACTIVATE not triggered on chrome when a tab is dragged in and out of the Chrome's window(FP-4198532) Flash Player settings panel become unresponsive when hardware acceleration is turned off on Firefox Flash Player 64 bit (flash.ocx) 27.0.0.130 quits unexpectedly (FP-4198598) Current Flash Player users who have enrolled in the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to Flash Player 27 over the next 24 hours. Users who have selected "Notify me to install updates" will receive an update notification dialog within 7 days from today.  Please note that Windows users will need to restart their system or log out and in to activate the update notification dialog. Customers using Google Chrome will receive updates through the Google update mechanisms.  Customers using Internet Explorer or Microsoft Edge on Windows 8.1 and Windows 10 will receive the update through Windows Update. If you would like to install the update immediately, please use one of the links below: Flash Player 26 Windows for Internet Explorer - ActiveX:  27.0.0.183 Flash Player 26 Windows for Firefox and other Netscape Compatible Browsers - NPAPI: 27.0.0.183 Flash Player 26 Windows for Opera and Chromium Based Browsers - PPAPI: 27.0.0.183 Flash Player 26 Windows for Google Chrome - PPAPI: 27.0.0.183 Flash Player 26 for Internet Explorer on Windows 8.1 (64-bit machine): 27.0.0.183 Flash Player 26 for Internet Explorer on Windows 8.1 (32-bit machine): 27.0.0.183 Flash Player 26 Windows for Internet Explorer and Edge on Windows 10 - ActiveX: 27.0.0.183 Flash Player 26 Mac for Safari, Firefox and other Netscape Compatible Browsers - NPAPI: 27.0.0.183 Flash Player 26 Mac for Opera and Chromium Based Browsers - PPAPI: 27.0.0.183 Flash Player 26 Mac for Google Chrome - PPAPI: 27.0.0.183 Flash Player 25 desktop for Linux (NPAPI): 27.0.0.183 Flash Player 25 desktop for Linux Chromium (PPAPI): 27.0.0.183 If you encounter a problem with broken or missing links, please clear your browser cache and try again.  If the problem persists, please create a new post in our forum or send email to ccampbel@adobe.com or mkumarjh@adobe.com. ... View more

In today's release, we've updated Flash Player with an important security fix.  Current Flash Player customers who have selected the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to the latest version of Flash Player over the next 24 hours. The most recent Flash Player security bulletin can be found here: Security Bulletin (APSB17-32) Features for Flash Player 27: Support ActionScript API for Audio Device Manager With the release of Flash Player 27, developers can now select the audio output from ActionScript using the new ActionScript API - “AudioDeviceManager”.  It is in sync with Flash Player's audio output settings. A UIA (User Invoked Action) restriction is applied to this API keeping in view user privacy concerns.  The API can only be invoked by a user invoked action.  If it is not invoked by user action, Flash Player throws a runtime error "IllegalOperationError" with error code 2176. Use the AudioDeviceManager class to list down the audio output devices attached to a system using the property, deviceNames().  This returns an array of the attached devices.  The index of the selected device from that array can then be retrieved using the selectedDeviceIndex() property.  A new event introduced with this API, named AudioOutputChangeEvent.AUDIO_OUTPUT_CHANGE is dispatched to ActionScript listeners when the audio output changes.  It is dispatched when the user selects a different audio device from Flash Player's setting UI (Audio Output), content setting (AudioDeviceManager.selectedDeviceIndex), or when adding/ removing the device from the system.  The ActionScript client can check how the audio output change is triggered through “AudioOutputChangeEvent.reason” class. The two reason codes are "AudioOutputChangeReason.USER_SELECTION" and "AudioOutputChangeReason.DEVICE_CHANGE". Here is the general workflow of the API: The content provides a control such as a button that indicates that the user should click to select an audio device. When the user selects the control, a separate UI is presented to the user to handle the click event. It uses the new AudioDeviceManager API to enumerate Audio Output device names, and the UI setup work. When the user selects a device, the content uses the new AudioDeviceManager  API to set the new device in handling the user's selection. Sample Snippet: Access the system available audio device names var audio_device_manager:AudioDeviceManager = AudioDeviceManager.audioDeviceManager; var status_ta:mx.controls.TextArea; status_ta.html = false ; status_ta.setStyle( "fontSize" , 9 ); 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+newline+newline; status_ta.text += "You have " +audio_output_device_array.length+ " device(s) available." +newline+newline; for (var i = 0 ; i&lt;audio_output_device_array.length; i++) {     status_ta.text += "[" +i+ "] " +audio_output_device_array+newline; } 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]      } } Audio device selections made by Flash via AudioDeviceManager API are only valid within the current browser session.  When the browser is closed, the selection will be lost.  User selected audio devices are not persisted within Flash storage, it's the developer's responsibility to save and restore the audio settings if it makes sense for their workflow.  If a user plugs in another default device, ie. a USB headset, Flash content audio will automatically switch to this default device. Known Issues: On Linux, Flash and Non-Flash audio player cannot play audio using the same device at the same time. If audio is switched to a device which is currently playing non Flash content, Flash audio will stop. Flash Player does not properly handle switching between devices with same name. For complete information please see our release notes. Fixed Issues Resolves CVE-2017-11292 Known Issues EVENT.ACTIVATE not triggered on chrome when a tab is dragged in and out of the Chrome's window(FP-4198532) Flash Player settings panel become unresponsive when hardware acceleration is turned off on Firefox Flash Player 64 bit (flash.ocx) 27.0.0.130 quits unexpectedly (FP-4198598) Current Flash Player users who have enrolled in the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to Flash Player 27 over the next 24 hours. Users who have selected "Notify me to install updates" will receive an update notification dialog within 7 days from today.  Please note that Windows users will need to restart their system or log out and in to activate the update notification dialog. Customers using Google Chrome will receive updates through the Google update mechanisms.  Please note that this release is not available for ActiveX Flash Player on Windows 8.1 and Windows 10. If you would like to install the update immediately, please use one of the links below: Flash Player 26 Windows for Internet Explorer - ActiveX:  27.0.0.170 Flash Player 26 Windows for Firefox and other Netscape Compatible Browsers - NPAPI: 27.0.0.170 Flash Player 26 Windows for Opera and Chromium Based Browsers - PPAPI: 27.0.0.170 Flash Player 26 Windows for Google Chrome - PPAPI: 27.0.0.170 Flash Player 26 for Internet Explorer on Windows 8.1 (64-bit machine): 27.0.0.170 Flash Player 26 for Internet Explorer on Windows 8.1 (32-bit machine): 27.0.0.170 Flash Player 26 Windows for Internet Explorer and Edge on Windows 10 - ActiveX: 27.0.0.170 Flash Player 26 Mac for Safari, Firefox and other Netscape Compatible Browsers - NPAPI: 27.0.0.170 Flash Player 26 Mac for Opera and Chromium Based Browsers - PPAPI: 27.0.0.170 Flash Player 26 Mac for Google Chrome - PPAPI: 27.0.0.170 Flash Player 25 desktop for Linux (NPAPI): 27.0.0.170 Flash Player 25 desktop for Linux Chromium (PPAPI): 27.0.0.170 If you encounter a problem with broken or missing links, please clear your browser cache and try again.  If the problem persists, please create a new post in our forum or send email to ccampbel@adobe.com or mkumarjh@adobe.com. ... View more

Today we're pleased to announce that the next version of the Windows AIR SDK is available for immediate download.  This release of AIR provides bug fixes for Windows-based developers. Below are some of the key features and benefits of AIR 27.  Please see our release notes for full details. Announcements 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. Disabling Packaging of Shared Android Applications Starting with AIR 26, packaging of shared applications for Android is disabled. With this change, published applications will always have a captive copy of the runtime included in their installation package irrespective of the target selected (that is, apk or apk-captive-runtime).  This change allows us to focus our testing and engineering on captive installation, by far, the most popular option. New Features macOS AIR SDK Upgrade From AIR 27, AIR Runtime is built with Mac 10.12 SDK. App Transport Security (ATS) introduced by Apple does not allow insecure connections between App and Web services. Because of this change, we recommend that developers update web connection calls to https to comply with Apple's App Transport Security.  Please see the announcement section for more details. Asynchronous texture upload for AIR Desktop In AIR 26, the texture upload was synchronous on AIR desktop. Therefore, developers had to wait till the new texture was uploaded successfully. With AIR 27, you can now upload textures asynchronously while the current texture is being rendered. This ensures a better UI performance for AIR applications and a smoother user experience. On successfully completing an asynchronous texture upload, a TEXTURE_READY event will be generated. Asynchronous upload of texture data for all the texture formats is done using the following two new APIs: uploadFromBitmapDataAsync( source:BitmapData, miplevel:uint = 0) uploadFromByteArrayAsync( data:ByteArray, byteArrayOffset:uint, miplevel:uint = 0 ) This feature supports Normal and Rectangular texture for miplevel 0 only. Enable DirectX 11 for AIR Win AIR 26 and below used DirectX 9 for hardware accelerated rendering on Windows. Beginning with AIR 27.0, AIR will use DirectX 11 for the hardware accelerated rendering for Windows 8.0 and above.For Windows 7 and below, hardware accelerated content will continue to use DirectX 9. The AIR application will load the respective DirectX 11 DLL i.e. d3d11.dll to render any hardware accelerated content. If hardware acceleration is disabled, or the hardware is unavailable the rendering falls back to the Software mode. If the specific DLL for DirectX 11 is missing on the system, the rendering again falls back to Software mode.This feature is supported with SWF version 38 and above. Adding support for new languages in AIR Mobile Starting with AIR 27, we have added support for the following languages: Finnish (fi), Greek (el), Indonesian (in), Malay (ms), Thai (th) Vietnamese (vi) Note: To use these languages, the Namespace value in application descriptor must be 27.0 or greater. Sample Snippet: <supportedLanguages>fi el in ms th vi</supportedLanguages> <name> <text xml:lang= "fi" >NameInFinnish</text> </name> Fixed Issues [IOS] IOS device list is not getting listed after iTunes update to 12.7.0.166 on Windows (AIR-4198467) [iOS] Installation Error: API Internal Error while installing ipa on iOS11 devices using Flash Builder, Animate CC and Command line on Windows Known Issues [iOS] Applications not getting installed on iOS 11 devices on Mac 10.13.  If encountered, please unplug and plug in the device a second time, then repeat the installation process Download Locations: AIR runtime for Windows: 27.0.0.124 Runtime Download AIR runtime for Macintosh: 27.0.0.128 Runtime Download AIR SDK & Compiler for Windows: 27.0.0.132 SDK & Compiler Download AIR SDK & Compiler for Macintosh: 27.0.0.128 SDK & Compiler Download Note: To provide all the all the necessary tools for our developers in one place and avoid having to download multiple components, we are packaging Adobe AIR 27 SDK and ActionScript Compiler 2.0 in a single SDK called “Adobe AIR 27 SDK & Compiler”. AIR SDK (Compatible with Flex) for Windows: 27.0.0.132 SDK Windows Download AIR SDK (Compatible with Flex) for Macintosh: 27.0.0.128 SDK Macintosh Download Previous versions of the AIR runtime and SDK can be found on the Archived AIR SDK and Runtimes page ... View more

In today's release, we've updated Flash Player with important bug fixes.  Current Flash Player customers who have selected the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to the latest version of Flash Player over the next 24 hours. Flash Player for Microsoft Edge and Internet Explorer 11 Update With this monthly Flash Player update addressing functionality bugs, Flash Player for Microsoft Edge and Internet Explorer on Windows 8.1 and Windows 10 will not be updated on "Patch Tuesday", October 10th. This update will instead be released by Microsoft later this month. The most recent Flash Player security bulletin can be found here: Security Bulletin (APSB17-31) Features for Flash Player 27: Support ActionScript API for Audio Device Manager With the release of Flash Player 27, developers can now select the audio output from ActionScript using the new ActionScript API - “AudioDeviceManager”.  It is in sync with Flash Player's audio output settings. A UIA (User Invoked Action) restriction is applied to this API keeping in view user privacy concerns.  The API can only be invoked by a user invoked action.  If it is not invoked by user action, Flash Player throws a runtime error "IllegalOperationError" with error code 2176. Use the AudioDeviceManager class to list down the audio output devices attached to a system using the property, deviceNames().  This returns an array of the attached devices.  The index of the selected device from that array can then be retrieved using the selectedDeviceIndex() property.  A new event introduced with this API, named AudioOutputChangeEvent.AUDIO_OUTPUT_CHANGE is dispatched to ActionScript listeners when the audio output changes.  It is dispatched when the user selects a different audio device from Flash Player's setting UI (Audio Output), content setting (AudioDeviceManager.selectedDeviceIndex), or when adding/ removing the device from the system.  The ActionScript client can check how the audio output change is triggered through “AudioOutputChangeEvent.reason” class. The two reason codes are "AudioOutputChangeReason.USER_SELECTION" and "AudioOutputChangeReason.DEVICE_CHANGE". Here is the general workflow of the API: The content provides a control such as a button that indicates that the user should click to select an audio device. When the user selects the control, a separate UI is presented to the user to handle the click event. It uses the new AudioDeviceManager API to enumerate Audio Output device names, and the UI setup work. When the user selects a device, the content uses the new AudioDeviceManager  API to set the new device in handling the user's selection. Sample Snippet: Access the system available audio device names var audio_device_manager:AudioDeviceManager = AudioDeviceManager.audioDeviceManager; var status_ta:mx.controls.TextArea; status_ta.html = false ; status_ta.setStyle( "fontSize" , 9 ); 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+newline+newline; status_ta.text += "You have " +audio_output_device_array.length+ " device(s) available." +newline+newline; for (var i = 0 ; i&lt;audio_output_device_array.length; i++) {     status_ta.text += "[" +i+ "] " +audio_output_device_array+newline; } 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]      } } Audio device selections made by Flash via AudioDeviceManager API are only valid within the current browser session.  When the browser is closed, the selection will be lost.  User selected audio devices are not persisted within Flash storage, it's the developer's responsibility to save and restore the audio settings if it makes sense for their workflow.  If a user plugs in another default device, ie. a USB headset, Flash content audio will automatically switch to this default device. Known Issues: On Linux, Flash and Non-Flash audio player cannot play audio using the same device at the same time. If audio is switched to a device which is currently playing non Flash content, Flash audio will stop. Flash Player does not properly handle switching between devices with same name. For complete information please see our release notes. Fixed Issues Audio device selection not working when there are multiple devices with same name(FP-4198585) Content freezes while switching the tabs on Firefox (FP-4198571, FP-4198555) Video stops rendering after minimizing/restoring the Firefox browser window Known Issues EVENT.ACTIVATE not triggered on chrome when a tab is dragged in and out of the Chrome's window(FP-4198532) Flash Player settings panel become unresponsive when hardware acceleration is turned off on Firefox Flash Player 64 bit (flash.ocx) 27.0.0.130 quits unexpectedly (FP-4198598) Current Flash Player users who have enrolled in the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to Flash Player 27 over the next 24 hours. Users who have selected "Notify me to install updates" will receive an update notification dialog within 7 days from today.  Please note that Windows users will need to restart their system or log out and in to activate the update notification dialog. Customers using Google Chrome will receive updates through the Google update mechanisms.  Please note that this release is not available for ActiveX Flash Player on Windows 8.1 and Windows 10. If you would like to install the update immediately, please use one of the links below: Flash Player 26 Windows for Internet Explorer - ActiveX:  27.0.0.159 Flash Player 26 Windows for Firefox and other Netscape Compatible Browsers - NPAPI: 27.0.0.159 Flash Player 26 Windows for Opera and Chromium Based Browsers - PPAPI: 27.0.0.159 Flash Player 26 Windows for Google Chrome - PPAPI: 27.0.0.159 Flash Player 26 for Internet Explorer on Windows 8.1 (64-bit machine): 27.0.0.159 Flash Player 26 for Internet Explorer on Windows 8.1 (32-bit machine): 27.0.0.159 Flash Player 26 Windows for Internet Explorer and Edge on Windows 10 - ActiveX: 27.0.0.159 Flash Player 26 Mac for Safari, Firefox and other Netscape Compatible Browsers - NPAPI: 27.0.0.159 Flash Player 26 Mac for Opera and Chromium Based Browsers - PPAPI: 27.0.0.159 Flash Player 26 Mac for Google Chrome - PPAPI: 27.0.0.159 Flash Player 25 desktop for Linux (NPAPI): 27.0.0.159 Flash Player 25 desktop for Linux Chromium (PPAPI): 27.0.0.159 If you encounter a problem with broken or missing links, please clear your browser cache and try again.  If the problem persists, please create a new post in our forum or send email to ccampbel@adobe.com or mkumarjh@adobe.com. ... View more

In Flash Player 27, we added support for user configurable audio output selection via Flash Player's settings dialog (see our release notes​ for additional details).  Unfortunately, this feature has caused adverse side effects for some customers that we did not encounter in our internal testing.  To resolve this as quickly as possible we are taking the following steps: In our next release, scheduled for October 10th, we will roll back the user configurable audio selection to Flash Player 26 levels.  This change should immediately resolve the problem that some customers have encountered with multiple audio devices on their system. Developers that are utilizing our new AudioDeviceManager API's can continue to do so, but any changes made will be local to the SWF being run and will be lost when the Flash process ends.  It will be up to the developer to remember and restore the user settings (if applicable). We will release a beta build of Flash player in the coming days for users to test these changes against.  Beta releases can be found on labs.adobe.com.  An update to this thread will be made when the beta is available. We will revisit this feature and determine what steps need to be taken to fully correct the behavior before rereleasing it in a future build. We thank you for your assistance and patience while we address this issue.  ... View more

Today we're pleased to announce that the next version of AIR is available for immediate download.  This release of AIR provides bug fixes, security updates, and new features. Below are some of the key features and benefits of AIR 27.  Please see our release notes for full details. Announcements 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. Disabling Packaging of Shared Android Applications Starting with AIR 26, packaging of shared applications for Android is disabled. With this change, published applications will always have a captive copy of the runtime included in their installation package irrespective of the target selected (that is, apk or apk-captive-runtime).  This change allows us to focus our testing and engineering on captive installation - by far, the most popular option. New Features macOS AIR SDK Upgrade From AIR 27, AIR Runtime is built with Mac 10.12 SDK. App Transport Security (ATS) introduced by Apple does not allow insecure connections between App and Web services. Because of this change, we recommend that developers update web connection calls to https to comply with Apple's App Transport Security.  Please see the announcement section for more details. Asynchronous texture upload for AIR Desktop In AIR 26, the texture upload was synchronous on AIR desktop. Therefore, developers had to wait till the new texture was uploaded successfully. With AIR 27, you can now upload textures asynchronously while the current texture is being rendered. This ensures a better UI performance for AIR applications and a smoother user experience. On successfully completing an asynchronous texture upload, a TEXTURE_READY event will be generated. Asynchronous upload of texture data for all the texture formats is done using the following two new APIs: uploadFromBitmapDataAsync( source:BitmapData, miplevel:uint = 0) uploadFromByteArrayAsync( data:ByteArray, byteArrayOffset:uint, miplevel:uint = 0 ) This feature supports Normal and Rectangular texture for miplevel 0 only. Enable DirectX 11 for AIR Win AIR 26 and below used DirectX 9 for hardware accelerated rendering on Windows. Beginning with AIR 27.0, AIR will use DirectX 11 for the hardware accelerated rendering for Windows 8.0 and above.For Windows 7 and below, hardware accelerated content will continue to use DirectX 9. The AIR application will load the respective DirectX 11 DLL i.e. d3d11.dll to render any hardware accelerated content. If hardware acceleration is disabled, or the hardware is unavailable the rendering falls back to the Software mode. If the specific DLL for DirectX 11 is missing on the system, the rendering again falls back to Software mode.This feature is supported with SWF version 38 and above. Adding support for new languages in AIR Mobile Starting with AIR 27, we have added support for the following languages: Finnish (fi), Greek (el), Indonesian (in), Malay (ms), Thai (th) Vietnamese (vi) Note:To use these languages, the Namespace value in application descriptor must be 27.0 or greater. Sample Snippet: <supportedLanguages>fi el in ms th vi</supportedLanguages> <name> <text xml:lang= "fi" >NameInFinnish</text> </name> Fixed Issues Application blinks when switched to the full-screen mode for Windows 8 and above.(AIR-4198437, AIR-4198443) AIR application jerk around when trying to move them. (AIR-4198340)"Error #3672: Buffer creation failed" is observed when Anti-Aliasing uses render to texture on starling projects (AIR-4198370) [iOS ] TextField Input position is largely deviated (AIR-4198324) [Android] Bug fixes related to Secure Socket on Android for TLS protocol. [Android] no-version-vectors flag has been added to aapt tool [tvOS ]ADT error 303: Icon banner320x180.png is missing from package (AIR-4198396) [iOS] Audio gone after playing an embedded Youtube Video (AIR-4198383) [iOS] Interruptions such as incoming calls break audio (AIR-4198386) [AndroidTV] TV banner is now required/mandatory for all Android TV apps. [iOS] ADT to correctly sign dynamic frameworks included packaged with iOS app (AIR-4198407) [iOS] ADT to correctly sign dynamic frameworks (AIR-4198408) Video Texture keeps accessing camera even after being disposed of. (AIR-4198123) Known Issues [Android] Error #3672: Buffer creation failed when using drawToBitmapData (Context3D) while using VideoTexture (AIR-4198290) [Android] No data from "android.intent.action.SEND" Intent (AIR-4197491) [tvOS] Installation of application fails on tvOS Simulator Artifacts are observed when child Sprite is near bottom of screen (AIR-4198445) Bitmap glitches are observed while drawing the pixels (AIR-4198453) [iOS] AIR app rotation broken on iOS Beta 3 when using -platformSDK (AIR-4198406) [iOS] Installation of AIR applications on iOS 11 fails using ADT on Windows Download Locations: AIR runtime for Windows: 27.0.0.124 Runtime Download AIR runtime for Macintosh: 27.0.0.128 Runtime Download AIR SDK & Compiler for Windows: 27.0.0.124 SDK & Compiler Download AIR SDK & Compiler for Macintosh: 27.0.0.128 SDK & Compiler Download Note: To provide all the all the necessary tools for our developers in one place and avoid having to download multiple components, we are packaging Adobe AIR 27 SDK and ActionScript Compiler 2.0 in a single SDK called “Adobe AIR 27 SDK & Compiler”. AIR SDK (Compatible with Flex) for Windows: 27.0.0.124 SDK Windows Download AIR SDK (Compatible with Flex) for Macintosh: 27.0.0.128 SDK Macintosh Download Previous versions of the AIR runtime and SDK can be found on the Archived AIR SDK and Runtimes page ... View more

In today's release, we've updated Flash Player with important bug fixes and security updates.  Current Flash Player customers who have selected the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to the latest version of Flash Player over the next 24 hours. The most recent Flash Player security bulletin can be found here: Security Bulletin (APSB17-28) Features for Flash Player 27: Support Audio Output Selection in Flash Player Starting with Flash Player version 27, the user can select an audio device directly from the Flash Player Settings dialog through a newly added audio output tab. Here is the screenshot of the Audio Output user interface: All the attached audio output devices of the system are listed in the drop-down menu. The user can select any of the available devices and once the settings dialog is closed, audio starts playing from the selected device. The selected device will be the current audio playback device for all Flash Player instances. For non-Pepper platforms, audio output selection setting is global among all browser tabs of the same process. When it is changed, all other tabs of the same process are affected. Restriction in Chrome: Audio Output device shares the same permissions with Microphone. So, if microphone permission is denied, audio output tab does not show the available audio devices. Also, “https:” must be used to enumerate Microphone and Audio Output devices after Chrome M60. You can show the device names on Chrome (or Chromium based browsers such as Opera) in the following ways: If the current flash content tries to use Microphone, and user grants the permission, then device names will be shown when the user opens "Audio Output" tab in Settings UI dialog. In Settings UI dialog, user can click Microphone tab, and grant the permission, then close and re-launch Settings UI dialog. This feature is supported in all versions of Flash Player Standalone and Plugin on Win/Mac/Linux except ChromeOS. Support ActionScript API for Audio Device Manager With the release of Flash Player 27, developers can now select the audio output from ActionScript using the new ActionScript API - “AudioDeviceManager”.  It is in sync with Flash Player's audio output settings. A UIA (User Invoked Action) restriction is applied to this API keeping in view user privacy concerns.  The API can only be invoked by a user invoked action.  If it is not invoked by user action, Flash Player throws a runtime error "IllegalOperationError" with error code 2176. Use the AudioDeviceManager class to list down the audio output devices attached to a system using the property, deviceNames().  This returns an array of the attached devices.  The index of the selected device from that array can then be retrieved using the selectedDeviceIndex() property.  A new event introduced with this API, named AudioOutputChangeEvent.AUDIO_OUTPUT_CHANGE is dispatched to ActionScript listeners when the audio output changes.  It is dispatched when the user selects a different audio device from Flash Player's setting UI (Audio Output), content setting (AudioDeviceManager.selectedDeviceIndex), or when adding/ removing the device from the system.  The ActionScript client can check how the audio output change is triggered through “AudioOutputChangeEvent.reason” class. The two reason codes are "AudioOutputChangeReason.USER_SELECTION" and "AudioOutputChangeReason.DEVICE_CHANGE". Here is the general workflow of the API: The content provides a control such as a button that indicates that the user should click to select an audio device. When the user selects the control, a separate UI is presented to the user to handle the click event. It uses the new AudioDeviceManager API to enumerate Audio Output device names, and the UI setup work. When the user selects a device, the content uses the new AudioDeviceManager  API to set the new device in handling the user's selection. Sample Snippet: Access the system available audio device names var audio_device_manager:AudioDeviceManager = AudioDeviceManager.audioDeviceManager; var status_ta:mx.controls.TextArea; status_ta.html = false ; status_ta.setStyle( "fontSize" , 9 ); 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+newline+newline; status_ta.text += "You have " +audio_output_device_array.length+ " device(s) available." +newline+newline; for (var i = 0 ; i&lt;audio_output_device_array.length; i++) {     status_ta.text += "[" +i+ "] " +audio_output_device_array+newline; } 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]      } } For complete information please see our release notes. Fixed Issues The application will behave abnormally when spacebar is pressed in the Text Field.(FP-4198253) [Win10] Context menu displayed with Offset when Flash Player movie fullscreen on Chrome(FP-4198406) Multiple security and functional fixes Known Issues Memory leak is observed when using baseline_constrained profile on Firefox 55 onwards (FP-4198562) Invalid stageWidth and stageHeight is observed on Firefox 55 onwards with render mode as direct and async drawing enabled. Current Flash Player users who have enrolled in the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to Flash Player 27 over the next 24 hours. Users who have selected "Notify me to install updates" will receive an update notification dialog within 7 days from today.  Please note that Windows users will need to restart their system or log out and in to activate the update notification dialog. Customers using Google Chrome will receive updates through the Google update mechanisms.  Please note that this release is not available for ActiveX Flash Player on Windows 8.1 and Windows 10. If you would like to install the update immediately, please use one of the links below: Flash Player 26 Windows for Internet Explorer - ActiveX:  27.0.0.130 Flash Player 26 Windows for Firefox and other Netscape Compatible Browsers - NPAPI: 27.0.0.130 Flash Player 26 Windows for Opera and Chromium Based Browsers - PPAPI: 27.0.0.130 Flash Player 26 Windows for Google Chrome - PPAPI: 27.0.0.130 Flash Player 26 for Internet Explorer on Windows 8.1 (64-bit machine): 27.0.0.130 Flash Player 26 for Internet Explorer on Windows 8.1 (32-bit machine): 27.0.0.130 Flash Player 26 Windows for Internet Explorer and Edge on Windows 10 - ActiveX: 27.0.0.130 Flash Player 26 Mac for Safari, Firefox and other Netscape Compatible Browsers - NPAPI: 27.0.0.130 Flash Player 26 Mac for Opera and Chromium Based Browsers - PPAPI: 27.0.0.130 Flash Player 26 Mac for Google Chrome - PPAPI: 27.0.0.130 Flash Player 25 desktop for Linux (NPAPI): 27.0.0.130 Flash Player 25 desktop for Linux Chromium (PPAPI): 27.0.0.130 If you encounter a problem with broken or missing links, please clear your browser cache and try again.  If the problem persists, please create a new post in our forum or send email to ccampbel@adobe.com or mkumarjh@adobe.com. ... View more