How to Update Your BuddyBoss Android App

Introduction

Keeping your Android app up to date ensures your users always have the latest features, fixes, and In-App Purchase pricing. This guide walks you through generating a new Android Release build, downloading the AAB, resubmitting it to Google Play Console, and handling review feedback.

Creating a New Android Release App Build

1. Go to BuddyBoss App > Build in your WordPress admin.
   
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.
   
6. Click Download AAB File on your new release build.
   
7. 

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

Save this AAB somewhere safe, you’ll need it to update your Play Store listing.

Downloading Your Latest Build from WordPress

1. In WordPress Admin, go to BuddyBoss 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 your 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 store listing, privacy policy, or content rating in Play Console, then resubmit the same release.
  
• App Issues: Address code-level problems, rebuild your AAB, and repeat the Create new release process.
  

You’ll receive email details and can track status under your app’s name in Play Console.

After Approval by Google

Once approved, your new version goes live immediately in the specified countries and regions.

• If Managed publishing is enabled, you must manually approve the release on the Managed publishing page before it appears.
  

Troubleshooting & FAQs

Q: Why can’t I upload my AAB?
A: Ensure the versionCode in your build exceeds any previously uploaded version in Play Console.

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

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 published, future submissions under the same App ID inherit prior configuration. Just upload the new AAB and roll out.