> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/codapay/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/integration-guide/create-android-build.md).

# Create Android Build

### Configure Android Settings:

After setting up the SDK configuration, you’ll also need to configure the Android settings. This ensures that your project includes the required Android dependencies for the Coda SDK.

1. **Go to the Coda menu**: `Coda → Modify Android Settings`
2. Verify dependency paths (leave defaults if unsure).
3. Click **Apply Android Settings** to automatically insert the required dependencies<br>

   <figure><img src="/files/EfeakOu4BlkskbIiOLnD" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
You can skip this "Configure Android Settings" section, if you have already did it before, the Android Settings needs to be configured only once, before the first build you create.
{% endhint %}

### **Create Android build**:&#x20;

Go to `File → Build Settings` and make sure your current scene is added under Scenes in Build. If it’s not listed, click Add Open Scenes, then click Build or **Build And Run.**

<figure><img src="/files/JOPP8eG18mAysJS6FrFD" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If you want to do "Build And Run" on physical device, make sure device is connected to your machine and is getting detected under Run Device dropdown, similarly if If you want to do "Build And Run" on android emulator, make sure your emulator is already running before you hit "Build And Run" and select your emulator as Run Device in Build Settings.
{% endhint %}

{% hint style="warning" %}
Make sure your Package Name inside `Player Settings → Other Settings` and Complete landing page URL in Coda Publisher Portal matches. If your package name is `com.yourcompany.yourapp` then, your Complete landing page URL in Coda Publisher Portal should be `coda://yourapp.yourcompany.com`
{% 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 dynamically by asking a question.

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

```
GET https://docs.coda.co/codapay/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/integration-guide/create-android-build.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.