Cómo actualizar la aplicación Android MemberPress

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.

1. Vaya a Panel de control > Aplicación MP > Compilar.
2. Haga clic en el botón Solicitar construir botón.

3. Compruebe el Android checkbox as the platform.
4. Seleccione Liberar aplicación como tipo de construcción.

5. Haga clic en Siguiente paso para proceder a la configuración de la compilación.
6. Haga clic en Enviar solicitud de construcción para enviar la solicitud de construcción.
7. Monitor the build progress under Historia de la construcción.
8. 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.

1. Vaya a Dashboard > MP App > Build.
2. Locate the completed release build in the builds list.
3. Haga clic en Install on Android device.
4. Click Descargar archivo AAB next to the release build.
5. Guarda el archivo AAB en una ubicación segura del dispositivo.

Nota: Google requires AAB files for all app submissions since August 2021. Previously published apps may continue using APK files for updates.

Submitting Update to Google Play Console

Update submission sends the new app version to Google for review.

1. Inicie sesión en Google Play Console en play.google.com/console.
2. Vaya a Todas las aplicaciones y selecciona la aplicación de la lista.

3. Haga clic en Release > Production en la barra lateral izquierda.
4. Haga clic en Crear nueva versión for new update submission.

5. Haga clic en Edit release if an existing draft release is present.
6. Desplácese hasta el Paquetes de aplicaciones y APK sección.
7. Haga clic en Cargar to open file selection.
8. Select the downloaded AAB file from the device.
9. Wait for upload completion and file processing.
10. Introduzca un Release name in the release name field.
11. Entre en Notas de publicación describing changes and improvements.
12. Haga clic en Guardar to store the release as a draft.
13. Haga clic en Revisión del lanzamiento to proceed to submission review.

Reviewing Update Configuration

Update review verifies version compatibility and release requirements.

1. Review the release summary page for errors or warnings.
2. Verify the version code is higher than previous releases.
3. Address all required errors before submission.
4. Optionally resolve warnings to improve update quality.
5. Confirm that release notes accurately describe changes.
6. Review countries and regions for update availability.

Nota: Version code must increment with each update for proper installation.

Submitting Update for Review

Update submission sends the release to Google's review team.

1. Review all updated details on the review page.
2. Verify no blocking errors remain in the configuration.
3. Haga clic en Start rollout to Production to submit the update.
4. Confirm submission in the confirmation dialog.
5. 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.

1. Inicie sesión en Google Play Console en play.google.com/console.
2. Navigate to the rejected app from the apps list.
3. Review rejection email for specific metadata concerns.
4. Haga clic en Store presence > Store listing to update listing content.
5. Correct problematic fields identified in rejection feedback.
6. Update the privacy policy URL if policy issues were identified.
7. Update content ratings if rating issues were identified.
8. Haga clic en Guardar after completing all necessary changes.
9. Return to the Release > Production página.
10. Haga clic en Start rollout to Production to resubmit the existing release.

Nota: Metadata updates do not require new AAB uploads for resubmission.

Resolving App Issues

App issue resolution requires code corrections and new build generation.

1. Review rejection email for specific app problems and violations.
2. Vaya a Dashboard > MP App en WordPress.
3. Address identified code issues or policy compliance problems.
4. Vaya a Panel de control > Aplicación MP > Compilar.
5. Haga clic en Solicitar construir to create a corrected version.
6. Seleccione Android plataforma y Liberar aplicación tipo de construcción.
7. Complete la solicitud de construcción y espere a que se complete.
8. Descargue el nuevo archivo AAB desde Historia de la construcción.
9. Navigate to the Google Play Console Production release page.
10. Haga clic en Crear nueva versión to begin a new submission.
11. Upload the corrected AAB file.
12. Enter release notes explaining fixes.
13. Haga clic en Revisión del lanzamiento y luego 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.

1. Navigate to Google Play Console at play.google.com/console.
2. Selecciona la aplicación de la lista de aplicaciones.
3. Haga clic en Publishing overview en la barra lateral izquierda.
4. Locate the approved update awaiting publication.
5. Review update details and approval status.
6. Haga clic en Go live to publish the approved update.
7. Confirm publication in the confirmation dialog.

Nota: Updates are distributed to existing users automatically after publication approval.