Quantcast
Channel: Adobe Community : Popular Discussions - Flash Runtime Announcements
Viewing all 25114 articles
Browse latest View live

12/28/2015 - Release - Flash Player 20

$
0
0

The next version of Flash Player is available for immediate download.  In today's release we've updated Flash Player with both critical security and functional bug fixes.  We recommend all users update to the latest version.

 

Security update details can be found here: Security Bulletin (APSB16-01)

 

New Features for Flash Player 20:


  • Video rotation information available to ActionScript

The Flash runtime will now process the track header box and movie header box metadata correctly, allowing for correct positioning and sizing of video.

 

  • Stage3D instanced drawing

We’re constantly looking for ways to improve the lives of our developers.  Our Stage3d API’s have allowed developers to create incredibly beautiful and fluid performing games.  This new API will leverage the GPU on mobile devices and provides improved performance when drawing similar objects numerous times in a scene.


  • PPAPI vector printing for Windows

Another platform parity success story.  With Flash Player 20, vector printing has come to the PPAPI platform on Windows (Mac support coming soon).  Developers can now provide an enhanced and superior quality printing experience for their customers if they desire while bitmap printing is still fully supported.

 

  • Hardware acceleration control for IE and Edge on Windows 8 & 10

With Flash Player 20, customers can now enable or disable hardware acceleration in Flash Player on Internet Explorer and Edge browsers for both Windows 8 and Windows 10.  This feature, available in the Flash Player settings dialog, provides users a critical support option when encountering issues with their system’s video drivers.


 

For complete information please see our release notes.



Fixed Issues

  • [PPAPI][Chrome]: Certain text is getting corrupted while printing [4101195]
  • VB6 Fusion Chart Not Loading [4100436]
  • Flash player freezes when accessing select content on beatingtheblues.co.uk [4099360]
  • [SAP Only] trackHeaderBoxMatrix and movieHeaderBoxMatrix value are not in proper format. (4093085)
  • 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 20 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 or Windows 8.x Internet Explorer or Windows 10 Internet Explorer or Microsoft Edge will receive the update through the Google and Microsoft update mechanisms.

 

If you would like to install the update immediately, please use one of the links below:

 

Flash Player 20 Windows for Internet Explorer - ActiveX: 20.0.0.267

Flash Player 20 Windows for Firefox and other Netscape Compatible Browsers - NPAPI: 20.0.0.267

Flash Player 20 Windows for Opera and Chromium Based Browsers - PPAPI: 20.0.0.267

 

Flash Player 20 for Internet Explorer on Windows 8.1 (64-bit machine): 20.0.0.267

Flash Player 20 for Internet Explorer on Windows 8.1 (32-bit machine): 20.0.0.267

Flash Player 20 for Internet Explorer on Windows 8 (64-bit machine): 20.0.0.267

Flash Player 20 for Internet Explorer on Windows 8 (32-bit machine): 20.0.0.267

 

Flash Player 20 Mac for Safari, Firefox and other Netscape Compatible Browsers - NPAPI: 20.0.0.267

Flash Player 20 Mac for Opera 26 and Chromium Based Browsers - PPAPI: 20.0.0.267

 

Flash Player 11.2 desktop for Linux (NPAPI): 11.2.202.559

 

Flash Player 18 Extended Support Release for Windows and Macintosh: 18.0.0.324

 

Previous versions of Flash Player can be found on the Flash Player Archive page

 

If you encounter a problems 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.


10/28/2016 - Beta - Flash Player 24.0.0.138

$
0
0

Welcome to the Flash Runtime version 24 beta!  We've been hard at work adding new features to Flash Player and we're looking forward to receiving feedback from our Flash Player community.

This beta release includes new features as well as enhancements and bug fixes related to security, stability, performance, and device compatibility for Flash Player 24.  For full details, please see our release notes.

Note:

  • The ActiveX Flash Player in this release is not compatible with Windows® 8.x or 10
  • Flash Player for Windows® 8.x/10 is available as part of the generally available Windows® 8.x/10 update

New and Updated Features

Improved support for high resolution displays on Firefox for Windows

Beginning with Flash Player version 24 and Firefox version 51 on Windows, Flash content will now scale appropriately on high resolution displays.

Separate HTTP and HTTPS permissions for Camera and Microphone

To provide users with a better control over their camera and microphone data, Flash Player now provides a more fine-grained control over how permissions are granted. Users can now allow camera and microphone access for a domain when that content is served via HTTPS, and disallow the access when content from the domain is served over HTTP. Since this feature is currently in beta, the settings will not be visible in the Global settings Manager.

Flash Player PPAPI & NPAPI for Linux

With this Beta we are providing 32 and 64 bit binaries in tar.gz format for NPAPI and PPAPI Linux. We will be adding RPM installers and Standalone players in upcoming Beta releases.

Known Issues

  • Enabling async drawing shows boundaries for transparent object (4196843).
  • Blank screen is observed until mouse click received after enabling Async drawing (4197066).
  • "ALT GR+0" Does not return @ on french layout Keyboard(4196791).
  • "Installation Failed" error is observed on Mac 10.7 for all browsers (4186587).
  • Black screen is observed when video is seeking on Chrome(4186499).
  • Seek bar does not appear on hovering mouse cursor on video(4186564).
  • Action Script is unable to handle MOUSE_MOVE event(4186547).

Fixed Issues

  • None

System Requirements

For system requirements of the current release of Flash Player in production, please visithttp://www.adobe.com/products/flashplayer/systemreqs/

About the Beta Channel

To get the latest Beta build of Flash Player visit Adobe labs

Beta versions of Flash Player are also available for automatic installation via our Background Update service.  Please subscribe to automatically receive update notifications for future Flash Runtime announcements.

Note: If you are having issues downloading Flash Player, it may be because of a cache or locale issue. Wait for 24 hours before retrying and if you still face issues, please post the issue in Flash Player forum

3/14/2017 - Release - AIR 25 Runtime and SDK

$
0
0

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 25.  Please see our release notes for full details.

 

New Features:

Android TV Support

With AIR 25, Android TV will be part of regular AIR SDK releases. It will not be restricted for beta channels only.

Android TV support for AIR Android applications was introduced in AIR 20. Using this feature, developers will be able to develop captive runtime applications that are also compatible with Android TV. Please use swf-version 31 or greater and namespace 20.0 or greater to access this feature. Below mentioned two tags needs to be added in 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 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, xhdpi resource. In case developer does not provide the banner image with <supportsAndroidTV>true<supportsAndroidTV> tag, a default banner image will reflect on home screen of  Android TV. SDK tools should be updates 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 –target apk-captive-runtime for Android TV. Android TV support is available from AIR SDK 20.0 or higher so namespace need to be added accordingly in app.xml file.

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

Starting in AIR 25, 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 foripa-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 on the AppStore 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/li b.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 arm64Compilation failed while executing : ld64

iOS SDK Upgrade

The AIR Runtime is now built with the iOS 10 SDK, which enables AIR developers to use ANEs built with iOS 10 APIs without using the –platformSDK switch while packaging with ADT.

Option to fallback to older video pipeline for Android

AIR 22 had significant changes to the Android Video pipeline. For more information, see the Release Notes for that release.  If your application is facing issues because of these changes, starting in AIR 25, you can fallback to the older video pipeline using a new tag named <disableMediaCodec> in the application descriptor to enable/disable MediaCodec for Android. When setting this flag as true, MediaCodec is disabled and video is decoded using OpenMax AL just like in AIR 21. The default value for this tag is false.

 

Sample snippet:Here is an example code snippet for disabling MediaCodec.

<android>

            <manifestAdditions><![CDATA[

           

           

            ]]></manifestAdditions>

            <disableMediaCodec>true</disableMediaCodec>

</android>

AS3 API to get Compilation Information for iOS

Starting AIR 25 (with swf version 36 and above) we have a new API for ActionScript developers to determine if their application is running with compiled runtime or interpreted runtime. The new API “isCompiledAOT” is added to NativeApplication class.This API returns true if the application is built using one of the following AOT targets:

 

  • ipa-app-store
  • ipa-test
  • ipa-debug
  • ipa-ad-hoc

 

This API returns false for any other iOS target and other AIR platforms like AIR android and AIR desktop.

 

Local Storage Support in StageWebView for Android

Starting AIR 25 (with swf version 36 and above), local storage in StageWebView is available for Android. Now, the sites that require local DOM storage work as expected on StageWebView.

 

Sample snippet:

 

For example, the below HTML page will load correctly in StageWebView using AIR 25.

<html>

    <script>

        function enableStore(){

            localStorage.setItem("set", "Storage enabled");

            document.getElementById("abc").innerHTML = localStorage.getItem("set");

        }

    </script>

    <body>

        <h1 id="abc"> Storage disabled </h1>

        <script> enableStore() </script>

    </body>

</html>

 

Result: "Storage enabled"

Adding support for new languages in AIR Mobile


Starting AIR 25, we have added support for the following languages:

  • Danish (da)
  • Norwegian (nb)
  • Hebrew (iw)

 

Note:To use these languages, the Namespace value in application descriptor must be 25.0 or greater.

 

Sample Snippet:

<supportedLanguages>da en nb</supportedLanguages>

<name>

<text xml:lang="da">NameInDanish</text>

</name>

 

Multidex support for Android

Starting with AIR 25, MultiDex support is available for Android. Through MultiDexing, developers can package apps that exceed the 64K references limit. Usually, 64K references limit reach when the ANEs have a lot of methods.

 

More information on Android Multidex can be found here: https://developer.android.com/studio/build/multidex.html.

 

Note: If you use ANEs containing pre-dex libraries, there will be a packaging error when you try to package it.

 

Offset support for drawToBitmapData()

Beginning in AIR 25, capturing current buffer data of the back render buffer through drawToBitmapData() allows offsets for capturing a target rectangle from buffer instead of complete buffer.The feature is supported on Windows, Mac, iOS and android platforms.

 

Background:

 

drawToBitmapdata(BitmapData) is used to draw the current render buffer to a destination bitmap. It used to take a bitmap input to which it would copy the complete buffer content.

 

Offset Implementation:

Starting with AIR 25, the API drawToBitmapData( destination:BitmapData, srcRect:Rectangle = null, destPoint:Point = null) copies a particular target area from the buffer and copies it to the bitmap. The API takes the following inputs:

 

  • Destination Bitmap(Bitmap): Bitmap to which rendered buffer data would be copied to.
  • Source Rectangle(srcRect): Rectangle defined on the back render buffer, from which the data would be copied
  • Destination point(destPoint): Offset on the bitmap where the data will be copied to.

 

This can be understood by the following demonstration:offsest.png

Some important points:

  • If the source rectangle goes beyond the current render buffer, the rectangle part extending beyond the dimensions of buffer is clipped, this is similar to target area of Stage3D as in the representation above.
  • If the target area selected in the above step goes beyond the dimensions of the bitmap, the part extending beyond bitmap is clipped.
  • The actual target area would be final bitmap data according to the rectangle size and the bitmap size and offsets chosen.
  • In case, the offsets (destination offset, source rectangle offset) falls out of the dimensions or are set negative, “Error #3802: Offset outside stage coordinate bound” would be thrown.
  • If the values for source rectangle and the destination offset is set null, the API falls back to the older implementation where complete buffer is copied to the bitmap.

Instanced Drawing on AIR Desktop

Instanced drawing feature which was available for AIR Mobile is now available in AIR Desktop. This feature helps developers to use a  model of graphical object and render it multiple times in a single frame. This reduces draw calls and hence rendering and overallperformance is smoother.

 

Similar to AIR Mobile, to use this feature on Desktop ,developers can use the createVertexBufferForIntance() and drawTriangleInstanced() APIs.

 

Context3D::createVertexBufferForInstances( numElements:int, data32PerElement:int, instancesPerElement:int, bufferUsage:String = "staticDraw", ):VertexBuffer3D;

 

Use the VertexBuffer3D object to upload a set of instance data to the rendering context.  The vertex buffer contains the data needed to render each instance in the scene geometry.  Vertex Buffers with instance data provide attributes that are common to all the vertices of an instance and serve as the input to the vertex shader program.

 

Context3D::drawTrianglesInstanced( indexBuffer:IndexBuffer3D, numInstances, firstIndex:int=0, numTriangles:int=-1 ):void;

 

AGAL version 3 with “iid” register can be downloaded from: https://github.com/adobe-flash/graphicscorelib/tree/master/src/com/adobe/utils/v3

 

Assumptions and Dependencies

  • 1) This feature is supported only on devices that support Standard Extended Profile
  • 2) This feature is only available in AIR Mobile and Desktop.

 

Fixed Issues

  • [Android] Allocations made by async texture upload are not freed up after multiple asynchronous uploads(AIR-4198245)
  • [Android] Framerate of application is very low in PowerVR GPU while using renderMode as GPU(AIR-4174521).
  • Unable to install the application on iOS Simulator(AIR-4198023)
  • TEXTURE_READY event is dispatched very soon when uploading the RectangleTexture repeatedly(AIR-4198247)
  • [iOS]Starling apps using starling.image.mask quits unexpectedly on low-end devices(4187140)
  • [MAC] Adobe AIR_64 Helper and ExtendedAppEntryTemplate64 creates problems while codesigning MAC Captive App.(AIR-4189809)
  • Starling does not display any content on Integrated GPU Intel HD Graphics with AIR 24 (AIR-4198176, AIR-4198227)
  • flash.ui.GameInput fires DEVICE_ADDED / DEVICE_REMOVED events in an endless loop (AIR-4198163)

 

 

Known Issues:

  • [iOS] Application crashes on using a feather textInput
  • [iOS] Dictionary containing values of type Vector.<Function> result in hidden String allocations (AIR-4115729)
  • [iOS] Compilation failed while executing : compile-abc - Class (...) could not be found. (AIR-4198225)
  • [Android] Launcher icons are packaged in incorrect resources location (AIR-4198222)
  • [iOS] Interfaces don't function when shared between swf’s (AIR-4194914)
  • [iOS] Crash when trying to access function arguments (AIR-4117964)

 

 

Download Locations:

 

AIR runtime for Windows: 25.0.0.134 Runtime Download

AIR runtime for Macintosh: 25.0.0.134 Runtime Download

 

AIR SDK & Compiler for Windows: 25.0.0.134 SDK & Compiler Download

AIR SDK & Compiler for Macintosh: 25.0.0.134 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 25 SDK and ActionScript Compiler 2.0 in a single SDK called “Adobe AIR 25 SDK & Compiler”.

 

AIR SDK (Compatible with Flex) for Windows: 25.0.0.134 SDK Windows Download

AIR SDK (Compatible with Flex) for Macintosh: 25.0.0.134 SDK Macintosh Download

 

Previous versions of the AIR runtime and SDK can be found on the Archived AIR SDK and Runtimes page

8/8/2017 - Release - Flash Player 26

$
0
0

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-23)

 

Features for Flash Player 26:

D2D Vector Printing Support

This feature brings back vector printing in Microsoft Edge in Windows 10 and Immersive IE in Windows 8 in "Out of Process" mode.  This feature will not only enhance the speed of printing but also reduce the data size input.  Initially, a mixed way to print (GDI Vector + D2D Bitmap) has been used in ActiveX Windows 8.1 and above.  Now Vector printing will be done through D2D APIs in Windows 8.1 and Windows 10.  There is no difference in the Actionscript API’s.

 

For complete information please see our release notes.

 

 

Fixed Issues

  • FileReference size and creationDate throws IO Error (FP-4198482)
  • Multiple security and functional fixes

Known Issues

  • 2.5D rotation: rotationX and rotationY rendering issues (FP-4198483)

 

 

Current Flash Player users who have enrolled in the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to Flash Player 26 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:  26.0.0.151

Flash Player 26 Windows for Firefox and other Netscape Compatible Browsers - NPAPI: 26.0.0.151

Flash Player 26 Windows for Opera and Chromium Based Browsers - PPAPI: 26.0.0.151

 

Flash Player 26 Windows for Google Chrome - PPAPI: 26.0.0.151

 

Flash Player 26 for Internet Explorer on Windows 8.1 (64-bit machine): 26.0.0.151

Flash Player 26 for Internet Explorer on Windows 8.1 (32-bit machine): 26.0.0.151

 

Flash Player 26 Windows for Internet Explorer and Edge on Windows 10 - ActiveX: 26.0.0.151

 

Flash Player 26 Mac for Safari, Firefox and other Netscape Compatible Browsers - NPAPI: 26.0.0.151

Flash Player 26 Mac for Opera and Chromium Based Browsers - PPAPI: 26.0.0.151

 

Flash Player 26 Mac for Google Chrome - PPAPI: 26.0.0.151

 

Flash Player 25 desktop for Linux (NPAPI): 26.0.0.151

Flash Player 25 desktop for Linux Chromium (PPAPI): 26.0.0.151

 

 

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.

11/23/2017 - Beta - AIR 28.0.0.120

$
0
0

Welcome to the AIR Runtime and SDK version 28 beta!  We've been hard at work adding new features to AIR and we're looking forward to receiving feedback from our development community.

This beta release includes new features as well as enhancements and bug fixes related to security, stability, performance, and device compatibility for AIR Runtime and SDK 28.  For full details, please see our release notes

New and Updated Features

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/sw ift/iphoneos for iOS

<dynamic_swift_framework>

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

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

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

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

iOS SDK Upgrade

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

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

Launch Xcode 9.

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

 

xcassests 1.jpeg

 

  1. Drag and drop iPad App icon of size 76x76 (76pt, 1x) & 152x152 (76pt, 2x).
  2. Drag and drop iPad Pro App icon of size 167x167 (83.5pt, 2x).
  3. Drag and drop iPhone App icon of size 120x120 (60pt, 2x).
  4. Drag and drop iPhone App icon of size 180x180 (60pt, 3x).

 

XCAssets 2.png

  1. In the drop-down select Generic iOS Device as the build target.
  2. Build the project ( Project -> Build).
  3. Right-click on your ‘.app’ -> Show in finder.
  4. Right click on your ‘.app’ -> Show package contents.
  5. 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. 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 below mentioned command to package a sample application using 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:

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 Platform25 ver 3 (Android 7.1.1)
Android SDK build tools26.0.1
Android SDK tools26.0.2
Android SDK platform tools26.0.0
Android NDK15.1.4119039
Android Support Repository47.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 needtobeadded in 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>:Applicationissupported on Android TV and it will reflect on the home screen of Android TV after the installation.

<supportsAndroidTV>false</supportsAndroidTV>:Applicationisnot 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 thetagwhereusercangivethe 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. Incasedeveloperdoesnot providethe 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 <SampleCertif

 

Notes:

  • Embeddingbitcodeenables AIR developers to upload their tvOS applications on the AppStorewherebitcodeisrequired.
  • Embeddingbitcodein your application increases both application size and packaging time.
  • Embeddingbitcoderequires that all your ANEsalsoincludebitcode. If not present,adtcanthrowpackaging errors such as the following:

ld: bitcode bundle could not be generated because '/var/folders/d3/yxwv5yn5715fk31lq36lnk780000gn/T/805ef2d4-5fe2-4ec9-a773-a3cc39845fa1/li b.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 builtwithtvOS 11 SDK, which enables AIR developers to use ANEs builtwithtvOS 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 anyuserinvokedaction, 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/AudioDevic eManager.html

Sample Snippet :

Access system available audio device names

 

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

 

Select an audio output device

 

var audio_device_manager:AudioDeviceManager = AudioDeviceManager.audioDeviceManager;
audio_device_manager.selectedDeviceIndex = desired_audio_output_index;

 

Monitor audio output change

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

 

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

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

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

<application>

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

</application>

 

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

Known Issues

  • [iOS] Missing entry for IpadPro10.5Inch - therefore incorrect screen size returned (AIR-4198511)
  • Flash Builder quits unexpectedly on High Sierra when "Export release build" is selected from the Project menu.
  • GESTURE_PAN event is not triggered on Mac
  • Some rendering issues related to direct render mode are known for e.g. BitmapData, CacheAsBitmap, cacheAsBitmapMatrix, PerspectiveTransform and related areas.
  • [Android] Stage shift offset error on StageText focus (AIR-4198421)
  • [Android] Banner.png is missing from apk packaged for Android TV
  • [Android] Camera miniature display at top-left corner when StageVideo video playback (AIR-4130641)

Fixed Issues

  • [Android] KeyboardEvent.KEY_DOWN dispatched twice for NEXT button (AIR-4198503)
  • AIR runtime quits unexpectedly after graphics.readGraphicsData when 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)
  • Bitmap glitches are observed while drawing pixels(AIR-4198453)
  • [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)

Authoring for Flash Player 28 and AIR 28

  • Update application descriptor namespace to 28
  • SWF version should be 39

System Requirements

For system requirements of the current release of AIR in production, visithttp://www.adobe.com/products/air/systemreqs/

About the Beta Channel

To get the latest Beta build of AIR Runtime and SDK visit Adobe labs

If you would like real-time notification for announcements related to the AIR Beta Channel please follow the Flash Runtime Announcements forums by choosing "Follow this forum" from the right-hand menu on the Forums page.

2/22/2018 - Beta - AIR 29.0.0.108

$
0
0

Welcome to the AIR Runtime and SDK version 29 beta!  We've been hard at work adding new features to AIR and we're looking forward to receiving feedback from our development community.

This beta release includes new features as well as enhancements and bug fixes related to security, stability, performance, and device compatibility for AIR Runtime and SDK 29.  For full details, please see our release notes

New and Updated 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 for WHEN_IN_USE permission, you can request for 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 see https://developer.apple.com/documentation/corelocation/choosing_the_authorization_level_fo r_location_services/requesting_always_authorization

Media AutoPlay for Android and iOS

With AIR 29, we have made some changes to 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 as 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 Version8.1
SDK Platform27
SDK Tool26.1.1
Android Build Tool27.0.3
Platform Tool27.0.1
Android Support Repository47.0.0
Android Google Repository58
LLDB3.0
Android Emulator27.0.5
Gradle plugin version for Android3.0.1
Multidex jar1.0.2

Combined Windows 32-bit and 64-bit AIR SDK

Earlier, separate AIR SDKs were made available over Windows for packaging 32-bit and 64-bit AIR applications. The AIR SDK for 64-bit AIR applications had the functionality to package 64-bit captive applications only. AIR 29 onwards, a combined AIR SDK for packaging 32-bit and 64-bit captive AIR applications is made available for Windows.

Deciding the architecture of AIR applications

The decision 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 decision will be 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 decision can be made 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 Windows8.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/a20d4773459b01e86acceac4524 0a2b4e88f67e3

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(Beta Only)

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(Beta Only)

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 beta(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.

Known Issues

  • Air apps quit unexpectedly when bytearray is attached to domainMemory(AIR-4198585)
  • Video flickers with containsVideo=true (AIR-4130641)
  • [Mac]GESTURE_PAN event is not fired.(AIR-4198492)

Fixed Issues

  • 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)
  • Asynchronous texture upload fails after uploading more than 6500 texture(AIR-4198527)
  • [Android]Incomplete textures are rendered when uploading large textures.(AIR-4198475)
  • Flash Builder quits unexpectedly on High Sierra when "Export release build" is selected from the Project menu.
  • Unexpected margin at the top of StageWebView on iOS 11 (AIR-4198537)
  • clipboard.dataForFormat returns null for Custom data in the Clipboard(AIR-4198553).
  • Asynchronous texture upload fails after uploading 5000 texture(AIR-4198527)
  • Various cases of SWF loading in HTML fail on AIR 64 bit Windows
  • Packaging 64-bit captive app results in error through adt.bat
  • The launch of two AIR captive apps simultaneously packaged with windows 64-bit runtime causes the second app to quit unexpectedly.
  • ATF texture with LZMA compressions is not rendering.
  • 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)

Authoring for Flash Player 29 and AIR 29

  • Update application descriptor namespace to 29
  • SWF version should be 40

System Requirements

For system requirements of the current release of AIR in production, visithttp://www.adobe.com/products/air/systemreqs/

About the Beta Channel

To get the latest Beta build of AIR Runtime and SDK visit Adobe labs

If you would like real-time notification for announcements related to the AIR Beta Channel please follow the Flash Runtime Announcements forums by choosing "Follow this forum" from the right-hand menu on the Forums page.

7/27/2016 - Beta - AIR 23.0.0.215

$
0
0

Welcome to the latest AIR Runtime and SDK version 23 beta!  We've been hard at work adding new features to AIR and we're looking forward to receiving feedback from our development community.

This beta release includes new features as well as enhancements and bug fixes related to security, stability, performance, and device compatibility for AIR Runtime and SDK 23.  For full details, please see our release notes

New and Updated Features

The StageText clear button is now optional on iOS

While creating StageText object on iOS, a clear button option is available by default to the AS developers.

Beginning with AIR 23, a new feature has been introduced, which makes the StageText clear button optional. This provides more flexibility to the AS developers when using StageText. In the earlier versions, StageText object was created with an integrated clear button.

To implement this feature, following changes are required in the ActionScript code:

stageText.clearButtonMode

For getting access to the optional clear button support, AS developers can now use a clearButtonMode property to set different modes. There are four modes associated with this property:

  •    To show clearButton while editing: StageTextClearButtonMode.WHILE_EDITING
  •    To never show clearButton: StageTextClearButtonMode.NEVER
  •    To always show clearButton: StageTextClearButtonMode.ALWAYS
  •    To show clearButton unless editing: StageTextClearButtonMode.UNLESS_EDITING

 

By default,  clearButtonMode property is set as StageTextClearButtonMode.WHILE_EDITING

 

Requirements

  • The application must be packaged with latest AIR SDK (version 23).
  • SWF version must be 34 or later.

 

Sample snippet

 

You can use this example code snippet for your reference.

 

public function ClearButtonMode()

{

label = new StageText();

label.clearButtonMode = StageTextClearButtonMode.NEVER;

label.textAlign = "right";

label.stage = stage;

label.viewPort = new Rectangle(20, 20, 90, 90);

}

 

Limitations for using stageText.clearButtonMode property     

 

  • This property is not available in StageText with multi-line  
  • This property is a No-Op for Android           

Win: Add HiDPI support for AIR desktop (Release)

 

Beginning with AIR 23, HiDPI support for AIR Desktop on Windows has been introduced. It allows you to provide a higher quality rendering for AIR content on HiDPI displays. This feature works on the concept of higher pixel density scaling instead of pixel-doubling scaling.

 

Note: HiDPI is already available for AIR on Mac Retina displays.

 

To implement this feature in an AIR app, the developer should set requestedDisplayResolution as high in the manifest file.

  • requestedDisplayResolution set high
    <requestedDisplayResolution>high</requestedDisplayResolution>

Known Issues

  • [Windows] ADL becomes unresponsive when manipulating frame tree of a new frame, before it has been installed in a frame tree (4175625)
  • [Android] softKeyboardRect height is incorrect (4085072)
  • [iOS 10] Apps are not visible on devices once installed using adt -installApp command
  • [iOS] VideoTexture on iOS - sometimes the event TEXTURE_READY isn't dispatched (4150401)
  • [iOS] Capabilities.screenDPI gives a wrong value on AIR 22 simulator (4157457)
  • [iOS] Context3D.drawToBitmapData uses wrong offset on mobile (4147414)
  • [iOS] Crash when trying to access function arguments (4117964)
  • [iOS] Landscape mode is not able to initiate the camera and the app crashes in debug mode (4168916)
  • [iOS] TextField with TextFieldType.INPUT cuts off text on the left side when focused (4009346)

Fixed Issues

  • [Android] OpenSSL library upgraded to 1.0.2h version
  • [iOS] App using concurrency closes when a class is instantiated on the worker .swf (4067035)
  • [iOS] CameraRoll on iOS returns Bitmap in incorrect orientation (4070057)
  • [iOS] sharedobjects fail when available storage is low (3711301)
  • [iOS] [Windows] Error, ld: in section __TEXT,__text reloc 153: R_ABS reloc but no absolute symbol at target address for architecture arm64 while packaging Application with Social.ane using flag -hideAneLibSymbols yes  (4005515)

Authoring for Flash Player 23 and AIR 23

  • Update application descriptor namespace to 23
  • SWF version should be 34

System Requirements

For system requirements of the current release of AIR in production, visit http://www.adobe.com/products/air/systemreqs/

About the Beta Channel

To get the latest Beta build of AIR Runtime and SDK visit Adobe labs

If you would like real-time notification for announcements related to the AIR Beta Channel please follow the Flash Runtime Announcements forums by choosing "Follow this forum" from the right-hand menu on the Forums page.

12/08/2016 - Beta - Flash 24.0.0.178

$
0
0

Welcome to the Flash Runtime version 24 updated beta!  We've been hard at work adding new features to Flash Player and we're looking forward to receiving feedback from our Flash Player community.

 

This beta release includes new features as well as enhancements and bug fixes related to security, stability, performance, and device compatibility for Flash Player 24.  For full details, please see our release notes.

Note:

  • The ActiveX Flash Player in this release is not compatible with Windows® 8.x or 10
  • Flash Player for Windows® 8.x/10 is available as part of the generally available Windows® 8.x/10 update

New and Updated Features

Spherical video support in Flash and AIR

Spherical videos support is added to both Flash Player and AIR from version 24 onward. Spherical videos have a specific meta-data attached to them, which can now be retrieved using the new property provided by the feature. This feature supports equirectangular projection type of videos conforming to https://github.com/google/spatial-media/blob/master/docs/spherical-video-rfc.md.

This feature is supported on Desktop and Android devices.

API introduced

The Object parameter of the onMetaData event provides video metadata information. The feature adds new properties to the parameter. The added property is an array of string type in XML format. Refer code below.

 

functionns_onMetaData(info:Object):void{

trace("The matrix of Movie Header Box:"+info.sphericalVideoInfo[0]); // info.sphericalVideoInfo provides the related meta-data

}

Sample Spherical Video Player

A sample project for Spherical video player can be downloaded from this link in order to understand the use of the metadata to render the spherical video. The sample code makes use of an instance of the context3D, where VideoTexture is used to render video for better performance.

See the following chart for ActionScript classes in the project.

Spherical Video.png

 

SampleSphericalVideoPlayer class

This class provides basic controls for the Spherical video functionality.

SphericalVideo class

This class creates the context3D instance to render spherical video using VideoTexture

Projection classes

These classes are used for generating vertices and indices corresponding to the projection type used.

Improved support for high resolution displays on Firefox for Windows

Beginning with Flash Player version 24 and Firefox version 51 on Windows, Flash content will now scale appropriately on high resolution displays.

Separate HTTP and HTTPS permissions for Camera and Microphone

To provide users with a better control over their camera and microphone data, Flash Player now provides a more fine-grained control over how permissions are granted. Users can now allow camera and microphone access for a domain when that content is served via HTTPS, and disallow the access when content from the domain is served over HTTP. Since this feature is currently in beta, the settings will not be visible in the Global settings Manager.

Known Issues

  • None

Fixed Issues

  • "The Last Stand Dead Zone" game is not loading when Flash protected mode is turned OFF(4197247)
  • Enabling async drawing shows boundaries for transparent object (4196843).
  • Worker is taking more time to write object in a shared byte array (4170367).
  • "ALT GR+0" Does not return @ on french layout Keyboard(4196791)
  • Blank screen is observed until mouse click received after enabling Async drawing (4197066).
  • Scaling the swf does not trigger a corresponding scaling of the hit area of elements in browser(4197425).

System Requirements

For system requirements of the current release of Flash Player in production, please visithttp://www.adobe.com/products/flashplayer/systemreqs/

About the Beta Channel

To get the latest Beta build of Flash Player visit Adobe labs

Beta versions of Flash Player are also available for automatic installation via our Background Update service.  Please subscribe to automatically receive update notifications for future Flash Runtime announcements.

Note: If you are having issues downloading Flash Player, it may be because of a cache or locale issue. Wait for 24 hours before retrying and if you still face issues, please post the issue in Flash Player forum


08/03/2017 - Beta - Flash 27.0.0.96 (Win & Mac)

$
0
0

Welcome to the Flash Runtime version 27 beta!  We've been fixing important bugs for Flash Player and we're looking forward to receiving feedback from our Flash Player community.

 

This beta release includes enhancements and bug fixes related to security, stability, performance, and device compatibility for Flash Player 27.  For full details, please see our release notes.

 

Note:

  • The ActiveX Flash Player in this release is not compatible with Windows® 8.x or 10
  • Flash Player for Windows® 8.x/10 is available as part of the generally available Windows® 8.x/10 update
  • Flash Player Linux builds have not been updated on Adobe Labs

New and Updated Features

None

Known Issues

  • N/A

Fixed Issues

  • N/A

 

Authoring for Flash Player 27 and AIR 27

  • Update application descriptor namespace to 27
  • SWF version should be 38

System Requirements

For system requirements of the current release of Flash Player in production, please visithttp://www.adobe.com/products/flashplayer/systemreqs/

About the Beta Channel

To get the latest Beta build of Flash Player visit Adobe labs

3/12/2015 - Release - Flash Player 17

$
0
0

The next version of Flash Player is available for immediate download.  In today's release we've updated Flash Player with new functionality, critical security fix.  We recommend all users update to the latest version.

 

Security update details can be found here: Security Bulletin (APSB15-05)

 

New Features for Flash Player 17:


  • Control Panel Improvements

The system control panel will now display the currently installed version of the ActiveX, NPAPI, and PPAPI plugins.  We've also clarified how Chrome and Chromium (PPAPI) users can edit their Flash Player settings.

 

  • Installer Improvements - Mac

The Mac installer will no longer request users close the Chrome browser during installation.  In future versions we'll work to further improve the user experience of our installers.


For complete information please see our release notes.



Fixed Issues

  • CrossBridge applications break after FP version >= 16.(3938269)
  • [Chromium 394217] Wrong text displayed with embedded fonts.(3782659)
  • Multiple security and stability fixes

 

 

Current Flash Player desktop users that have enrolled in the "Allow Adobe to install updates (recommended)" or the "Notify me to install updates" update options will receive an update notification dialog within 7 days from today (please note that Windows users will need to restart their system to receive the notification dialog.)

 

Please note that both Flash Player for Google Chrome and Microsoft Internet Explorer for Windows 8.x are updated using different mechanisms.  Flash Player for Google Chrome updates will occur during regular Chrome updates.  Flash Player updates for Internet Explorer on Windows 8.x will be provided by Microsoft though the Windows automatic update feature.

 

If you would like to install the update immediately, please use one of the links below:

 

Flash Player 17 Windows for Internet Explorer - ActiveX: 17.0.0.134

Flash Player 17 Windows for Firefox and other Netscape Compatible Browsers - NPAPI: 17.0.0.134

Flash Player 17 Windows for Opera 26 and Chromium Based Browsers - PPAPI: 17.0.0.134

 

Flash Player 17 for Internet Explorer on Windows 8.1 (64-bit machine): 17.0.0.134

Flash Player 17 for Internet Explorer on Windows 8.1 (32-bit machine): 17.0.0.134

Flash Player 17 for Internet Explorer on Windows 8 (64-bit machine): 17.0.0.134

Flash Player 17 for Internet Explorer on Windows 8 (32-bit machine): 17.0.0.134

 

Flash Player 17 Mac for Safari, Firefox and other Netscape Compatible Browsers - NPAPI: 17.0.0.134

Flash Player 17 Mac for Opera 26 and Chromium Based Browsers - PPAPI: 17.0.0.134

 

Flash Player 11.2 desktop for Linux (NPAPI): 11.2.202.451

 

Flash Player 13 Extended Support Release for Windows and Macintosh: 13.0.0.277

 

Previous versions of Flash Player can be found on the Flash Player Archive page

 

If you encounter a problems 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.

3/23/2016 - Release - Flash Player 21

$
0
0

In today's release, we've updated Flash Player with an important bug fix that was affecting a subset of Flash gaming content.  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.  Please note that this release is not available for the ActiveX Flash Player on Windows 8.1 and Windows 10.

 

The most recent Flash Player security bulletin can be found here: Security Bulletin (APSB16-08)

 

New Features for Flash Player 21:

 

  • GPU Memory Information In Context3D

When a Context3D object is created, developers allocate memory for various Stage3D structures which include index buffers, vertex buffers, textures, and programs. Prior to Flash and AIR 21, the only way to verify the memory allocated by the current Context3D is through values displayed by Scout. With the release of Flash Player and AIR 21, a new property of context3D class called "totalGPUMemory" has been introduced which provides the sum of gpu memory used by the index buffers, vertex buffers, textures, and programs created through Context3D.

 

The total value can be obtained by property "Context3D.totalGPUMemory;".

 

The value of this property is in bytes and its default value is 0.  The information is only provided in direct mode on mobile and in direct and GPU mode on desktop ( On desktop computers, using <renderMode>gpu</renderMode> will fallback to <renderMode>direct</renderMode>).  This property can be used when the SWF version is 32 or more .

 

  • Support for Browser Zoom Factor in Firefox

We’ve extended the support for Browser Zoom Feature that proposes scaling of Flash content in the web browser in response to web page zoom factor change. The feature is already available for the ActiveX and PPAPI plugin (link).

 

It will be available from FP version 21 and is currently available on Firefox Nightly 45.0a1, the official Firefox version supporting the feature has yet to be announced.


  • PPAPI vector printing on OSX

As of Flash Player version 19, Vector Printing has only been available for NPAPI while PPAPI supported only bitmap printing. Hence there was an observable difference in printing quality between NPAPI and PPAPI (with NPAPI being better). Now in version 21, we have introduced vector printing for PPAPI for OSX, thus giving a better printing experience from PPAPI supported browsers and applications.  The bitmap printing functionality will continue to be supported and used when requested by the content.

 

  • Simplified LSO UI

Flash player provides an per domain/swf option to store locally shared objects on user's system. In the past, users could specify the size up to which a domain or SWF could save their LSOs on their machine. We have now simplified the LSO UI Options.  This Simple LSO feature will change the permission scheme and related dialogs to only allow/deny and universally imposes a rational upper limit to the LSO size. End users will no longer be able to specify the size of LSOs (but will be able to approve if LSOs can be created or not).


 

For complete information please see our release notes.



Fixed Issues

  • Significant performance degradation while reading/writing LSOs [4127545]

 

 

Current Flash Player users who have enrolled in the "Allow Adobe to install updates (recommended)" update mechanism will be automatically updated to Flash Player 21 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 21 Windows for Internet Explorer - ActiveX: 21.0.0.197

Flash Player 21 Windows for Firefox and other Netscape Compatible Browsers - NPAPI: 21.0.0.197

Flash Player 21 Windows for Opera and Chromium Based Browsers - PPAPI: 21.0.0.197

 

Flash Player 21 for Internet Explorer on Windows 8.1 (64-bit machine): 21.0.0.182

Flash Player 21 for Internet Explorer on Windows 8.1 (32-bit machine): 21.0.0.182

 

Flash Player 21 Windows for Internet Explorer and Edge on Windows 10 - ActiveX: 21.0.0.182

 

Flash Player 21 Mac for Safari, Firefox and other Netscape Compatible Browsers - NPAPI: 21.0.0.197

Flash Player 21 Mac for Opera 26 and Chromium Based Browsers - PPAPI: 21.0.0.197

 

Flash Player 11.2 desktop for Linux (NPAPI): 11.2.202.577

 

Flash Player 18 Extended Support Release for Windows and Macintosh - NPAPI : 18.0.0.333

Flash Player 18 Extended Support Release for Windows - ActiveX : 18.0.0.333

 

Previous versions of Flash Player can be found on the Flash Player Archive page

 

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.

11/4/2016 - Beta - Flash 24.0.0.145

$
0
0

Welcome to the Flash Runtime version 24 updated beta!  We've been hard at work adding new features to Flash Player and we're looking forward to receiving feedback from our Flash Player community.

This beta release includes new features as well as enhancements and bug fixes related to security, stability, performance, and device compatibility for Flash Player 24.  For full details, please see our release notes.

Note:

  • The ActiveX Flash Player in this release is not compatible with Windows® 8.x or 10
  • Flash Player for Windows® 8.x/10 is available as part of the generally available Windows® 8.x/10 update

New and Updated Features

Spherical video support in Flash and AIR

Spherical videos support is added to both Flash Player and AIR from version 24 onward. Spherical videos have a specific meta-data attached to them, which can now be retrieved using the new property provided by the feature. This feature supports equirectangular projection type of videos conforming to https://github.com/google/spatial-media/blob/master/docs/spherical-video-rfc.md.

This feature is supported on Desktop and Android devices.

API introduced

The Object parameter of the onMetaData event provides video metadata information. The feature adds new properties to the parameter. The added property is an array of string type in XML format. Refer code below.

 

functionns_onMetaData(info:Object):void{

trace("The matrix of Movie Header Box:"+info.sphericalVideoInfo[0]); // info.sphericalVideoInfo provides the related meta-data

}

Sample Spherical Video Player

A sample project for Spherical video player can be downloaded from this link in order to understand the use of the metadata to render the spherical video. The sample code makes use of an instance of the context3D, where VideoTexture is used to render video for better performance.

See the following chart for ActionScript classes in the project.

Spherical Video.png

SampleSphericalVideoPlayer class

This class provides basic controls for the Spherical video functionality.

SphericalVideo class

This class creates the context3D instance to render spherical video using VideoTexture

Projection classes

These classes are used for generating vertices and indices corresponding to the projection type used.

Flash Player PPAPI & NPAPI for Linux

With this beta we are providing additional binaries (32 and 64 bit in tar.gz and RPM installers)  for NPAPI and PPAPI Linux and Standalone Player for Linux 64bit.

Improved support for high resolution displays on Firefox for Windows

Beginning with Flash Player version 24 and Firefox version 51 on Windows, Flash content will now scale appropriately on high resolution displays.

Separate HTTP and HTTPS permissions for Camera and Microphone

To provide users with a better control over their camera and microphone data, Flash Player now provides a more fine-grained control over how permissions are granted. Users can now allow camera and microphone access for a domain when that content is served via HTTPS, and disallow the access when content from the domain is served over HTTP. Since this feature is currently in beta, the settings will not be visible in the Global settings Manager.

Known Issues

  • Performance drop is observed on Firefox 49.0.2 when async drawing is enabled.(4197072)
  • Enabling async drawing shows boundaries for transparent object (4196843).
  • Blank screen is observed until mouse click received after enabling Async drawing (4197066).
  • "ALT GR+0" Does not return @ on french layout Keyboard(4196791).
  • "Installation Failed" error is observed on Mac 10.7 for all browsers (4186587).

Fixed Issues

  • Flash Player quits unexpectedly while playing  http://www.evil3d.cn/example/ (4195719)
  • Black screen is observed when video is seeking on Chrome(4186499).
  • Seek bar does not appear on hovering mouse cursor on video(4186564).
  • Action Script is unable to handle MOUSE_MOVE event(4186547).

System Requirements

For system requirements of the current release of Flash Player in production, please visithttp://www.adobe.com/products/flashplayer/systemreqs/

About the Beta Channel

To get the latest Beta build of Flash Player visit Adobe labs

Beta versions of Flash Player are also available for automatic installation via our Background Update service.  Please subscribe to automatically receive update notifications for future Flash Runtime announcements.

Note: If you are having issues downloading Flash Player, it may be because of a cache or locale issue. Wait for 24 hours before retrying and if you still face issues, please post the issue in Flash Player forum

11/11/2016 - Beta - Flash 24.0.0.154

$
0
0

Welcome to the Flash Runtime version 24 updated beta!  We've been hard at work adding new features to Flash Player and we're looking forward to receiving feedback from our Flash Player community.

This beta release includes new features as well as enhancements and bug fixes related to security, stability, performance, and device compatibility for Flash Player 24.  For full details, please see our release notes.

Note:

  • The ActiveX Flash Player in this release is not compatible with Windows® 8.x or 10
  • Flash Player for Windows® 8.x/10 is available as part of the generally available Windows® 8.x/10 update

New and Updated Features

Spherical video support in Flash and AIR

Spherical videos support is added to both Flash Player and AIR from version 24 onward. Spherical videos have a specific meta-data attached to them, which can now be retrieved using the new property provided by the feature. This feature supports equirectangular projection type of videos conforming to https://github.com/google/spatial-media/blob/master/docs/spherical-video-rfc.md.

This feature is supported on Desktop and Android devices.

API introduced

The Object parameter of the onMetaData event provides video metadata information. The feature adds new properties to the parameter. The added property is an array of string type in XML format. Refer code below.

 

functionns_onMetaData(info:Object):void{

trace("The matrix of Movie Header Box:"+info.sphericalVideoInfo[0]); // info.sphericalVideoInfo provides the related meta-data

}

 

Sample Spherical Video Player

A sample project for Spherical video player can be downloaded from this link in order to understand the use of the metadata to render the spherical video. The sample code makes use of an instance of the context3D, where VideoTexture is used to render video for better performance.

 

See the following chart for ActionScript classes in the project.

/servlet/JiveServlet/downloadImage/2-9113257-1056748/Spherical+Video.png

Spherical Video.png

SampleSphericalVideoPlayer class

This class provides basic controls for the Spherical video functionality.

SphericalVideo class

This class creates the context3D instance to render spherical video using VideoTexture

Projection classes

These classes are used for generating vertices and indices corresponding to the projection type used.

Flash Player PPAPI & NPAPI for Linux

With this Beta we are providing Standalone content Debugger for Linux 64bit.

Improved support for high resolution displays on Firefox for Windows

Beginning with Flash Player version 24 and Firefox version 51 on Windows, Flash content will now scale appropriately on high resolution displays.

Separate HTTP and HTTPS permissions for Camera and Microphone

To provide users with a better control over their camera and microphone data, Flash Player now provides a more fine-grained control over how permissions are granted. Users can now allow camera and microphone access for a domain when that content is served via HTTPS, and disallow the access when content from the domain is served over HTTP. Since this feature is currently in beta, the settings will not be visible in the Global settings Manager.

Known Issues

  • Significant performance degradation in Flash Player 23 in comparison to Flash Player 22 when instantiating Shape(4197421)
  • Performance drop is observed on Firefox 49.0.2 when async drawing is enabled.(4197072)
  • Enabling async drawing shows boundaries for transparent object (4196843).
  • Blank screen is observed until mouse click received after enabling Async drawing (4197066).
  • "ALT GR+0" Does not return @ on french layout Keyboard(4196791).
  • "Installation Failed" error is observed on Mac 10.7 for all browsers (4186587).

Fixed Issues

  • Flash Player quits unexpectedly while playing  http://www.evil3d.cn/example/ (4195719)
  • Black screen is observed when video is seeking on Chrome(4186499).
  • Seek bar does not appear on hovering mouse cursor on video(4186564).
  • Action Script is unable to handle MOUSE_MOVE event(4186547).

System Requirements

For system requirements of the current release of Flash Player in production, please visithttp://www.adobe.com/products/flashplayer/systemreqs/

About the Beta Channel

To get the latest Beta build of Flash Player visit Adobe labs

Beta versions of Flash Player are also available for automatic installation via our Background Update service.  Please subscribe to automatically receive update notifications for future Flash Runtime announcements.

Note: If you are having issues downloading Flash Player, it may be because of a cache or locale issue. Wait for 24 hours before retrying and if you still face issues, please post the issue in Flash Player forum

11/23/2016 - Beta - Flash 24.0.0.170

$
0
0

Welcome to the Flash Runtime version 24 updated beta!  We've been hard at work adding new features to Flash Player and we're looking forward to receiving feedback from our Flash Player community.

This beta release includes new features as well as enhancements and bug fixes related to security, stability, performance, and device compatibility for Flash Player 24.  For full details, please see our release notes.

Note:

  • The ActiveX Flash Player in this release is not compatible with Windows® 8.x or 10
  • Flash Player for Windows® 8.x/10 is available as part of the generally available Windows® 8.x/10 update

New and Updated Features

Spherical video support in Flash and AIR

Spherical videos support is added to both Flash Player and AIR from version 24 onward. Spherical videos have a specific meta-data attached to them, which can now be retrieved using the new property provided by the feature. This feature supports equirectangular projection type of videos conforming to https://github.com/google/spatial-media/blob/master/docs/spherical-video-rfc.md.

This feature is supported on Desktop and Android devices.

API introduced

The Object parameter of the onMetaData event provides video metadata information. The feature adds new properties to the parameter. The added property is an array of string type in XML format. Refer code below.

 

functionns_onMetaData(info:Object):void{

trace("The matrix of Movie Header Box:"+info.sphericalVideoInfo[0]); // info.sphericalVideoInfo provides the related meta-data

}

 

Sample Spherical Video Player

A sample project for Spherical video player can be downloaded from this link in order to understand the use of the metadata to render the spherical video. The sample code makes use of an instance of the context3D, where VideoTexture is used to render video for better performance.

See the following chart for ActionScript classes in the project.

Spherical Video.png

SampleSphericalVideoPlayer class

This class provides basic controls for the Spherical video functionality.

SphericalVideo class

This class creates the context3D instance to render spherical video using VideoTexture

Projection classes

These classes are used for generating vertices and indices corresponding to the projection type used.

Improved support for high resolution displays on Firefox for Windows

Beginning with Flash Player version 24 and Firefox version 51 on Windows, Flash content will now scale appropriately on high resolution displays.

Separate HTTP and HTTPS permissions for Camera and Microphone

To provide users with a better control over their camera and microphone data, Flash Player now provides a more fine-grained control over how permissions are granted. Users can now allow camera and microphone access for a domain when that content is served via HTTPS, and disallow the access when content from the domain is served over HTTP. Since this feature is currently in beta, the settings will not be visible in the Global settings Manager.

Known Issues

  • None

Fixed Issues

  • Enabling async drawing shows boundaries for transparent object (4196843).
  • Worker is taking more time to write object in a shared byte array (4170367).
  • "ALT GR+0" Does not return @ on french layout Keyboard(4196791)
  • Blank screen is observed until mouse click received after enabling Async drawing (4197066).
  • Scaling the swf does not trigger a corresponding scaling of the hit area of elements in browser(4197425).

System Requirements

For system requirements of the current release of Flash Player in production, please visithttp://www.adobe.com/products/flashplayer/systemreqs/

About the Beta Channel

To get the latest Beta build of Flash Player visit Adobe labs

Beta versions of Flash Player are also available for automatic installation via our Background Update service.  Please subscribe to automatically receive update notifications for future Flash Runtime announcements.

Note: If you are having issues downloading Flash Player, it may be because of a cache or locale issue. Wait for 24 hours before retrying and if you still face issues, please post the issue in Flash Player forum

12/13/2016 - Release - AIR 24 Runtime and SDK

$
0
0

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 24.  Please see our release notes for full details.

 

 

New Features:

Support for Android App Links

Starting AIR 24, Developers can use Android App Links that allows app developers to associate an application with a web domain they own. The Android App Links feature allows your app to become the default handler for the website URIs you specify in your app.xml

Follow the below steps to get your application ready for App Links:

 

1. Create Intent filter for URI in app.xml

To enable your app to handle links, use intent filters in your app.xml under manifest to declare the URI patterns that your app handles. The following example shows an intent filter that can handle links to https://www.example.in and http://www.example.in

<manifestAdditions>

    <![CDATA[

        <manifest android:installLocation="auto">

                ...

            ...

            <application android:enabled="true">

            <activity android:excludeFromRecents="false">

                <intent-filter>

                    <action android:name="android.intent.action.MAIN"/>

                    <categoryandroid:name="android.intent.category.LAUNCHER"/>

                </intent-filter>

                   

                <intent-filter android:autoVerify="true">

                    <action android:name="android.intent.action.VIEW"/>

                    <category android:name="android.intent.category.DEFAULT"/>

                    <category android:name="android.intent.category.BROWSABLE"/>

                    <data android:scheme="http"android:host="www.example.in"/>

                    <data android:scheme="https"android:host="www.example.in"/>

                </intent-filter>

            </activity>

            </application>

        </manifest>

    ]]>

</manifestAdditions>

 

As shown above, intent filters for app links must declare an android:scheme value of http, https, or both. The filter must not declare any other schemes. To enable link verification for your app, set the android:autoVerify attribute to true on at least one of the web URI intent filters in your app manifest. Read more about the intent filter here.

 

2. Publish a Digital Asset Links JSON file on your websites to provide verification

Follow the steps mentioned here to create assetlinks.json file and publishing the same on your website.

Note:  Developers can receive the url and its arguments in the ActionScript code by registering for NativeApplication InvokeEvent(e.g. NativeApplication.nativeApplication.addEventListener(InvokeEvent.INVOKE, invokeHandler); ) To read more about the ActionScript InvokeEvent read here.

Spherical video support in AIR

Spherical videos support is added to both Flash Player and AIR from version 24 onward. Spherical videos have a specific meta-data attached to them, which can now be retrieved using the new property provided by the feature. This feature supports equirectangular projection type of videos conforming to https://github.com/google/spatial-media/blob/master/docs/spherical-video-rfc.md.

This feature is supported on Desktop and Android devices.

API introduced

The Object parameter of the onMetaData event provides video metadata information. The feature adds new properties to the parameter. The added property is an array of string type in XML format. Refer code below.

 

functionns_onMetaData(info:Object):void{

trace("The matrix of Movie Header Box:"+info.sphericalVideoInfo[0]);

// info.sphericalVideoInfo provides the related meta-data

}

 

Sample Spherical Video Player

A sample project for Spherical video player can be downloaded from this link in order to understand the use of the metadata to render the spherical video. The sample code makes use of an instance of the context3D, where VideoTexture is used to render video for better performance.

See the following chart for ActionScript classes in the project.

Spherical Video.png

SampleSphericalVideoPlayer class

This class provides basic controls for the Spherical video functionality.

SphericalVideo class

This class creates the context3D instance to render spherical video using VideoTexture

Projection classes

These classes are used for generating vertices and indices corresponding to the projection type used.

Android SDK Upgrade

Beginning with AIR 24, Android SDK (API Level 24) has been upgraded in the AIR Runtime.Important: If you upload an app on Google Play using AIR SDK 24 and default targetSdkVersion value as 24 in the application descriptor, Google Play does not allow uploading the next version of your app with AIR SDK 23 or earlier (see the error message below). Using targetSdkVersion value as 21 allows you to switch between AIR SDK 24 and AIR SDK 23 for your app updates.Error thrown by Google Play on uploading the next version of your app with AIR SDK 23 or earlier:
ErrorMessage.png

Here is the list of version numbers of the tools upgraded in AIR 24.

SDK Tool25.1.7
SDK Platform24
Platform Tool24.0.2
Android Support Repository36
Android Google Repository32
Android Build Tool24.0.1

 

Permissions on Android and iOS

Beginning with Android 6.0 (API level 23), the users now need to grant permissions to apps while it is running, not when they install the application. To handle the permissions requests and status, we have introduced Permissions API for Android and iOS. The developers can request permissions for classes like Camera, Microphone, Geolocation, CameraRoll, CameraUI, File, and FileReference. The applications must be packaged with AIRSDK 24 or greater and must have SWF version 35 or later. Apps built using these APIs throw a dialog only on Android 6.0 and later. For Android 5.0 or earlier, you can continue to mention permissions in the application descriptor file.

On Android, If you do not want to handle permissions in your application, use targetSdkVersion less than 23 in your application descriptor file.

  1. permissionStatus: This propertyinforms whether the application has been granted the required permission or not. This property always returns the status as GRANTED on AIR desktop and Android apps that have targetSDKVersion less than 23. The list of properties for PermissionStatus class includes UNKNOWN,GRANTED, and DENIED. The property UNKNOWN specifies that the permission hasn’t been requested yet or the permission has been denied by user with check box option 'Don’t ask again.'.
  2. requestPermission(): The method requestPermission requests for the permission to be granted to the application. A PermissionEvent is dispatched when the user grants or denies a permission.
  3. PermissionError: Accessing properties and methods of such ActionScript classes without requesting for permission throws Error #3800 PermissionError.
  • While requesting for multiple permissions simultaneously, runtime throws the error below:
    Error #3801: Another permission request is in progress.
  • Accessing the File class without requesting for permissions throws Error #3012, which is the old behavior of File API.

 

package

{

    importflash.display.Sprite;

    importflash.display.StageAlign;

    importflash.display.StageScaleMode;

    importflash.events.PermissionEvent;

    importflash.media.Camera;

    importflash.media.Video;

    importflash.permissions.PermissionStatus;

  

    publicclasscodeSnippet extendsSprite

    {

        privatevarvideo:Video;

        privatevarcam:Camera;

        publicfunctioncodeSnippet()

        {

            super();

          

            stage.align = StageAlign.TOP_LEFT;

            stage.scaleMode = StageScaleMode.NO_SCALE;

          

            if(Camera.isSupported)

            {

                cam = Camera.getCamera();

              

                if(Camera.permissionStatus != PermissionStatus.GRANTED)

                {

                    cam.addEventListener(PermissionEvent.PERMISSION_STATUS, function(e:PermissionEvent):void{

                        if(e.status == PermissionStatus.GRANTED)

                        {

                            connectCamera();

                        }

                        else

                        {

                            // permission denied

                        }

                    });

                  

                    try{

                        cam.requestPermission();

                    } catch(e:Error)

                    {

                        // another request is in progress

                    }

                }

                else

                {

                    connectCamera();

                }

            }

        }

      

        privatefunctionconnectCamera():void

        {

            video = newVideo(640, 480);

            video.attachCamera(cam);

            addChild(video);

        }

    }

}

 

For training resource on Android permissions, see https://developer.android.com/training/permissions/index.html.

For information about iOS permissions, see Apple's documentation https://developer.apple.com/ios/human-interface-guidelines/interaction/requesting-permissi on/.

Points to note

  • A new feature for iOS 10 submissions requires you to add the 'purpose string' to your app when accessing a user's private data such as Camera or Photos. For information about providing keys in your app descriptor file, see Information Property List Key Reference | Cocoa Keys.
  • While requesting for multiple permissions simultaneously, runtime throws the error below:
    Error #3801: Another permission request is in progress.
  • Accessing the File class without requesting for permissions throws Error #3012, which is the old behavior of File API.

Custom fonts support for StageText on iOS and Android

Beginning with AIR 24, we have introduced support for Custom fonts on StageText for iOS and Android. Earlier, StageText was created with specific system fonts. With the introduction of this feature, the AS developers now have more flexibility in using fonts apart from the ones present in system. The developers can use ttf and otf font files. The changes required to use custom fonts are listed below.

1. Changes required in the application descriptor xml.

Note: To access this functionality, the Namespace value in the app descriptor must be 24.0 or greater.

<application>

...

...

<embedFonts>

     <font>

          <fontName>FontID1</fontName>

          <fontPath>path_to_custom_font_fileName1.ttf</fontPath>

     </font>

     <font>

          <fontName>FontID2</fontName>

          <fontPath>path_to_custom_font_fileName2.ttf</fontPath>

     </font>

</embedFonts>

...

...

<application>

2. Changes required in the ActionScript code

The developers can provide any value under fontName tag, for example FontID1 here.

publicfunctionCustomFonts()

{

     label= newStageText();

     label.fontFamily = "FontID1";

     label.textAlign = "right";

     label.stage = stage;

     label.viewPort = newRectangle(20, 20, 90, 90);

}

Known Issues

  • For packaging the .apk file using Flash Builder, the developer needs to provide absolute fontPath.
  • With Java 1.6 on Windows, otf files are not rendered for IPAs.

Asynchronous texture upload for mobile

Till AIR 23, the texture upload was synchronous. Therefore, the developers had to wait till the new texture was uploaded successfully.

With AIR 24, 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 successful completion of 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:

  1. uploadFromBitmapDataAsync( source:BitmapData, miplevel:uint = 0)
  2. uploadFromByteArrayAsync( data:ByteArray, byteArrayOffset:uint, miplevel:uint = 0 )

This feature supports Normal and Rectangular texture for miplevel 0 only.

Anti-Aliasing using configureBackBuffer() on iOS

Anti-Aliasing is useful in improving the perceived image quality in applications. Hardware base Multisampling Anti-Aliasing (MSAA) is now available for iOS using Contex3D.configureBackBuffer.This feature was previously available for Desktop and Flash Player. To enable MSAA, set the level from 0 to 2 using the configureBackBuffer. The following are the effect of levels of antialiasing values:

0=1 subsample, No antialiasing

1=2 subsamples, medium antialiasing

2=4 subsamples, high antialiasing.

If you provide higher level of antialiasing (more than 2), the level will be clipped to either the maximum level of anti-aliasing supported by GPU or the value of 2.

Note: This feature is currently not available on Android using configureBackbuffer.

API assumptions and dependencies

  1. Anti-Aliasing is not available in software mode rendering.
  2. The application use extra GPU memory when using anti-aliasing and hence can cause slight performance degradation.

 

 

Fixed Issues

  • Starling.display.Image mask is not rendering on mobile when rendered with starling.textures.RenderTexture (4196946)
  • Exponential Increase in GDI object handler due to which application quits unexpectedly (4194045).
  • [Windows 7]Memory leak is observed when using Cairo and HTML5 canvas in AIR Desktop Runtime(4192545).
  • [Mac] Application quits unexpectedly on Mac with OS X exception (SIGSEGV) KERN_INVALID_ADDRESS(4195975).
  • [Mac] FLEX AIR application (digi.me) quits unexpectedly (4152837).
  • [Mac] AIR application quits unexpectedly on network changes or screen invalidation(4011481).
  • [Android N] AIR apps are not able to recognise display changes & font size as per the new Android N features (4186054)
  • Android - Status bar appears when soft keyboard opens and then stays indefinitely (4184348)
  • setAspectRatio(StageAspectRatio.PORTRAIT) doesnt work if the device is held in landscape orientation [4197162]
  • [iOS] Capabilities.cpuArchitecture returning wrong value for iOS Simulator [4142569]
  • [iOS] UIDeviceFamily values are now integers(4176499)
  • [Android] While using Android Video, video will hang for a second when other operations occur such ad addChild (4161877).
  • [Android]Video blacks out and only audio plays when user stops and restarts the video ( 4194916)
  • [Android] HLS video using video texture is not playing(4186193)
  • [iOS] Background sound stuttering when going idle (4184841).
  • [iOS] GameInput API now supports iOS8 devices.
  • [Android] While using immersive mode on devices having soft navigational keys, pink bar appears under that navigational area (4100625).
  • Circled Digit characters shown as boxes when used in a flex project inside <s:label> (4186628)

 

 

  Known Issues:

  • Adobe AIR_64 Helper and ExtendedAppEntry Template64 creates problem while code signing MAC Captive App.(4189809)
  • [iOS] Crash when trying to access function arguments (4117964)
  • TextField: delay after creation of first TextField (4133187)
  • [iOS] Failed to find class DTiPhoneSimulatorSystemRoot at runtime on trying to install App on iOS 10.0 Simulator (4186457).
  • Interfaces don't function on iOS in AIR23 when shared between swf's (4194914)

 

 

Download Locations:

 

AIR runtime for Windows: 24.0.0.180 Runtime Download

AIR runtime for Macintosh: 24.0.0.180 Runtime Download

 

AIR SDK & Compiler for Windows: 24.0.0.180 SDK & Compiler Download

AIR SDK & Compiler for Macintosh: 24.0.0.180 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 24 SDK and ActionScript Compiler 2.0 in a single SDK called “Adobe AIR 24 SDK & Compiler”.

 

AIR SDK (Compatible with Flex) for Windows: 24.0.0.180 SDK Windows Download

AIR SDK (Compatible with Flex) for Macintosh: 24.0.0.180 SDK Macintosh Download

 

Previous versions of the AIR runtime and SDK can be found on the Archived AIR SDK and Runtimes page


12/14/2016 - Beta - Flash 24.0.0.189

$
0
0

Welcome to the Flash Runtime version 24 updated beta!  We've been hard at work adding new features to Flash Player and we're looking forward to receiving feedback from our Flash Player community.

 

This beta release includes new features as well as enhancements and bug fixes related to security, stability, performance, and device compatibility for Flash Player 24.  For full details, please see our release notes.

Note:

  • The ActiveX Flash Player in this release is not compatible with Windows® 8.x or 10
  • Flash Player for Windows® 8.x/10 is available as part of the generally available Windows® 8.x/10 update

New and Updated Features

Spherical video support in Flash and AIR

Spherical videos support is added to both Flash Player and AIR from version 24 onward. Spherical videos have a specific meta-data attached to them, which can now be retrieved using the new property provided by the feature. This feature supports equirectangular projection type of videos conforming to https://github.com/google/spatial-media/blob/master/docs/spherical-video-rfc.md.

This feature is supported on Desktop and Android devices.

API introduced

The Object parameter of the onMetaData event provides video metadata information. The feature adds new properties to the parameter. The added property is an array of string type in XML format. Refer code below.

 

functionns_onMetaData(info:Object):void{

trace("The matrix of Movie Header Box:"+info.sphericalVideoInfo[0]); // info.sphericalVideoInfo provides the related meta-data

}

 

Sample Spherical Video Player

A sample project for Spherical video player can be downloaded from this link in order to understand the use of the metadata to render the spherical video. The sample code makes use of an instance of the context3D, where VideoTexture is used to render video for better performance.

See the following chart for ActionScript classes in the project.

Spherical Video.png

SampleSphericalVideoPlayer class

This class provides basic controls for the Spherical video functionality.

SphericalVideo class

This class creates the context3D instance to render spherical video using VideoTexture

Projection classes

These classes are used for generating vertices and indices corresponding to the projection type used.

Improved support for high resolution displays on Firefox for Windows

Beginning with Flash Player version 24 and Firefox version 51 on Windows, Flash content will now scale appropriately on high resolution displays.

Separate HTTP and HTTPS permissions for Camera and Microphone

To provide users with a better control over their camera and microphone data, Flash Player now provides a more fine-grained control over how permissions are granted. Users can now allow camera and microphone access for a domain when that content is served via HTTPS, and disallow the access when content from the domain is served over HTTP. Since this feature is currently in beta, the settings will not be visible in the Global settings Manager.

Known Issues

  • None

Fixed Issues

  • Socket connection fails with Security error#2048.(FP-4198184)

System Requirements

For system requirements of the current release of Flash Player in production, please visithttp://www.adobe.com/products/flashplayer/systemreqs/

About the Beta Channel

To get the latest Beta build of Flash Player visit Adobe labs

Beta versions of Flash Player are also available for automatic installation via our Background Update service.  Please subscribe to automatically receive update notifications for future Flash Runtime announcements.

Note: If you are having issues downloading Flash Player, it may be because of a cache or locale issue. Wait for 24 hours before retrying and if you still face issues, please post the issue in Flash Player forum

4/11/2017 - Release - Flash Player 25

$
0
0

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-10)

 

 

Features for Flash Player 25:

Separate HTTP and HTTPS permissions for Camera and Microphone

With Flash Player 24 release, we provided users with a fine-grained control over how permissions are granted for their camera and microphone data. These settings are visible in the Global Settings Manager and Native Control Panel for Mac and Windows.  With the latest update of Flash Player 25, users can customize these settings from the Native Control Panel for both HTTP and HTTPS on Linux too.

 

For complete information please see our release notes.

 

 

Fixed Issues

  • [Windows] Flash player unresponsive after connecting with the socket.(FP-4198296)
  • 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 25 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 25 Windows for Internet Explorer - ActiveX:  25.0.0.148

Flash Player 25 Windows for Firefox and other Netscape Compatible Browsers - NPAPI: 25.0.0.148

Flash Player 25 Windows for Opera and Chromium Based Browsers - PPAPI: 25.0.0.148

 

Flash Player 25 Windows for Google Chrome - PPAPI: 25.0.0.148

 

Flash Player 25 for Internet Explorer on Windows 8.1 (64-bit machine): 25.0.0.148

Flash Player 25 for Internet Explorer on Windows 8.1 (32-bit machine): 25.0.0.148

 

Flash Player 25 Windows for Internet Explorer and Edge on Windows 10 - ActiveX: 25.0.0.148

 

Flash Player 25 Mac for Safari, Firefox and other Netscape Compatible Browsers - NPAPI: 25.0.0.148

Flash Player 25 Mac for Opera and Chromium Based Browsers - PPAPI: 25.0.0.148

 

Flash Player 25 Mac for Google Chrome - PPAPI: 25.0.0.148

 

Flash Player 25 desktop for Linux (NPAPI): 25.0.0.148

Flash Player 25 desktop for Linux Chromium (PPAPI): 25.0.0.148

 

 

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.

6/13/2017 - Release - AIR 26 Runtime and SDK

$
0
0

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 26.  Please see our release notes for full details.

 

Announcement

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

Moving to WKWebView for StageWebView on iOS

Starting AIR 26, For StageWebView on iOS, we now use WKWebView (instead of UIWebView) behind the scene, which uses WebKit engine to render WebViews. For more information on WKWebView, see https://developer.apple.com/reference/webkit/wkwebview. This does not impact AS developers directly. However, because of a few known WebKit bugs, there may be some workflow changes in the existing iOS Apps. Do report them on Adobe AIR forums for us to investigate.

This change also allows developers to debug StageWebView content in iOS. To enable web inspector on iOS, complete the following steps:

  1. Open the Settings app.
  2. Tap Safari.
  3. Scroll down and select Advanced.
    gen_adv_2x.png
  4. Switch Web Inspector to ON.

gen_adv_switch_2x.png

 

5. After Web Inspector is enabled, connect your device to your desktop machine with a USB cable. The name of your device appears in the Develop menu of Safari.

iPhone_for_development_2x.png

 

Alternately, developers can use iOS Simulator to take advantage of Web Inspector’s debugging capabilities. Use the same instructions to enable Web Inspector on iOS, from within the iOS Simulator’s Settings app.

 

Apple TV support (Beta Quality)

We have made some enhancements to tvOS support, which was introduced in AIR 24 beta channel. For more information, see the Release Notes specific to this feature.

 

DeviceRotation Event Handler for Mobile

When a device is rotated, the orientation of the plane defining device screen changes. This change can be depicted in terms of a Rotation Vector, which can be represented by Roll-Pitch-Yaw or Quaternions data. The DeviceRotation event handler is used to fetch this data. One scenario where this data can be useful is to update the viewport of Spherical videos when the device is rotated.

 

This event handler has been introduced in AIR 26, where we have added a new DeviceRotation class which dispatches DeviceRotationEvent based on the activity detected by the device’s motion sensors namely Accelerometer and Gyroscope.

 

DeviceRotation object

The user can create an object of DeviceRotation class and can access its properties or register for events on this object.

For example:

 

var deviceRotation:DeviceRotation = new DeviceRotation();

 

DeviceRotation.isSupportedreturns true if the following conditions are satisfied:

  • The device has Accelerometer and Gyroscope sensors.
  • Android devices with versions 4.3(JELLY_BEAN_MR2) and above.
  • iOS devices with versions 4.0 and above.

 

DeviceRotationEvent.UPDATE is the event, attached to a DeviceRotation object. The event is used in the following scenarios:

  • When a new listener function is attached using addEventListener.
  • When the value of the DeviceRotation vector changes, this event is delivered at some device-determined interval.
  • When the player may have missed a change in the DeviceRotation (for example, if the player is waking up after sleep), this event is delivered.

 

DeviceRotationEvent object

When an update event is fired on DeviceRotation object, it is caught as a DeviceRotationEvent object. For example:private function updateHandler(event : DeviceRotationEvent ) : void { }Properties for DeviceRotationEvent are exposed as:

  • Timestamp - The duration in milliseconds from the application launch time.
  • Roll, along Y-Axis - Its unit is Number and the value is an angle in degrees.
  • Pitch, along X-Axis - Its unit is Number and the value is an angle in degrees.
  • Yaw, along Z-Axis - Its unit is Number and the value is an angle in degrees.
  • Quaternion - It is an array that represents the quaternion values in [w, x, y, z] format.

Enhanced Profile

With AIR 26, we are introducing a new stage3D profile “Enhanced”  for AIR Mobile. This will be a new constant in Context3DProfile class. Availability of "enhanced" profile indicates the availability of AGAL4. The same profile name can be used in requestContext3D and requestContext3DMatchingProfiles methods of Stage3D.

AGAL 4 introduces a new opcode “tld” and new Vertex Sampler register “vs” for fetching texture in a 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 for parameter since GPU does not support the automatic calculation of LOD in the vertex shader.

Latest version of AGAL is available at https://github.com/adobe-flash/graphicscorelib/tree/master/src/com/adobe/utils

 

Vertex Texture Fetch

With the introduction of new Stage3D profile i.e. ‘ENHANCED’, Vertex Texture Fetch is now available in AIR mobile. 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 will be 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 should 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.

 

 

Fixed Issues

 

  • [iOS] drawViewPortToBitmapData method on StageWebView return an empty bitmapdata
  • [iOS] AudioPlaybackMode.VOICE and SoundMixer.useSpeakerphoneForVoice = true not working with bluetooth headset (AIR-4196360)
  • [Android] StageText not firing ENTER event (AIR-4198260)
  • [iOS] Unable to launch iPad Pro on iOS Simulator from ADT (AIR-4198314)
  • [Android] Launcher icons are packaged in incorrect resources location (AIR-4198222)
  • [iOS] Starling masking does not work on iOS with anti-aliasing turned ON (AIR-4198229)
  • [iOS] ErrorEvent.ERROR not fired (AIR-4198355)
  • [iOS] StageText: setting stage property after calling selectRange() incorrectly gives focus to StageText (AIR-4198296)
  • "Could not generate timestamp: Connection error" is displayed while packaging the AIR application (AIR-4195221, AIR-4198332, AIR-4172255)

 

 

Known Issues:

 

  • [Android] 'Texture decoding failed' error is displayed when uploading the texture asynchronously (AIR-4198272)
  • [iOS] Compilation fails while executing: compile-abc - class (...) could not be found (AIR-4198225)
  • [iOS] Interfaces do not function when shared between SWFs (AIR-4194914)
  • [Android] Error #3672: Buffer creation failed when using drawToBitmapData (Context3D) while using VideoTexture (AIR-4198290)

 

 

Download Locations:

 

AIR runtime for Windows: 26.0.0.118 Runtime Download

AIR runtime for Macintosh: 26.0.0.118 Runtime Download

 

AIR SDK & Compiler for Windows: 26.0.0.118 SDK & Compiler Download

AIR SDK & Compiler for Macintosh: 26.0.0.118 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 26 SDK and ActionScript Compiler 2.0 in a single SDK called “Adobe AIR 26 SDK & Compiler”.

 

AIR SDK (Compatible with Flex) for Windows: 26.0.0.118 SDK Windows Download

AIR SDK (Compatible with Flex) for Macintosh: 26.0.0.118 SDK Macintosh Download

 

Previous versions of the AIR runtime and SDK can be found on the Archived AIR SDK and Runtimes page

9/12/2017 - Release - Flash Player 27

$
0
0

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:

Settings.png

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:

  1. 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.
  2. 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:

  1. The content provides a control such as a button that indicates that the user should click to select an audio device.
  2. 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.
  3. 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[i]+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) {

          [dosomething]

     } elseif(evt.reason == AudioOutputChangeReason.DEVICE_CHANGE) {

          [dosomething]

     }

}

 

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.

9/12/2017 - Release - AIR 27 Runtime and SDK

$
0
0

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:

 

  1. uploadFromBitmapDataAsync( source:BitmapData, miplevel:uint = 0)
  2. 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

 

Viewing all 25114 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>