Introduction #
Keeping your Android app updated ensures your users receive the latest features, bug fixes, and accurate In-App Purchase pricing.
This guide walks you through generating a new Android Release build, downloading the AAB file, submitting it to Google Play Console, and addressing any review feedback from Google.
Creating a New Android Release App Build #
- In WordPress Admin, go to Learndash App > Build.
- Click Request Build.
- Select Android as the Platform and Release App as the Build Type.
- Click Next Step, then Send Build Request.
- Once complete, go to Build History.
- Click Download AAB File on your new release build.
Note: Since August 2021, Google requires AAB files for new submissions. APK uploads are only possible if previously published.
Save the downloaded AAB file securely, you will need it for the Play Store update.
Downloading Your Latest Build from WordPress #
- In WordPress Admin, go to Learndash App > Upload > Google Play Console.
- Select the Release build you want to update.
- Choose the file format (AAB recommended).
- Click Download Build.
Use AAB for new submissions. Legacy APK files remain supported if previously published.
Resubmitting to Google Play Console #
- Log in to Google Play Console.
- Under All apps, select your app.
- Go to Release > Production and click Create new release (or Edit release if one exists).
- In App bundles and APKs, click Upload and select your downloaded AAB.
- Enter a Release name and Release notes.
- Click Save, then Review release.
- Resolve any errors (required) or warnings (recommended).
- Click Start rollout to Production to submit for review.
Responding to Google Rejections #
- Metadata issues: Update your store listing, privacy policy, or content rating in Play Console, then resubmit the same release.
- App issues: Fix the reported issues in your code, rebuild the AAB, and follow the Create new release process again.
You will receive rejection details by email and can track status under your app in Play Console.
After Approval by Google #
- The update goes live immediately in the approved countries/regions.
- If Managed publishing is enabled, manually approve the release in the Managed publishing page for it to go live.
Troubleshooting and FAQs #
Q: Why can’t I upload my AAB?
A: Make sure the versionCode in your build is higher than any previous upload in Play Console.
Q: My release is stuck in “Draft” status.
A: Click Start rollout to Production. Saving alone does not publish your update.
Q: Can I revert to a previous version?
A: Yes. Upload the last working AAB as a new release and roll it out to Production.
Q: Do I need to repeat the Publishing Checklist for each update?
A: No. Once your app is live, future updates under the same App ID inherit the configuration. You only need to upload the new AAB and roll out.
Q: My update is taking a long time to appear in the Play Store.
A: Google’s review time can vary from minutes to several days, depending on the complexity of the update.
Q: The Play Store says “Not available in your country” after update.
A: Check that your target countries are still selected under Release > Production > Countries/regions in Play Console.