> For the complete documentation index, see [llms.txt](https://docs.appmachine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmachine.com/share-your-app/google-play/update-android-app-short.md).

# Update Android app (short)

### **Release management - Upload your app** <a href="#e.-release-management-upload-your-app" id="e.-release-management-upload-your-app"></a>

**Prerequisites:** You've already downloaded the .AAB file from the Publishing page in AppMachine:

<figure><img src="/files/kIpAXH5Vc6xpTKkHCLUx" alt=""><figcaption><p>Under the Google Play section of the Publish page you'll find the Download option for the .AAB file.</p></figcaption></figure>

1. **Open the** [**Google play console**](https://play.google.com/apps/publish/?hl=en) and login with the right developer account

2. In the left side menu find the option **Release > Production** \
   ![](/files/77RSHe0ekHrcTanc0L0g)

3. To create a new release, click **Create new release** in the top-right corner

4. Open a Finder on your Mac machine and look for an AAB file with a name which looks like this:<br>

   <figure><img src="https://s3-eu-central-1.amazonaws.com/euc-cdn.freshdesk.com/data/helpdesk/attachments/production/80116790801/original/TCvsUKYJbBVTeFoPehMdsyvIocAoktQIwg.png?1656323470" alt=""><figcaption></figcaption></figure>

5. **Drag and drop the AAB.file** onto the screen in de App Bundle area, or by using the **Upload** button displayed on the page.\
   \
   \&#xNAN;*On Mac devices, you cannot use the Upload button* \
   \
   \&#xNAN;*If you cannot find the AAB file on your computer, you can always download it again from the publish page.*\
   \ <mark style="color:red;">**Important: If you receive a notification about enrolling in Play App Signing, please contact AppMachine Support through <support@appmachine.com>.**</mark><br>

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

6. A name for the release will automatically be filled in, so leave this field as is. You do have the option to enter Release Notes. But you can also leave the default value as shown below:<br>

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

7. **Save** your changes in the bottom-right corner of the screen

8. Click **Next** in bottom-right corner.

9. Review the new version and click **Save** to continue the process. If any policy related matters occur at this time you can resolve them. If you need any assistance with this contact us at <support@appmachine.com>.&#x20;

10. Click the **Go to overview** button.\ <br>

    <figure><img src="/files/1HxWaVr7Qj4O2Tvg0l3I" alt=""><figcaption></figcaption></figure>

11. If there are no policy related matters that still need your attention, you can click the **Send 1 change for review** button to submit your new app version. <br>

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

12. Your app is now in review<br>

    <figure><img src="https://s3-eu-central-1.amazonaws.com/euc-cdn.freshdesk.com/data/helpdesk/attachments/production/80112276022/original/R-H7QJwsv80QBW-3QHCsVNZ1FIs5I7kCRg.png?1654944809" alt=""><figcaption></figcaption></figure>

In case the app is rejected -or suspended as Google calls it- you will receive an email notification from Google on the owner email address of your Google Play developer account explaining why the app was suspended and what needs to be changed.\
\
The time it takes Google to review is generally anywhere between 1-3 days, depending on the amount of apps that have been submitted to Google.\
\
**Congratulations, you've successfully updated your Android app in the Google Play Store!**


---

# 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.appmachine.com/share-your-app/google-play/update-android-app-short.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.
