How to Update Your Android Learndash App

Introduction #

Keeping your Android app up to date ensures users always have access to the latest features, bug fixes, and updated In-App Purchase pricing.

This guide walks you through generating a new Android Release build, downloading the AAB, submitting it to Google Play Console, and addressing review feedback.

Creating a New Android Release App Build #

1. In your WordPress admin, go to Learndash App > Build.
   
2. Click Request Build.
   

3. Select Android as the Platform and Release App as the Build Type.
   

4. Click Next Step, then Send Build Request.
   
5. When complete, go to Build History.
   

5. When complete, go to Build History.
   
6. Click Download AAB File on your new release build.
   

Note: Since August 2021, Google requires AAB files for new submissions. Previously published apps may still use APKs.

Save the downloaded AAB file in a secure location. You will need it for your Play Store update.

Downloading Your Latest Build from WordPress #

1. In WordPress admin, go to Learndash App > Upload > Google Play Console.
   
2. Select the Release build you want to update and choose the file format.
   
3. Click Download Build.
   

Note: Use AAB for new submissions; legacy APKs remain supported if previously published.

Resubmitting to Google Play Console #

1. Log into Google Play Console.
   
2. In All apps, select your app.
   
3. Under Release > Production, click Create new release (or Edit release if one exists).
   
4. In App bundles and APKs, click Upload and choose your downloaded AAB.
   
5. Enter a Release name and Release notes (as per your Publishing Checklist).
   
6. Click Save, then Review release.
   
7. Resolve any errors (required) or warnings (recommended).
   
8. Click Start rollout to Production to submit for review.
   

Responding to Google Rejections #

• Metadata Issues – Revise your store listing, privacy policy, or content rating in Play Console, then resubmit the same release.
  
• App Issues – Fix code-level issues, rebuild your AAB, and repeat the Create new release process.
  

You’ll receive detailed emails from Google and can track your submission status in Play Console.

After Approval by Google #

• If Managed publishing is OFF – Your app will go live immediately in approved regions.
  
• If Managed publishing is ON – You must manually approve the release before it appears in the store.
  

Troubleshooting & FAQs #

Q: Why can’t I upload my AAB?
A: Ensure the versionCode in your build is higher than any previously uploaded version.

Q: My release remains in “Draft” status.
A: You must click Start rollout to Production; saving alone does not publish the update.

Q: What if I only changed metadata?
A: Metadata-only changes still require a new release to be created and rolled out.

Q: Can I revert to a previous version if something breaks?
A: Yes. Create a new release using the last working AAB and roll it out to Production.

Q: Do I need to repeat the checklist for every update?
A: No. Once your app is published, future submissions under the same App ID inherit prior configuration. Just upload the new AAB and roll out.

Q: My AAB upload fails with a “signing” error.
A: Ensure the AAB is signed with the same key as previous versions. Changing keys will block updates.