Skip to main content

4 posts tagged with "updates"

View All Tags

· One min read
Jan

AIR Runtime 33.1.1.743 has been released by Harman.

Bug Fixes

github-183: Fixing crash when cleaning up Windows StageWebView when debugger is active
github-1509/1522/1529: Correcting file dialog handling of properties such as filters and filenames
github-1510: Protected the audio track 'stopped' property from destroyed objects on Android
github-1516: Fixing problem with ANE zips being closed before extracting all Android files
github-1528: Using XML descriptor 'versionLabel' for Android 'versionName' field
github-1531: Ensure event handlers are still called when lower-priority event listeners are added within an earlier handler
github-1536: Detecting Windows 11 version in Capabilities information
github-1541: Ensuring unnamed local variables can still be inspected via a debugger connection

· 2 min read
Jan

AIR Runtime 33.1.1.713 has been released by Harman.

Changes and Issues

3.1 Changes in this Release

3.1.1 Runtime

No changes – the below details will be fixed for all “33.1” version numbers:
Namespace: 33.1
SWF version: 44

The namespace and SWF version updates are made across all platforms and may be used to access the updated ActionScript APIs that will be introduced in future beta releases of 33.1. Note that using “33.0” as a namespace is not valid, and is resulting in behaviors such as VerifyErrors being dispatched at application start-up with built-in class names such as ExtensionContext, Context3D, and others.

3.1.2 Build Tools

Xcode 13 and the latest macOS and iphoneOS SDKs are now being used to build the AIR SDK. The build system for this is on a version of macOS that doesn’t support 32-bit processes hence we cannot generate the 32-bit versions of the stub files. This means that we can no longer support older 32-bit iPhone/iPad devices.

3.1.3 AS3 APIs

Updated AS3 APIs are described in section 12.

3.1.4 Features

github-1432: Updating version of ADB to 1.0.41 to match recent Android platform-tools

3.1.5 Bug Fixes

github-274: Updating Java bytecode generator to cope with Android styleable resources
github-444: Allow additional languages to be used in AIR mobile apps
github-1368: Failed to package Android APK using Java 17
github-1392: Ensuring utf-8 based Android resources can be compiled with javac
github-1405: Failed to package Android AAB using Java 17
github-1409: Ensuring jarsigner process uses quotes around arguments and correct relative paths
github-1418: Ensuring default APK build is targeting armv7
github-1424: Ensuring correct ANE .so files are placed in the correct ABI subfolders
github-1426: Gradle java process to use the higher of ADT memory vs config setting
github-1429: APKs generated without legacy build mode will include all ABIs
github-1430: ADT failing to launch an Android application when using new build mechanism
github-1431: Better error handling for invalid license files
AIR-5449: AIR Android packaging using ADT should work with compatible major/minor AIR releases

· 2 min read
Jan

AIR Runtime 33.1.1.698 has been released by Harman.

Changes and Issues

3.1 Changes in this Release

3.1.1 Runtime

No changes – the below details will be fixed for all “33.1” version numbers:
Namespace: 33.1
SWF version: 44

The namespace and SWF version updates are made across all platforms and may be used to access the updated ActionScript APIs that will be introduced in future beta releases of 33.1. Note that using “33.0” as a namespace is not valid, and is resulting in behaviors such as VerifyErrors being dispatched at application start-up with built-in class names such as ExtensionContext, Context3D, and others.

3.1.2 Build Tools

Xcode 13 and the latest macOS and iphoneOS SDKs are now being used to build the AIR SDK. The build system for this is on a version of macOS that doesn’t support 32-bit processes hence we cannot generate the 32-bit versions of the stub files. This means that we can no longer support older 32-bit iPhone/iPad devices.

3.1.3 AS3 APIs

Updated AS3 APIs are described in section 12.

3.1.4 Features

github-1387: Switch APK builds so that they use Android Gradle plug-in. When an Android APK build is requested, the default mechanism is now to use Gradle (similarly to how the AAB bundles are created). This brings some parity to the two mechanisms which should help to ensure developers don’t encounter problems with deployed bundles that haven’t been first spotted during local testing. For developers who would prefer to keep using the earlier APK generation mechanisms, a flag can be added to the XML Descriptor File under the <android> section: “<BuildLegacyAPK>true</BuildLegacyAPK>”.

3.1.5 Bug Fixes

github-972: Ensure signing of an App Bundle preserves the file permissions
github-1006: Adding support for 'webViewAllowFileAccess' tag for Android local file access in WebView
github-1340: Ensuring 'resdir' option in XML descriptor can use relative paths
github-1376: Ensuring no-compress settings are used in App Bundle packages
github-1391: Fixing signing block format for dynamic frameworks in macho binaries
github-1392: Android APK: updating Java code generation to target 1.8
github-1397: Ensuring Android package names don't include Java reserved words
github-apm40: Fixing crash when using command-line tools with nativeprocess
AIR-4740: Remove use of sun internal security classes for APK/AAB signing
AIR-5427: AIR Android security update for https certificate errors

· 2 min read
Michael

Due to a lot of requests over the previous months we have added several new sections to promote developers and better direct people to the current resources available for AIR.

We also have started creating a detailed "Getting Started" guide to walk new users through the installation of the AIR SDK and setup of a development environment.

The first of these is the Community section. This section is aimed to direct developers to the resources and community channels that are available and active on the net.

We have initially added three of what we believe are the most important resources currently:

And we will be adding the ever present stackoverflow reference as well. If you believe anything else should be added, please let us know!

The second is the Showcase section. The showcase is designed to be a place for AIR developers to not only promote their work but promote the AIR platform and show what is possible using the AIR SDK. You can add your own application through a pull request to the repository (or you can just email me your details).

If you have any feedback on the tutorials or guides we are writing (or if you would like to contribute) please reach out!