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

# Google Play Setup

> Create a Google Play Developer account, connect it to Newly, and choose the right Android build target.

## Prerequisites

To publish on the Play Store you need a [Google Play Developer account](https://play.google.com/console/signup) — a **one-time \$25 fee**, not a yearly one.

<Warning>
  Google verifies your identity when you sign up, which usually takes a day or two and occasionally longer. Start this early — it's the most common thing that delays a first Android launch.
</Warning>

You don't need the account to build an **APK** for testing. You need it before you can upload anything to Google Play.

## Choosing your Android build target

The Deploy modal has four Android targets. Pick the one that matches what you're actually doing:

| Target         | Produces                                             | Use it for                                                      |
| -------------- | ---------------------------------------------------- | --------------------------------------------------------------- |
| **Simulator**  | A build that runs in the in-browser Android emulator | Fast iteration while building                                   |
| **APK**        | An installable `.apk` file                           | Sideloading onto a real device, sharing with testers directly   |
| **AAB**        | A signed `.aab` bundle                               | Uploading to Play Console — internal testing through production |
| **Play Store** | Store-readiness checks for a public release          | Preparing a full public Play Store launch                       |

<Note>
  Only the **AAB** target takes you through the signing wizard, because only Play Store uploads need a release key. See [Android Signing Keys](/guides/android-signing-keys).
</Note>

## Connecting your Google Play account

Connecting Play Console lets Newly verify your Android store readiness against your actual developer account.

1. Open your project and go to the **Accounts** panel — or open the **Deploy** modal, select an Android store target, and find it in the readiness checklist
2. Click **Connect Google Play Console**
3. Sign in with the Google account that owns your Play Developer account and approve the permissions
4. You'll be returned to Newly, and the card switches to **Google Play Connected** showing the connected email address

To disconnect, click **Disconnect** on that same card.

<Tip>
  Use the Google account that actually owns (or has access to) the Play Developer account. A personal Gmail that isn't attached to Play Console will connect fine but won't be able to verify anything.
</Tip>

<Info>
  **Connecting Play Console is separate from your signing key.** The Google connection identifies *you* to Newly; the signing key identifies *your app* to Google. You need both, and losing one doesn't affect the other. Signing keys are covered in [Android Signing Keys](/guides/android-signing-keys).
</Info>

## Release tracks

Play Console gives you four release tracks, in increasing order of exposure. Your `.aab` is the same file for all of them — the track is chosen in Play Console when you create the release:

| Track                | Who sees it                                                          |
| -------------------- | -------------------------------------------------------------------- |
| **Internal testing** | Up to 100 testers you list by email; available within minutes        |
| **Closed testing**   | A larger invited group; required for new personal developer accounts |
| **Open testing**     | Anyone who opts in via a public link                                 |
| **Production**       | Everyone on the Play Store                                           |

<Warning>
  **If you registered a personal Google Play Developer account after November 2023**, Google requires you to run a **closed test with at least 12 testers for 14 consecutive days** before you can apply for production access. This catches a lot of first-time publishers by surprise — start your closed test as early as you can.
</Warning>

<Card title="Running a Google Play closed test" icon="users" href="https://newly.app/how-to/google-play-closed-testing">
  Step-by-step walkthrough of the 12-tester / 14-day requirement.
</Card>

## Restricted permissions

Some Android permissions — background location, SMS/call log access, and others — are classed as high-risk by Google. Requesting one triggers a **Permissions Declaration** in Play Console, and in most cases you need approval before your app or any update can publish.

<Card title="Permissions & Entitlements" icon="shield-check" href="/guides/permissions-and-entitlements">
  How to declare restricted Android permissions and apply for approval.
</Card>

## Troubleshooting

<AccordionGroup>
  <Accordion title="The connection succeeded but shows the wrong email">
    Click **Disconnect**, then reconnect and pick the correct Google account at the sign-in step. Google may sign you in silently with whichever account your browser is already using, so check the account picker rather than clicking straight through.
  </Accordion>

  <Accordion title="'Version code already used'">
    Every upload to Google Play needs a **higher version code** than the last one, and codes can never be reused — even for a release you deleted. Bump the version code on step 2 of the AAB wizard and rebuild.
  </Accordion>

  <Accordion title="Google Play rejects the package name">
    Check that `android.package` in your `app.json` matches the app you created in Play Console. Package names cannot be changed after your first submission — see [Changing your bundle ID](/guides/bundle-id-changes).
  </Accordion>

  <Accordion title="Play Console won't accept my APK">
    Play Store releases require an **AAB**, not an APK. Switch to the AAB target in the Deploy modal and rebuild.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Android Signing Keys" icon="key" href="/guides/android-signing-keys">
    Generating and safeguarding your release key
  </Card>

  <Card title="App Store Submission" icon="list-check" href="/guides/app-store-submission">
    Start-to-finish submission for both stores
  </Card>

  <Card title="App Deployment" icon="rocket" href="/features/deployment">
    How Newly builds APKs and AABs
  </Card>

  <Card title="Permissions & Entitlements" icon="shield-check" href="/guides/permissions-and-entitlements">
    Restricted Android permissions
  </Card>
</CardGroup>