Android app updates ensure members access the latest features, bug fixes, and updated pricing. Regular updates maintain app functionality and compliance with Google Play Store requirements. This document explains how to generate new Android release builds, download AAB files, submit updates to Google Play Console, and handle review feedback.
Understanding App Updates
App updates deliver improvements and fixes to existing installations through the Google Play Store. Updates maintain the same application identifier and signing key as the original publication. Version codes must increase with each update to enable proper update detection and installation.
Creating New Android Release Build
Release build generation creates the updated app package for Google Play submission.
- Navegue até Dashboard > MP App > Build.
- Clique no botão Request Build botão.

- Verifique o Android checkbox as the platform.
- Selecione Release App as the build type.

- Clique em Próxima etapa to proceed to build configuration.
- Clique em Send Build Request to submit the build request.
- Monitor the build progress under Build History.
- Wait for the build completion status.
Build completion typically occurs within 5-10 minutes after request submission.
Downloading AAB Build File
AAB file download prepares the updated app package for Google Play Console upload.
- Navegue até Dashboard > MP App > Build.
- Locate the completed release build in the builds list.
- Clique em Install on Android device.
- Click Download AAB File next to the release build.
- Save the AAB file to a secure location on the device.

Submitting Update to Google Play Console
Update submission sends the new app version to Google for review.
- Log in to Google Play Console at play.google.com/console.
- Navegue até All apps and select the app from the list.

- Clique em Release > Production in the left sidebar.
- Clique em Create new release for new update submission.

- Clique em Edit release if an existing draft release is present.
- Role até o App bundles and APKs seção.
- Clique em Carregar to open file selection.
- Select the downloaded AAB file from the device.
- Wait for upload completion and file processing.
- Digite um Release name in the release name field.
- Entrar Release notes describing changes and improvements.
- Clique em Salvar to store the release as a draft.
- Clique em Review release to proceed to submission review.
Reviewing Update Configuration
Update review verifies version compatibility and release requirements.
- Review the release summary page for errors or warnings.
- Verify the version code is higher than previous releases.
- Address all required errors before submission.
- Optionally resolve warnings to improve update quality.
- Confirm that release notes accurately describe changes.
- Review countries and regions for update availability.
Submitting Update for Review
Update submission sends the release to Google's review team.
- Review all updated details on the review page.
- Verify no blocking errors remain in the configuration.
- Clique em Start rollout to Production to submit the update.
- Confirm submission in the confirmation dialog.
- Monitor submission status in Google Play Console.
Understanding Rejection Types
Google may reject update submissions for compliance or technical issues.
Metadata issues involve store listing content, privacy policy updates, or content rating changes. Metadata rejections require Play Console updates without new app builds.
App issues involve code problems, policy violations, or functionality defects. App issue rejections require code fixes, new builds, and complete resubmission.
Resolving Metadata Issues
Metadata issue resolution updates store information without rebuilding the app.
- Log in to Google Play Console at play.google.com/console.
- Navigate to the rejected app from the apps list.
- Review rejection email for specific metadata concerns.
- Clique em Store presence > Store listing to update listing content.
- Correct problematic fields identified in rejection feedback.
- Update the privacy policy URL if policy issues were identified.
- Update content ratings if rating issues were identified.
- Clique em Salvar after completing all necessary changes.
- Return to the Release > Production página.
- Clique em Start rollout to Production to resubmit the existing release.
Resolving App Issues
App issue resolution requires code corrections and new build generation.
- Review rejection email for specific app problems and violations.
- Navegue até Dashboard > MP App em WordPress.
- Address identified code issues or policy compliance problems.
- Navegue até Dashboard > MP App > Build.
- Clique em Request Build to create a corrected version.
- Selecione o Android platform and Release App build type.
- Complete the build request and wait for completion.
- Download the new AAB file from Build History.
- Navigate to the Google Play Console Production release page.
- Clique em Create new release to begin a new submission.
- Upload the corrected AAB file.
- Enter release notes explaining fixes.
- Clique em Review release e depois Start rollout to Production.
Understanding Post-Approval Behavior
Update behavior after approval depends on the managed publishing configuration.
Automatic publication occurs for apps without managed publishing enabled. Approved updates go live immediately in all configured regions.
Managed publishing requires manual approval before updating the publication. Updates await publisher action on the Managed Publishing page before distribution.
Approving Managed Publishing Updates
Managed publishing updates require manual approval for distribution.
- Navigate to Google Play Console at play.google.com/console.
- Select the app from the apps list.
- Clique em Publishing overview in the left sidebar.
- Locate the approved update awaiting publication.
- Review update details and approval status.
- Clique em Go live to publish the approved update.
- Confirm publication in the confirmation dialog.