Mobile SDK Support Policy

The Airship Mobile SDK support policy defines the support lifecycle for native and plugin SDKs, including version coverage, support status definitions, and how Maintenance windows are determined.

View as Markdown

This policy applies to the Airship Mobile SDKs:

Native Apple and Android libraries
SDK plugins and modules that wrap the native libraries: React Native, Flutter, Capacitor, Cordova, Unity, .NET MAUI

Airship follows Semantic Versioning for every SDK release. The goal is a predictable lifecycle so customers can plan upgrades.

Support status definitions

Airship assigns each SDK major version one of three support statuses:

Status	Definition	Version coverage
Active	The SDK version receives new features and bug fixes.	The current major version
Maintenance	The SDK version receives critical security patches and high-priority bug fixes on a best-effort basis, when the supporting framework and tooling allow Airship to ship a patch. A fix is not provided if it requires a major API change or a bump in the minimum required IDE or build-tool version.	The previous major version, for 12 months from the date it entered Maintenance
Unsupported (EOL)	The SDK version receives no updates, security patches, or technical support.	Any version past its Maintenance window

A major version enters Maintenance the day it is superseded by a newer major. The 12-month Maintenance clock starts on that date and is not extended by subsequent major releases. Maintenance is a migration window, not a support extension. Customers should plan their upgrade to the Active version well before the window closes. Once it does, the version is End of Life.

Note

Unsupported SDKs do not stop functioning when they reach End of Life. They no longer receive security patches, bug fixes, or technical support, so upgrade to the Active version as soon as possible.

OS and tooling compatibility

New SDK majors are planned around major IDE and toolchain releases. For example, a new Apple SDK major typically follows a new Xcode major. Compatibility with a new IDE, OS, or toolchain ships in the next Active major, and the prior major moves to Maintenance. Maintenance may receive best-effort patches for obvious build issues under the same rules above. Fixes that require a major API change or a bump in the minimum IDE or build-tool version are not provided.

SDK plugins and modules

Airship’s SDK plugins and modules (React Native, Flutter, Capacitor, Cordova, Unity, .NET MAUI) follow the same lifecycle as the native SDKs, with one difference: a major reaches End of Life on the date the last of its underlying native Airship SDKs reaches End of Life, even if its 12-month Maintenance window has not yet closed. While only one underlying native SDK is End of Life, the plugin stays in Maintenance, but patches are not provided for issues specific to the already-EOL platform.

Backports

New features and compatibility updates are not backported to older majors. To access the latest Airship capabilities, stay on the Active version.

Current support status by SDK version

The tables below show the current support status for each Airship SDK major version. Refer to the SDK changelogs for patch-level release history.

Apple SDK

The Airship Apple SDK integrates Airship’s customer experience platform into native iOS, tvOS, and visionOS applications.