> For the complete documentation index, see [llms.txt](https://docs.emobiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emobiq.com/emobiq-ai/readme/building-your-app/build-and-publish/android-build-and-publish.md).

# Android Build and Publish

## **Publishing Your Android App to Google Play Store**

Deploy your eMOBIQ-built Android app to the Google Play Store manually or via auto-publishing

This guide focuses **primarily on eMOBIQ AI’s workflow**. For detailed Android/Google Play steps, follow the linked official documents.

***

### **Build Settings**

#### **Prerequisites**

* A keystore File
  * *Don’t have one?* Follow this online guide on how to [Generate a keystore file](https://support.kotobee.com/en/support/solutions/articles/8000065886-create-an-android-keystore-file)
* A Google Play [**Developer Account**](https://play.google.com/console/u/0/signup) (Official Documentation: [setup guide](https://developer.android.com/distribute/console))
* A Google Cloud [Console Account](https://console.cloud.google.com/apis/api/androidpublisher.googleapis.com/overview?project=879362208751\&inv=1\&invt=Ab3bJg)

{% hint style="success" %}
*Tip: For different apps, a different keystore is recommended*
{% endhint %}

**Go to the** `Publish` Tab → `Settings` → Select `Android` → Build Settings

<figure><img src="/files/VTaTue5KabZkRJBHhnmZ" alt="" width="563"><figcaption></figcaption></figure>

***

### **Building Your App**

1. **Go to the** `Publish` Tab → `New Build` → Select `Android` → `Select Version` → `Build`

<figure><img src="/files/Jnxg1c1M4MkPwkZbuCrR" alt="" width="563"><figcaption></figcaption></figure>

2. Choose `.AAB` for deploying to Google Playstore

   <figure><img src="/files/eyQ3Q17O75Fz0wC2dMPM" alt="" width="375"><figcaption></figcaption></figure>

***

### **Deploy to Google Play**

**Link Google Play to eMOBIQ AI**

1. Google Service Account file in eMOBIQ AI refers to your Service account in [Google Console](https://console.cloud.google.com/)

<figure><img src="/files/r7qGeHDioE28HEJd8z3p" alt="" width="563"><figcaption></figcaption></figure>

2. Ensure that the Google Service Account and Google Play Console account is linked by navigating to `Users and permissions` tab → `Invite User` → Fill in the `Email address` with the Google Service Account you created

<figure><img src="/files/8V5HYZwcqfiN3nJNE2Ph" alt="" width="563"><figcaption></figcaption></figure>

3. Add your app and ensure App permissions and Account permissions are given full access
4. After building the app successfully and creating your Google Service account, navigate to `Settings` → `Android` → `Publish Settings` → `Upload` Service Account file in **JSON** format

<figure><img src="/files/Wy42HiuRtoPjL9qqYinu" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="warning" %}
*Note: App metadata (must match Google Play Console)*
{% 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.emobiq.com/emobiq-ai/readme/building-your-app/build-and-publish/android-build-and-publish.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.