BUDDYBOSS WEB

Your community, courses and memberships on your own website.

BUDDYBOSS APP

Your own branded app on iOS and Android.

DONE FOR YOU

We build, launch and run it for you.

BuddyBoss website and mobile app

Web + App Done For You

$4,999 flat

Web Scale + Done For You Web

App Launch + Done For You App

PRICING

Web Pricing

Launch, Scale and Done For You Web.

From

$199

first year

App Pricing

Solo, Launch and Done For You App.

From

$499

first year

SITE + APP

Web + App Done For You

Your site and your app, built and run for you.

$4,999

flat, never rises

How to Fix an Android Package Name Mismatch

Updated

An Android package name mismatch can prevent you from uploading an APK or Android App Bundle (AAB) to your app in Google Play Console. To fix an Android package name mismatch, confirm that the Application ID configured in BuddyBoss exactly matches the package name already registered for your Android app in Google Play Console.

For an existing app, keep the registered package name and existing keystore unchanged. After correcting the Application ID, generate a new Android Release App build and make sure you upload the AAB to the correct app in Google Play Console.

Verify and Update the Application ID

  1. Check the Google Play Console error and note the package name Google expects for the app.
  2. In your WordPress Dashboard, navigate to BuddyBoss App > Configure > Android Settings.
  3. Locate the Application ID setting.
  4. Confirm that the Application ID exactly matches the package name associated with the app in Google Play Console.
  5. If it does not match, update the Application ID to the correct package name.
  6. Save your changes.
  7. Generate a new Android Release App build.
  8. Once the build is complete, upload the new AAB to the correct app in Google Play Console.

Important: If this is an existing app, do not change the Application ID to a new or different package name. It must match the package name already registered for that app in Google Play Console.

Do not replace or regenerate your existing keystore as part of this fix. Continue using the signing configuration associated with the existing Android app.

Also make sure you are uploading the AAB to the correct app in Google Play Console. Uploading a build to a different app profile will result in a package name mismatch.

Was this article helpful?

Subscribe to Our Newsletter

This field is for validation purposes and should be left unchanged.
This field is hidden when viewing the form

Can’t find the answer you’re looking for?

Our support team is here to help with anything the docs don’t cover.