> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mythex.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Android & Google Play

> Build your Mythex app for Android, download the file, or connect your own Google Play service account so every build goes to internal testing and the agent can manage your Play listing.

# Android & Google Play

## Without a Google Play account

Ask the agent to build for Android. When the card says **Ready to upload**, click **Download**.

![An Android build without Google Play: Ready to upload, with Download](https://mintcdn.com/mythex/CIs3OEtRfkVYDlLf/images/mobile-card-file.png?fit=max\&auto=format\&n=CIs3OEtRfkVYDlLf\&q=85\&s=66aecfc5baa1b7324e162a1c7c8cb765)

The file is an **AAB** (Android App Bundle), the format Google Play takes: upload it in Play Console under **Testing** or **Production → Create new release**. It stays downloadable for about 30 days in **Project settings → Mobile app**.

An AAB can't be installed directly on a phone; it's for Google Play.

## Connect Google Play

Connected, every Android build also goes to your app's **internal testing** track by itself, and the agent can manage your Play listing. You use **your own** Google service account, so Mythex can only reach the apps you give it.

**1. Create the app in Play Console (once)**

In [Play Console](https://play.google.com/console), **Create app**. Google doesn't let anything outside Play Console create apps. The agent tells you the name to use; the first build sets its package name.

**2. Create a service account and its key**

In [Google Cloud](https://console.cloud.google.com/iam-admin/serviceaccounts), pick or create a project → **Create service account** (any name; no Cloud roles needed) → open it → **Keys → Add key → Create new key → JSON**. A `.json` file downloads.

**3. Invite it in Play Console**

Play Console → **Users and permissions → Invite new users** → paste the service account's email (it ends in `iam.gserviceaccount.com`) → **App permissions → Add app** → your app → grant **Admin**, or at least: release to production, release to testing tracks, manage testing tracks, manage store presence → **Invite user**.

**4. Connect it in Mythex**

Drop the `.json` file in the **Connect Google Play** panel the agent shows (or **Project settings → Mobile app → Google Play account → Connect**). Mythex checks the key can manage your app before saving it. A key you connected to another of your projects is offered at the top.

![The Connect Google Play panel](https://mintcdn.com/mythex/CIs3OEtRfkVYDlLf/images/mobile-connect-google-play.png?fit=max\&auto=format\&n=CIs3OEtRfkVYDlLf\&q=85\&s=408505cd8ac6d588ba3dc59d0d16a6e4)

Then ask *"Send it to Google Play"*. The card shows a third step, **Sending to Google Play**, and ends at **In internal testing**.

![In internal testing, with a Play Console button](https://mintcdn.com/mythex/CIs3OEtRfkVYDlLf/images/mobile-card-play.png?fit=max\&auto=format\&n=CIs3OEtRfkVYDlLf\&q=85\&s=8d8b2a04b1830d1189684abd0e8a0fe8)

Internal testers you've added in Play Console can install it from the Play Store a few minutes later.

The build number Google checks (versionCode) is chosen for you, above anything already on Google Play, including builds you uploaded by hand.

## When something stops it

| Card | What to do |
| - | - |
| **Create the app in Google Play** | Create the app in Play Console (step 1), then ask the agent to send it again. The file is still downloadable. |
| **Give access in Play Console** | Invite the service account's email with access to this app (step 3), then ask again. |
| **Google Play refused the build** | Google's reason (for example, a target Android version that's too old) goes to the agent, which fixes the app and builds again. |
| **Reconnect Google Play** | Google no longer accepts the key (deleted or disabled). Connect a new one. |

## Going public

Internal testing is for you and your testers. For **production** (or closed/open testing), ask the agent — it asks you before anything reaches the public. A brand-new app's first production release waits as a draft until you finish its setup in Play Console (Data safety, content rating, pricing and countries); the agent tells you what's left.

## Remove access

Disconnect in **Project settings → Mobile app**. To cut access completely, also remove the service account in Play Console → Users and permissions, or delete its key in Google Cloud.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.