1. Home
  2. Knowledge Base
  3. BuddyBoss App
  4. App Publishing
  5. How to Publish Your Android App to the Google Play Store

How to Publish Your Android App to the Google Play Store

Introduction

If you haven’t published your Android app yet, we highly recommend using the BuddyBoss Publishing Service. The BuddyBoss Publishing Team will review your app to ensure it complies with Google Play Store guidelines and, when it’s ready, publish it live using your own developer account.

Find out how to use the BuddyBoss Publishing Service.

This guide also shows you the manual flow: download your AAB, upload to a Production release, invite testers via Testing Tracks, and handle rejections all without leaving WordPress.

Before You Begin

Complete all steps in the Google Play Store Publishing Checklist and finalize your app customizations. Ensure that you have generated the required app screenshots for your white-label app.

Downloading the AAB File

  1. In WordPress Admin, go to BuddyBoss App > Upload > Google Play Console.
  2. Select the build you wish to publish, choose the file format, and click Download Build.

Note: Since August 2021, Google requires an AAB file for new submissions. If your app has been published before, you can still use APK files for your release builds.

Submitting Your App to Google for Review

  1. Log into your Google Play Console .
  2. On the Home page, click your app to open its details.
  3. In the sidebar under Test and release, select Production.
  4. Click Create new release (or Edit release if one already exists).
  5. In App bundles, click Upload and select the AAB file you downloaded.
  6. Enter a Release name and Release notes (as per your Publishing Checklist).
  7. Choose Save as draft or click Next to continue.

Reviewing and Submitting Your Release

  1. Review your release: resolve all errors before submission (warnings are suggestions).
  2. Click Start rollout to Production. Your app’s status will change to In review.
  3. Monitor your publishing status under your app’s title and Application ID.

Handling Google Rejections

If Google finds that your app doesn’t comply with the Google Play Policies, and rejects your release, you’ll receive an email with details:

  • Metadata Issues: Correct your store listing, privacy policies, or content ratings in Play Console and resubmit.
  • App Issues: Fix code-level problems, build a new version, and submit a new Production release.

After Approval

Once approved, your app goes live immediately in the regions specified in your Production Release.

  • If Managed Publishing is enabled, your app won’t go live until you approve it from the Managed Publishing page.

Publishing New Versions

To publish updates, repeat these steps: upload your new build and submit for review. For detailed instructions, refer to our tutorial on creating and uploading new app builds for Google Play Store submission.

Troubleshooting and FAQs

Q: Where do I find my downloaded AAB file?
A: After building, go to BuddyBoss App > Upload > Google Play Console and click Download Build next to your chosen build.

Q: I can’t upload my AAB. I am receiving an error about higher version code.
A: Ensure the build’s versionCode in your plugin matches or exceeds any previously uploaded build’s versionCode in Play Console.

Q: My release is stuck in “Draft” status.
A: Make sure you clicked Start rollout to Production. Drafts must be explicitly rolled out.

Q: Testers can’t access the Testing Track link.
A: Confirm you copied the exact URL under Testing > Closed testing > How testers join your test and that you added their emails under Testers and License testing.

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

Was this article helpful?

Related Articles

To speak to our Agency consultant, fill in the form found at our Contact Page.

  • Get Started

    Enter your name and email address to get started with your project...

  • This field is for validation purposes and should be left unchanged.

Not recently active