> 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/cordova/advanced/overriding-native-sdk-versions.md).

# Overriding native SDK versions

Batch Cordova Plugin depends on native Android and iOS SDKs. It is set to use latest patch version of the minor native SDK version that was available when the plugin was published.\
For example, Batch Cordova Plugin 3.0 was published when iOS and Android native SDKs' latest versions were 1.17.0: without having to update the plugin, it will automatically use 1.17.1 when available but not 1.18.

If you need a specific native SDK version, you can control it using a Cordova plugin variable:

* `BATCHSDK_ANDROID_VERSION` for Android. Syntax is a Gradle version specification.
* `BATCHSDK_IOS_VERSION` for iOS. Syntax is a Cocoapod Podfile version specification.

For example, forcing SDK 1.18 while keeping automatic patch updates would look like:

```bash
cordova plugin add @batch.com/cordova-plugin --variable BATCHSDK_ANDROID_VERSION="1.18.+" --variable BATCHSDK_IOS_VERSION="~> 1.18"
```

If you're using Ionic Capacitor, see their documentation regarding how to set Cordova plugin variables.

> Note: Versions earlier than 1.17.0 are not supported.


---

# 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/cordova/advanced/overriding-native-sdk-versions.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.
