View Categories

How to Generate Android Release Apps

Introduction #

Android Release Apps allow you to prepare production-ready builds for Google Play submission, real-world testing, and accurate In-App Purchase validation. Built using our cloud-based servers, Release Apps compile your site’s configuration, branding, menus, and any GitHub-connected customizations into an Android App Bundle (AAB) file.

While Test Apps are ideal for daily QA and rapid development previews, Release Apps are required for publishing to Google Play and verifying actual subscription pricing, durations, and purchase flows.

This guide will walk you through creating an Android Release App build, uploading it to a Google Play testing track, inviting testers, and managing build updates.

Release vs Test Apps #

Test Apps

  • Best for daily QA, stakeholder demos, and custom code previews.
  • Installable via QR code without using Google Play.
  • Simulate purchases with placeholder pricing (no real transactions).

Release Apps

  • Required for Google Play Store submission and live testing.
  • Generated as AAB files for Google Play upload.
  • Display actual pricing, subscription durations, and terms.
  • Enable genuine In-App Purchase transactions.

Creating an Android Release App Build #

  1. In WordPress Admin, go to Learndash App > Build.
  2. Click Request Build.
  1. Select Android as the Platform and Release App as the Build Type.
  2. Click Next Step, then Send Build Request.
  1. Wait for the build to complete.
  2. In Build History, click Download AAB File for the finished release build.

Note: Since August 2021, Google requires AAB uploads. APK uploads are only possible if previously published.

Uploading Your AAB to a Google Play Testing Track #

  1. Log in to the Google Play Console.
  2. Open your app under All apps.
  3. Under Release > Production, confirm your target countries/regions are set.
  4. Go to Release > Testing and choose Closed testing (recommended for In-App Purchase QA).
  5. Click Manage track (e.g., Alpha) > Create new release.
  6. In App bundles and APKs, upload your downloaded AAB.
  7. Under Release details:
    • Leave the auto-filled release name as is.
    • Paste the Learndash App release notes.
  8. Click Save, then Review release, then Start rollout to [track name].
  9. Wait for Google approval (may take minutes to days).

Inviting Testers to Your Track #

  1. In Play Console, go to Release > Testing > Closed testing and open the Testers tab.
  2. Under Email lists, select or create a new list.
  3. Add tester emails (must match their Google Play account) and click Save Changes.
  4. Scroll to How testers join your test and copy the join link.
  5. Share the link with testers.

Configuring License Testing #

  1. In the sidebar, go to Settings > License testing.
  2. Add the same tester emails and click Save Changes.

Testers can now install your Release App with full In-App Purchase functionality.

Updating Your Testing Track with New Builds #

  1. Generate a new Release App build in Learndash App > Build.
  2. In Play Console, go to Release > Testing > Closed testing > Manage track.
  3. Click Create new release, upload the new AAB, and start the rollout.
  4. Testers will see the update in their Play Store testing link.

Troubleshooting and FAQs #

Q: My testers can’t access the build.
 A: Make sure their exact Google Play account emails are added in both the Testers list and License Testing, and that Google has approved the testing track.

Q: In-App Purchase prices aren’t showing.
 A: Only Release Apps from an approved closed testing track display real pricing. Ensure testers install from the track URL.

Q: Build upload fails with “AAB version is lower than previous.”
 A: Increase the versionCode in your app’s build.gradle before rebuilding.

Q: Google rejected my build.
 A: Review the rejection email for specific policy violations and address them before resubmitting.

Q: Can I switch from Closed to Open testing?
 A: Yes. Go to Release > Testing and select your preferred testing type.

Q: My testers see “App not available in your country.”
 A: Verify your target countries are set under Release > Production in the Play Console.

Updated on September 23, 2025