> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/developer/sdk/support-policy.md).

# Support Policy

This page describes how long each major version of our native SDKs (iOS, Android, and Web) receives updates, so you can plan upgrades with confidence. As a rule, we support the two most recent major versions of each SDK. The current one and the one right before it, and encourage all new integrations to start on the latest major.

| Version          | Status      | Support                                   |
| ---------------- | ----------- | ----------------------------------------- |
| Latest major (N) | 🟢 Active   | Full support: new features, all bug fixes |
| N - 1            | 🟡 Extended | Critical & security fixes only            |
| N - 2 and older  | 🔴 EOL      | No support, migration required            |

### Support definitions

* **Active:** the current major version. Gets new features and fixes for all bugs, and guaranteed compatibility with new OS releases.
* **Extended:** the previous major version, supported for 12 months after the new major's release. Only critical and security fixes; no new features.
* **EOL (End of Life):** no longer supported. We recommend upgrading as soon as possible; documentation is kept for reference only.

{% hint style="info" %}
We announce end-of-life dates at least 12 months in advance, via this documentation and our [GitHub repositories](https://github.com/BatchLabs).
{% endhint %}

### Current versions

These are the currently supported major versions for each platform.

| Platform | Active | Extended |
| -------- | ------ | -------- |
| iOS      | 3.4.0  | 2.1.3    |
| Android  | 3.4.0  | 2.1.2    |
| Web      | 5.0.0  | 4.4.0    |

### Migration guides

Every major release that introduces breaking changes is accompanied by a dedicated migration guide.

| Platform | Guide                                                                                                                                                                    |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| iOS      | [v1 → v2](/developer/sdk/ios/advanced/migration-guides/2x-migration.md) · [v2 → v3](/developer/sdk/ios/advanced/migration-guides/3x-migration.md)                        |
| Android  | [v1 → v2](/developer/sdk/android/advanced/2x-migration.md) · [v2 → v3](/developer/sdk/android/advanced/3x-migration.md)                                                  |
| Web      | [v2 → v3](/developer/sdk/web/advanced/2x-migration.md) · [v3 → v4](/developer/sdk/web/advanced/3x-migration.md) · [v4 → v5](/developer/sdk/web/advanced/4x-migration.md) |

### Plugin SDKs (React Native, Flutter, Cordova)

Our React Native, Flutter, and Cordova plugins wrap the native iOS and Android SDKs above. Their own plugin version follows a separate release cycle, but each plugin version pins to a specific native SDK version under the hood. Check the plugin's changelog and migration guides to see which native major it embeds:

* [Flutter migration guide](/developer/sdk/flutter/advanced/1x-migration.md)
* [React Native migration guide](/developer/sdk/react-native/advanced/8x-migration.md)
* [Cordova migration guide](/developer/sdk/cordova/migrations/5x-migration.md)

{% hint style="info" %}
Support for a plugin version depends on the support status of the native SDK it embeds. Upgrading the plugin is the recommended way to stay on a supported native version.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.batch.com/developer/sdk/support-policy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.