-
-
Notifications
You must be signed in to change notification settings - Fork 0
feat(news): news april 2026 #13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,148 @@ | ||
| --- | ||
| slug: 2026-04 | ||
| title: April 2026 | ||
| description: Extension Updates | ||
| image: images/adobeair.png | ||
| authors: [ marchbold ] | ||
| tags: [newsletter, inappbilling, facebookapi, nativewebview, agerange, playbilling] | ||
| --- | ||
|
|
||
| > 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. | ||
|
|
||
|
|
||
| :::tip Repository Migration Notice | ||
| We are migrating our GitHub repositories for native extensions from the [**distriqt**](https://github.com/distriqt) organisation to [**airnativeextensions**](https://github.com/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. | ||
| ::: | ||
|
|
||
|
|
||
| <!-- truncate --> | ||
|
|
||
| Here's a quick overview of the latest extension updates: | ||
|
|
||
| :::note Extension Updates | ||
| - [InAppBilling v18.1.0](https://github.com/distriqt/ANE-InAppBilling/releases/tag/v18.1.0) - Play Billing SDK v8.3.0 and `countryCode` support in `getUserData` | ||
| - [FacebookAPI v18.1.1](https://github.com/distriqt/ANE-FacebookAPI/releases/tag/v18.1.1) - iOS SDK update to v18.0.3 | ||
| - [NativeWebView v8.0.5](https://github.com/distriqt/ANE-NativeWebView/releases/tag/v8.0.5) - macOS focus-loss crash fix | ||
| - [AgeRange v0.3.0](https://github.com/airnativeextensions/ANE-AgeRange/releases/tag/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! | ||
|
|
||
|
|
||
| --- | ||
|
|
||
|  | ||
|
|
||
| ### [InAppBilling](https://airnativeextensions.com/extension/com.distriqt.InAppBilling) | ||
|
|
||
| [v18.1.0](https://github.com/distriqt/ANE-InAppBilling/releases/tag/v18.1.0) | ||
|
|
||
| This release updates Google Play Billing and improves user data support across platforms. | ||
|
|
||
| #### Updates | ||
| - Android: Updated Play Billing SDK to v8.3.0 | ||
| - Android and iOS: Added `countryCode` to `getUserData` functionality | ||
|
|
||
|
|
||
| --- | ||
|
|
||
|  | ||
|
|
||
| ### [FacebookAPI](https://airnativeextensions.com/extension/com.distriqt.FacebookAPI) | ||
|
|
||
| [v18.1.1](https://github.com/distriqt/ANE-FacebookAPI/releases/tag/v18.1.1) | ||
|
|
||
| This update keeps the iOS Facebook integration current and aligned with the latest SDK release. | ||
|
|
||
| #### Updates | ||
| - iOS SDK updated to v18.0.3 | ||
|
|
||
|
|
||
| --- | ||
|
|
||
|  | ||
|
|
||
| ### [NativeWebView](https://airnativeextensions.com/extension/com.distriqt.NativeWebView) | ||
|
|
||
| [v8.0.5](https://github.com/distriqt/ANE-NativeWebView/releases/tag/v8.0.5) | ||
|
|
||
| This release addresses a macOS stability issue seen in specific focus-change situations. | ||
|
|
||
| #### Updates | ||
| - macOS: Fixed a crash when WebView loses focus in particular situations | ||
|
|
||
|
|
||
| --- | ||
|
|
||
|  | ||
|
|
||
| ### [AgeRange](https://docs.airnativeextensions.com/docs/agerange/) | ||
|
|
||
| [v0.3.0](https://github.com/airnativeextensions/ANE-AgeRange/releases/tag/v0.3.0) | ||
|
|
||
| AgeRange v0.3.0 improves reliability and testing support around user status and error simulation. | ||
| The previous release (v0.2.0) updated the Play Age Signals API integration and introduced support for the new `SELF_DECLARED` status and `SDK_VERSION_OUTDATED` error handling path. | ||
|
|
||
| #### Updates | ||
| - Android: Handle `null` values for user status in both normal and fake result paths | ||
| - Android: Added ability to set fake error values for testing | ||
| - iOS: Added ability to set fake error values for testing | ||
| - AirPackage: Corrected dependencies and package metadata | ||
| - Android: Updated Play Age Signals API to v0.0.3 | ||
|
|
||
|
|
||
| --- | ||
|
|
||
|  | ||
|
|
||
| ## Further Information | ||
|
|
||
| As always, thank you for your continued support of distriqt and the AIR developer community. | ||
| Your feedback and contributions help us keep these extensions up to date and running smoothly across platforms. | ||
|
|
||
| - For full documentation and setup guides, visit [docs.airnativeextensions.com](https://docs.airnativeextensions.com) | ||
| - Join the AIR community discussions and get support at [github](https://github.com/airsdk/Adobe-Runtime-Support/) | ||
| - Publicly available extensions at [airnativeextensions](https://github.com/airnativeextensions) | ||
| - [Support](https://github.com/sponsors/marchbold) my ongoing involvement in the community | ||
|
|
||
| Stay tuned for more updates next month! | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.