How to Generate Android Release Apps for Your BuddyBoss App

Introduction

Building and distributing Android Release Apps is straightforward with our cloud-based build servers. They pull your site’s configuration, branding, menus, and any GitHub-connected customizations, then compile everything into an Android App Bundle (AAB) that is ready for Google Play submission or testing. While Test Apps support your daily QA and custom development, Release Apps let you verify real In-App Purchase pricing, terms, and prepare production rollouts.

This guide shows you how to create an Android Release App build, upload it into a Google Play testing track, invite testers, and distribute your AAB via a secure track URL.

Release vs Test Apps

Test Apps

• Used for daily QA, stakeholder demos, and rapid custom-code previews
• Installable via QR code without App Store involvement
• Allow you to view products and perform fake “purchases” to test flows
• Show placeholder pricing and terms (no real In-App Purchase data)
  

Release Apps

• Intended for Google Play Store submission and real-world testing
• Generated as AAB files and uploaded to Google Play testing tracks
• Required to display actual pricing, subscription durations, and terms
• Enable genuine In-App Purchase transactions via Google’s billing system

Creating an Android Release App Build

Go to BuddyBoss App > Build, then click Request Build.

1. Select Android as the Platform and Release App as the Build Type.
   
2. Click Next Step, then Send Build Request.
   
3. Once complete, open Build History and click Download AAB File on the finished release build.
   

Note: Since August 2021, Google requires AAB uploads. Legacy APK uploads remain available if previously published.

4. Save the AAB file for uploading to Google Play.
   

Uploading Your AAB to a Google Play Testing Track

1. Log in to the Google Play Console and open your app under All apps.
   
2. Under Release > Production, ensure your target countries or regions are configured.
   
3. Under Release > Testing, choose Closed testing (recommended for In-App Purchase QA).
   
4. Click Manage track (e.g., Alpha), then Create new release.
   
5. In App bundles and APKs, upload the AAB you downloaded.
   
6. Under Release details:
   
   • Release name auto-fills with your version. Leave it as is.
     
   • Release notes: paste the BuddyBoss App release notes for context.
     
7. Click Save, then Review release, and Start rollout to [track name].
   
8. Wait for Google’s approval. This may take minutes or days.
   

Inviting Testers to Your Track

1. In your Play Console, go to Release > Testing > Closed testing and click the Testers tab.
   
2. Under Email lists, select an existing list or Create email list.
   
3. Add testers’ email addresses (comma-separated), press Enter, then Save Changes. Emails must match their Google Play accounts.
   
4. Scroll to How testers join your test, copy the Join on Android link, and share it.
   

Configuring License Testing

1. In the sidebar, go to Settings > License testing.
   
2. Under Add license testers, enter the same tester emails (comma-separated), press Enter, then Save Changes.
   
3. Testers can now access your Release App build via the shared testing-track URL, with full In-App Purchase functionality.
   

Updating Your Testing Track with New Builds

To roll out a newer AAB to the same track:

1. Generate a fresh Release App build in BuddyBoss App > Build.
   
2. In the Google Play Console, revisit Release > Testing > Closed testing > Manage track > Create new release.
   
3. Upload the new AAB, Save, Review release, and Start rollout to [track name].
   
4. Testers will see the updated build in the Play Store testing link.
   

Troubleshooting & FAQs

Q: My testers can’t access the new build.
A: Confirm you added their exact Google Play emails under both Testers and License testing and that Google approved the testing track.

Q: In-App Purchase prices aren’t showing in the testing build.
A: Make sure your AAB is uploaded to a closed testing track, and testers install via the track URL. Only Release Apps pulled from a Google-approved track display real pricing and terms.

Q: Build upload fails with “AAB version is lower than previous.”
A: Ensure your AAB’s versionCode in build.gradle is higher than any prior upload to Google Play.

Q: Can I switch from Closed to Open testing later?
A: Yes, under Release > Testing, select Open testing or Internal testing, then manage the track similarly.