AIR Native Extension News

[marchbold]

Discussion for posting news from the AIR Native Extensions team.

[marchbold]

September 2024

Notifications, Game Services, InAppBilling, Firebase Dynamic Links, Adverts, ironSource

Recently we have released updates to several of our main extensions, key updates include:

• Notifications on windows from non-UWP applications
• Play Games Services v2 integration through GameServices and access through Google Play Games on PC
• InAppBilling Play Billing update to v6.2.1
• AdMob update to the latest SDK (Android and iOS)
• ironSource update to the latest SDK (Android and iOS)

Lots of Android and specifically Google related updates ensuring your applications can meet the latest requirements for the Play Store.

As always, if you have any development needs for AIR, Unity, Flutter or Haxe, please feel free to contact us at airnativeextensions@distriqt.com.

---

[AnAmateurDev]

Do you have any native extension that works in Haxe ?

[marchbold]

Nothing publicly available that works natively in Haxe, you can use them with the AIR/Flash output though I believe.

[marchbold]

Is there something in particular you are looking for? We have done work in Haxe for clients before.

[marchbold]

February 2025

A Major Upgrade for AIR Extensions! New Payment System and Custom Development Work

Over the past six months, we’ve been working closely with Harman to bring a smarter, more efficient dependency system to AIR. Our new approach replaces embedded dependencies with Gradle dependencies, making extension management easier, faster, and more resilient.

What this means for you:

• Smaller extension file sizes – Free up space & streamline your builds
• Faster compilation times – Get things done in record time
• Much simpler manual manifest additions – Spend less time on setup
• Better dependency resolution – Seamless updates and fewer conflicts
• Improved compatibility – Extensions work together more smoothly

These improvements happen behind the scenes, making everything more stable and maintainable. But you’ll definitely notice the difference with smaller files, fewer manifest changes, and much faster builds. 🚀

---

Got an idea or a project in mind? Let’s make it happen! Reach out to us at airnativeextensions@distriqt.com.

Let’s build something amazing together! 🚀🔥

[Devin-Licastro]

Oh my goodness, that sounds fantastic! Looking forward to upgrading!

[2jfw]

Very nice! I update end of last year and the compile times (IntelliJ) went up several 100% (not exaggerating here!) as the annoying extraction of the ANE's is now remarkably faster!
Great Job 🍻

[marchbold]

APM v2.0

Linux support

APM Now Supports Linux: Expanded Capabilities and Key Updates

Great news for developers! APM has been updated to fully support Linux operating systems. This means you can now use APM to install and manage libraries, extensions, and application descriptors in Linux-based development environments. This long-awaited feature enhances APM’s versatility and makes it even more accessible to a broader range of developers.

read more...

[marchbold]

June 2025

New website release, extension updates!

Over the past few months, we've been working intensively to rebuild airnativeextensions.com, primarily to integrate a new payment provider and ensure we can continue delivering extensions to developers worldwide. It's been a significant undertaking, but we're confident the improvements to the platform will be well worth it.

What this means for you:

• Nothing will change in the near future
• All new purchases will be done through our new payment provider
• We are asking all clients to migrate to the new payment provider

We've made migration easy and allows you to combine your subscriptions into a single payment if you want. More information below.

Also there are lots of extension updates that have been released.

Extension Updates

• Scanner v6.0.5 - Major Upgrade for Barcode Scanning
• Share v8.1.0 - SMS Reading Added on Android
• InAppBilling v16.1.2 - Improved handling of subscription offer details and purchase flow
• InAppUpdates v3.0.1
• Vibration v5.4.2
• CameraRollExtended v8.0.2 - Fixed image loading and permissionless picker issues
• Adverts v16.1.0 - Updated SDKs
• CrashUtils v0.0.2 - New free extension
• DetectScreenshot v1.0.0 - New free extension
• NFC v5.6.1

Got questions? We're here to help! Let's build better, faster, and smarter together. 💡

read more...

[marchbold]

July 2025

Play Billing v7 (Android 35), Adverts

We've had a big month of updates! From crucial billing upgrades to smoother sign-ins and better mediation support, this round of releases helps you stay compliant, improve user experience, and keep things running smoothly.

We'd also like to take a moment to thank everyone who has migrated to our new payment provider and started using the new website. We hope the transition has been smooth and that you're finding the new site easier to use. If you run into any issues or have any questions, don't hesitate to reach out - we're always happy to help!

Here's everything you need to know.

Extension Updates

• InAppBilling v17.1.0 - Major Overhaul for Google Play + Samsung IAP
• Adverts v16.2.0 - AdMob SDK Update + Audio Fix
• GoogleIdentity v7.1.1 - Smarter, Seamless Sign-In

Got questions? We're here to help! Let's build better, faster, and smarter together.

read more...

[marchbold]

Android 15 UI Changes

Android 15 (API v35) includes some changes that are intended to create a more consistent, intuitive user experience.

note

You can read the official release of this information here: https://developer.android.com/about/versions/15/behavior-changes-15

Window inset changes​

There are two changes related to window insets in Android 15: edge-to-edge is enforced by default, and there are also configuration changes, such as the default configuration of system bars.

Edge-to-edge enforcement​

Apps are edge-to-edge by default on devices running Android 15 if the app is targeting Android 15 (API level 35).

An app that targets Android 14 and is not edge-to-edge on an Android 15 device. The application is contained within the window insets.

After updating your target sdk to 35 you will find that your application is now expected to handle the window insets and is rendered edge-to-edge. However, many elements are now hidden by the status bar, 3-button navigation bar, or display cutout due to the Android 15 edge-to-edge enforcements.

You will need to update your application to correctly handle rendering within the window insets and render within these bounds so UI elements are not hidden.

Handling window insets​

To get the safe area to render you can use the Application extension to retrieve the display cutout information:

var displayCutout:DisplayCutout = Application.service.display.getDisplayCutout();

This object contains 4 properties: safeInsetBottom, safeInsetTop, safeInsetLeft, safeInsetRight, each indicating the number of pixels from the edge of the screen that system bars or cutouts may affect.

There is also an boundingRects property containing detailed areas for any cutouts that may affect rendering.

You can use this to apply bounds to your root content 'safe area', eg using a starling _safeArea object for rendering UI elements you can use something like the following :

if (Application.isSupported)
{
    var cutout:DisplayCutout = Application.service.display.getDisplayCutout();
    var topInset:Number = cutout.safeInsetTop / _scale;
    var bottomInset:Number = cutout.safeInsetBottom / _scale;
    var leftInset:Number = cutout.safeInsetLeft / _scale;
    var rightInset:Number = cutout.safeInsetRight / _scale;

    _safeArea.setTo(leftInset, topInset,
        _stageWidth - leftInset - rightInset,
        _stageHeight - topInset - bottomInset);
}

note

If you use immersive mode or change display modes at any time in your application you should ensure to reapply these corrections afterwards.

Cutouts​

If your app targets SDK 35 and is running on an Android 15 device, LayoutMode.CUTOUT_ALWAYS is the default behavior. This means that if you were previously relying on setting the LayoutMode eg via calling

Application.service.display.setDisplayMode( 
    DisplayMode.FULLSCREEN, 
    LayoutMode.CUTOUT_NEVER );

this will be interpretted as 'always' and your content will be drawn into cutout regions.

Opt-out​

As a temporary workaround you can opt-out of this edge-to-edge enforcement in v35.

caution

This option to opt-out will be removed once you update to target v36, so this workaround should only be treated as temporary.

Firstly, create a custom resources folder in your application and package it according to the guide here.

Under your resources folder create a values-v35 folder and add a file styles.xml into this folder with the following content:

styles.xml

<?xml version='1.0' encoding='utf-8'?>
<resources>

    <style name='Theme.NoShadow' parent='android:style/Theme.NoTitleBar'>
        <item name='android:windowContentOverlay'>@null</item>
        <item name='android:windowOptOutEdgeToEdgeEnforcement'>true</item>
    </style>

</resources>

The android:windowOptOutEdgeToEdgeEnforcement option is the critical one that will disable this edge-to-edge enforcement for Android 35.read more...

[2jfw]

Very informative and exactly what I was looking for - I'm using the latest AIR SDK now and just had a tester with a Galaxy S25 report that my app header is covered with the camera and that the in-app bottom navigation is covered with the native android buttons.

Regarding your code sample, what exactly is the _scale var?
Do I assume correctly, that the saveArea is what I would assign as the starling.viewPort ?

[marchbold]

Ah that's an excerpt from the starling scaffolding project: https://github.com/Gamua/Starling-Framework/blob/master/samples/scaffold_mobile/src/utils/ScreenSetup.as#L87-L105

So the scale is just adjusting the raw pixel values to the starling scale.

[marchbold]

August 2025

August Release Roundup: Major updates across several extensions

This month brings one of the biggest waves of updates we've seen recently, with multiple major version releases, SDK updates, and a few important deprecations to note. A lot of these updates bring improved compatibility with Android 35 with the major view changes that are required with any app updates now.

This August has been a month of major foundation upgrades - from Firebase and Play Services to Media Player and Adverts. While some updates require careful migration (especially Firebase and Game Services), they set developers up with the latest features, improved stability, and compliance with upcoming platform changes.

If you're using any of these extensions, now is the time to update your projects and plan migrations ahead of deprecations like Firebase Dynamic Links.

Here's a quick look at the most important updates this month across distriqt extensions:

Extension Updates

• Firebase v11.0.0 Major update: Dynamic Links removed (deprecated by Google). Migration required for email link authentication.
• Game Services v11.0.0 Updated to Google Play Games v2 SDK (v21.0.0). Migration guide available.
• Push Notifications v17.0.0 Latest Firebase Messaging SDKs (Android v25.0.0 / iOS v12.1.0).
• Adverts v16.3.0 AdMob SDK updates (Android v24.5.0 / iOS v12.9.0).
• Adverts Mediation v9.0.0 Latest SDKs for AppLovin, UnityAds, Facebook Audience, IronSource, and more.
• Native Maps v7.0.0 Play Maps SDK v19.2.0 + Android ARMv8 fixes.
• Media Player v6.0.0 Migrated to AndroidX Media3, added new video scale modes, and improved background audio support.
• Google Identity v8.0.0 Updated iOS/Android SDKs + new disconnect functionality.

Biggest change to note: Firebase Dynamic Links is deprecated and removed. Projects using email link authentication should migrate immediately.

Got questions? We're here to help! Let's build better, faster, and smarter together.

read more...

[Brujotesco]

Hi, I created the account just to see if I get a response before this! I see that they updated Admob, I want to think it is the Admob v24.5.0 version of the SDK, I also updated to that version but I am getting an error when calling MobileAds.initialize(this, initializationStatus -> {});, I read that it could be because the getActivity context is not supported or I may have missed some dependency to include in my packaging! I did a native test and it works fine!

[marchbold]

@Brujotesco Log an issue in the Adverts repository and we'll follow up with you there. Cheers

[Brujotesco]

It's my own project. All I want to know is what dependency you used when packaging the .ane file so that when launching admob.int it doesn't crash since version 24.4 of admob. The previous one works perfectly for me! I just want to know if you've had that issue and how to fix it.

[marchbold]

There are lots of dependencies and they are listed in the documentation, just make sure you either using apm or have the latest of all the dependencies. Highly recommend using apm to ensure your dependencies are correct. If you are still having issues, log all the details in the Adverts repo and we'll follow up with you.

[marchbold]

September 2025

September Release Roundup: Android 15 & iOS 26 Compatibility

Great news for all our developers! This month brings critical updates across our extension portfolio to ensure compatibility with Android 15 (API 35) and iOS 26, along with exciting new features to enhance your applications.

Here's a quick overview of our latest extension updates:

Extension Updates

• Adverts v16.4.0 - Android 15 & iOS 26 compatibility updates
• InAppBilling v18.0.0 - Major Update to Play Billing v8 + macOS compatibility fix
• Location v6.1.0 - Major Update with rebuilt Android implementation
• Scanner v6.0.6 - Major Update with completely rewritten scanning algorithm + Android 15 system bars and cutouts fix
• BranchIO v5.20.100 - Updated SDKs and modernized integration
• Singular v13.1.0 - SDK updates: Android v12.10.0, iOS v12.8.1
• MediaPlayer v6.0.2 - Improved iOS background audio handling
• AudioRecorder v4.0.0 - Updated dependencies and permission handling
• GameServices v11.0.1 - Fixed macOS Game Center crash
• PushNotifications v17.0.1 - Updated OneSignal SDKs
• Core v7.5.5 - Updated for macOS 10.13 minimum and latest Xcode
• Google Play Services v32.0.1 - AdMob SDK updated to v24.6.0

Got questions? We're here to help! Let's build better, faster, and smarter together.

read more...

[marchbold]

October 2025

October Release Roundup

This month we've released a range of updates focusing on macOS compatibility, Android 15 edge-to-edge improvements, and major SDK updates across Adverts, Facebook, and mediation extensions.

These updates continue our commitment to keeping all ANEs stable, modern, and aligned with the latest platform changes from Google and Apple.

Here's a quick overview of our latest extension updates:

Extension Updates

• GameServices v11.0.2 - Fixed macOS compatibility issue
• InAppBilling v18.0.3 - Fixed macOS compatibility issue
• Adverts v16.5.0 - Android 15 & iOS 26 compatibility updates
• Native WebView v8.0.1 - Fixed null exception when WebView
• Facebook v18.1.0 - Updated SDKs

Got questions? We're here to help!

read more...

[marchbold]

November 2025

November Release Roundup

Welcome to this month's extension update! We've been busy refining existing tools and expanding support across platforms to keep your AIR development workflow modern, reliable, and aligned with evolving platform requirements. This release brings important improvements to the WebP extension - now fully supported on macOS and Windows - as well as the first beta of our new AgeRange extension, designed to simplify age-verification flows on iOS and Android. There's also ongoing progress on the new Display extension, and we'd love your help testing it.

Here's a quick overview of our latest extension updates:

Extension Updates

• WebP v4.2.2 - WebP library update + macOS and Windows support
• AgeRange v0.0.1 - Beta release for new age related SDKs

If you have any questions or want to get involved in testing, we're here to help!

read more...

[marchbold]

Edge-to-Edge Displays

Edge-to-edge layouts means that the window spans the entire width and height of the display by drawing behind the system bars including the status bar, caption bar, and navigation bar.

This means that your content may render behind operating system elements and you will need to account for this in the design and execution of your application. You will likely want to render certain content under the system UI, such as scrolling and non-UI elements however it is important that your interactive elements never get rendered in these areas.

For example in the following a button is obscured by the navigation bar:

| Obscured | Correctly Rendered |
| read more...

[marchbold]

January 2026

Welcome to 2026!

As we step into the new year, I'd like to warmly thank all of my clients and the community for your support throughout 2025. Your continued support makes my contribution to the AIR community possible and I really do hope it is valuable to your applications. I'm incredibly excited about what's ahead in 2026, with new extensions on the horizon and continued improvements across our extensions.

December has been a particularly busy month, with new features, important fixes, and several new beta and initial releases. Your issue reports, beta testing, and discussions have played a direct role in shaping these improvements, and I'm incredibly grateful for that collaboration.

I hope you're all able to enjoy a well-earned New Year break, and I'm excited to kick off 2026 with even more momentum. There's a lot planned, and I look forward to continuing to build powerful, reliable tools together in the year ahead.

Wishing you a relaxing break and an exciting start to 2026.

If you have a project in mind and are looking for development support, please don't hesitate to reach out. I'm excited to kick off new projects in 2026 and would love to chat.

Happy coding!

Here's a quick overview of the latest extension updates:

Extension Updates

• Image v7.1.0 - Screenshot capture improvements
• NativeWebView v8.0.2 - Disable the iOS input accessory view
• AgeRange v0.0.4 - Further updates to the beta release for new age related SDKs
• Display v0.0.4 - Beta release of the new Display extension

If you have any questions or want to get involved in testing, we're here to help!

read more...

[marchbold]

February 2026

January Release Update

Welcome to your latest AIR Native Extensions update! We've had a busy start to 2026, featuring a brand-new system information extension, a highly requested debugging feature for WebView's on Android and better support for handling Age restrictions in the Amazon App Store ecosystem.

Here's a quick overview of the latest extension updates:

Extension Updates

• SystemInfo v0.1.0 - SystemInfo extension release for Android, iOS, macOS, Windows
• NativeWebView v8.0.4 - Added Android Debugging Support
• AgeRange v0.1.0 - Amazon SDK Integration

If you have any questions or want to get involved in testing, we're here to help!

read more...

[marchbold]

March 2026

February Release Update

It has been a busy month for the AIR development ecosystem! The February releases focus heavily on modernizing core SDKsspecifically Firebase v12.9.0 and AdMob v24.9.0 - while introducing some highly requested UI features and critical stability fixes.

Key focus:

• Keeping all Firebase and Google SDKs fully up to date
• Aligning AdMob and mediation networks with the latest versions
• Improving consent management and monetisation reporting
• Fixing packaging and manifest generation issues
• Introducing new UI capabilities like the colour picker dialog

As always, we recommend updating to the latest versions to ensure compliance, stability, and access to new features.

Here's a quick overview of the latest extension updates:

Extension Updates

• Dialog v9.1.0 - Added native Colour Picker
• Adverts v17.0.0 - AdMob v24.9.0 + Consent Sync
• Firebase v12.0.0 - SDK v12.9.0 (iOS) / BOM v34.9.0 (Android).
• GoogleIdentity v8.1.0 - Latest Google Sign-In SDK support
• GooglePlayServices v32.1.4 - Fixes for apm manifest generation

If you have any questions, we're here to help!

read more...

[marchbold]

Brazil Digital ECA Support

Update: AgeRange ANE v0.0.3 Brazil Digital ECA Support

We have released a critical update for the AgeRange Adobe AIR Native Extension to support v0.0.3 of the Google Play Age Signals API.

This update is essential for developers with apps available in Brazil, ensuring your projects are ready for the Digital Child and Adolescent Statute (Digital ECA) before the March 17, 2026 deadline.

What's happening

Brazil has passed a law, the Digital Child and Adolescent Statute (Digital ECA), outlining new obligations for app developers. Key provisions include:

• Requiring developers of apps aimed at children and adolescents or likely to be accessed by them to ingest age range data from app stores; and
• Prohibiting loot boxes in electronic games aimed at children and adolescents or likely to be accessed by them.

It is scheduled to take effect on March 17, 2026. We recommend that you take action to determine whether and how the Digital ECA applies to your app and implement any necessary changes to ensure compliance.

What's New?[​](https://docs.airnativeextensions.com/news/2026/03/12/brazil-digital-eca-support#whats-new 'Direct link to What's New?')

Google has updated the Age Signals API and will roll out age range information via this API for users in Brazil, beginning with supervised users and scaling to all users over the coming months. This release updates the underlying implementation to support Google's latest version.

This release introduces more granular user data and vital error-handling mechanisms to help you navigate global age verification laws:

• SELF_DECLARED Status: The API can now distinguish between users who are VERIFIED (official ID/Credit Card), SUPERVISED (Family Link), or SELF_DECLARED (manually entered). This allows you to tailor your app's restrictions or content based on the level of verification certainty.
• SDK_VERSION_OUTDATED Error Code: A key addition to the API. When this error occurs, age signals will not be returned.
  • Pro Tip: We recommend implementing a 'graceful degradation' plan. If your app receives this error, consider falling back to an in-app age gate or a third-party verification service to maintain compliance.

Change Log​

• feat(android): Update Play Signals API to v0.0.3 (Resolves #3).
• Update: Support for the new SELF_DECLARED status and SDK_VERSION_OUTDATED error code.

read more...

[marchbold]

April 2026

March Release Update

March brought a focused set of extension updates with important SDK upgrades, stability fixes, and testing improvements across billing, social login, web views, and age signal support.

Key focus:

• Updating Google Play Billing to the latest supported version
• Keeping Facebook iOS SDK integrations current
• Resolving a macOS NativeWebView crash scenario
• Expanding AgeRange testing and handling paths for edge cases
• Migrating extension repositories from distriqt to airnativeextensions

As always, we recommend updating to the latest versions to ensure compatibility, stability, and access to the newest platform features.

Repository Migration Notice

We are migrating our GitHub repositories for native extensions from the distriqt organisation to airnativeextensions.

During this migration, existing users may receive invitations to the new repositories.

You will need to accept these GitHub invitations to continue having access to extension repositories and future updates.

What to expect

1. We will progressively move extension repositories to the airnativeextensions organisation.
2. If you currently have access, GitHub will send an invitation for the equivalent repository under the new organisation.
3. Invitations are sent by GitHub and may appear as an email and/or a notification in GitHub.

What you need to do

1. Open the invitation from GitHub.
2. Accept the invitation to the repository under airnativeextensions.
3. Confirm you can access the new repository and release tags.
4. Update any existing bookmarks, remotes, or automation to point to the new repository URL.

Timing and continuity

• Access to migrated repositories depends on accepting the invitation.
• We will aim to keep migration disruption to a minimum and communicate important changes as they happen.

Questions

If you believe you should have access but do not receive an invite or if the invitation expires, please contact us so we can verify your account access and resend the invitation where required.

Please feel free to reach out if you have any questions or concerns about this migration.

---

Here's a quick overview of the latest extension updates:

Extension Updates

• InAppBilling v18.1.0 - Play Billing SDK v8.3.0 and countryCode support in getUserData
• FacebookAPI v18.1.1 - iOS SDK update to v18.0.3
• NativeWebView v8.0.5 - macOS focus-loss crash fix
• AgeRange v0.3.0 - Null handling, fake error testing, and packaging fixes. Play Age Signals API v0.0.3 updates

If you have any questions, we're here to help!

read more...