# Support Policy

## **Versioning strategy**

The iAdvize Mobile SDK follows [Semantic Versioning](https://semver.org/), that means that given a `x.y.z` version number:

* releasing critical bug fixes will change the `z` number: `3.4.5` -> `3.4.6` (PATCH release)
* releasing non-critical bug fixes or backward-compatible new features will change the `y` number: `3.4.5` -> `3.5.0` (MINOR release)
* releasing anything breaking the SDK public API will change the `x` number: `3.4.5` -> `4.0.0` (MAJOR release)

As versioning may differ from a platform to another, each iteration is given a codename so that it is easier to find the corresponding SDK on another platform.

## **Support status**

iAdvize Mobile SDK support comes in several distinct status:

* **Full support**: the SDK will receive bug-fixes and new features on a regular basis. MAJOR, MINOR and PATCH versions can be released upon it.
* **Partial support**: the SDK will receive security bug-fixes. Upon this version, only PATCH releases will be made, no MAJOR or MINOR. Update to the latest SDK is advized.
* **No support**: this SDK version is not supported anymore, update to the latest SDK is mandatory and unstable behaviours may occur during the use.

## **Release support lifecycle**

When a new MAJOR version is released, the previous MAJOR version enters a **grace period of 24 months**, at the end of which it reaches its **end-of-life**. After that moment, no support is provided on this version.

The **latest release** (most recent MAJOR.MINOR) is the only version that is **fully supported** by iAdvize.

In addition, several versions benefit from a **partial support**:

* the last 3 MINOR of the current MAJOR
* the last MINOR of previous MAJOR still in grace-period

## **Hybrid plugins**

Please be aware that the support policy only applies to the **native** iAdvize Mobile SDK (Android & iOS). Even though the hybrid plugin wrappers may have semantic versioning that differs from the native SDK, their support status is dependent on the native SDK version they embed.

## Supported versions

<table><thead><tr><th width="156.9453125">Status</th><th width="119.36328125">Codename</th><th width="110">Android</th><th>iOS</th><th>React Native</th><th>Flutter</th></tr></thead><tbody><tr><td>🟢 Full support</td><td>Herbillette</td><td><code>3.0</code></td><td><code>3.0</code></td><td><code>5.0</code></td><td><code>3.0</code></td></tr><tr><td>🟠 Partial support</td><td>Gaperon<br><em>(until March 2028)</em></td><td><code>2.16</code></td><td><code>2.18</code></td><td><code>4.4</code></td><td><code>2.17</code></td></tr><tr><td>🔴 No support</td><td>Any other version</td><td>Any other version</td><td>Any other version</td><td>Any other version</td><td>Any other version</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.iadvize.dev/technologies/web-and-mobile-sdk/mobile-sdk/support-policy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.