So aktualisieren Sie die Android-App 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. Navigieren Sie zu Dashboard > MP App > Build.
2. Klicken Sie auf die Request Build Taste.

3. Prüfen Sie die Android checkbox as the platform.
4. Wählen Sie Release App as the build type.

5. Klicken Sie auf Nächster Schritt to proceed to build configuration.
6. Klicken Sie auf Send Build Request to submit the build request.
7. Monitor the build progress under Build History.
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. Navigieren Sie zu Dashboard > MP App > Build.
2. Locate the completed release build in the builds list.
3. Klicken Sie auf Install on Android device.
4. Click Download AAB File next to the release build.
5. Save the AAB file to a secure location on the device.

Anmerkung: 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. Log in to Google Play Console at play.google.com/console.
2. Navigieren Sie zu All apps and select the app from the list.

3. Klicken Sie auf Release > Production in the left sidebar.
4. Klicken Sie auf Create new release for new update submission.

5. Klicken Sie auf Edit release if an existing draft release is present.
6. Blättern Sie zum App bundles and APKs Abschnitt.
7. Klicken Sie auf Hochladen to open file selection.
8. Select the downloaded AAB file from the device.
9. Wait for upload completion and file processing.
10. Eingabe einer Release name in the release name field.
11. Eingabe Release notes describing changes and improvements.
12. Klicken Sie auf Speichern Sie to store the release as a draft.
13. Klicken Sie auf Review release 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.

Anmerkung: 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. Klicken Sie auf 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. Log in to Google Play Console at play.google.com/console.
2. Navigate to the rejected app from the apps list.
3. Review rejection email for specific metadata concerns.
4. Klicken Sie auf 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. Klicken Sie auf Speichern Sie after completing all necessary changes.
9. Return to the Release > Production Seite.
10. Klicken Sie auf Start rollout to Production to resubmit the existing release.

Anmerkung: 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. Navigieren Sie zu Dashboard > MP App in WordPress.
3. Address identified code issues or policy compliance problems.
4. Navigieren Sie zu Dashboard > MP App > Build.
5. Klicken Sie auf Request Build to create a corrected version.
6. Wählen Sie die Android platform and Release App build type.
7. Complete the build request and wait for completion.
8. Download the new AAB file from Build History.
9. Navigate to the Google Play Console Production release page.
10. Klicken Sie auf Create new release to begin a new submission.
11. Upload the corrected AAB file.
12. Enter release notes explaining fixes.
13. Klicken Sie auf Review release und dann 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. Select the app from the apps list.
3. Klicken Sie auf Publishing overview in the left sidebar.
4. Locate the approved update awaiting publication.
5. Review update details and approval status.
6. Klicken Sie auf Go live to publish the approved update.
7. Confirm publication in the confirmation dialog.

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