1. Home
  2. Knowledge Base
  3. Frequently Asked Questions
  4. BuddyBoss App FAQs
  5. Resolve Android In-App Purchase Billing Permission Issues

Resolve Android In-App Purchase Billing Permission Issues

Android In-App Purchase Billing Permission Issues can prevent Google Play from recognizing or allowing you to configure products for your BuddyBoss App. If you see the “Your app doesn’t have any in-app products yet” error, Google Play may not yet recognize your app’s billing configuration, or required billing and permissions information may be incomplete.

To resolve the issue, generate a BuddyBoss Android Release App build and upload its AAB file to a Google Play closed testing track. BuddyBoss Test App builds should not be used because they have a different Application ID and are not intended for Google Play release or billing configuration.

Upload an Android Release Build to Google Play

  1. Navigate to BuddyBoss App > Build and generate an Android Release App build.
  2. Once the build is complete, download the AAB file.
  3. Log in to the Google Play Console and select your app.
  4. Navigate to Testing > Closed testing.
  5. Create a new testing track, or open an existing track.
  6. Click Create new release.
  7. Under App bundles, upload the AAB file generated by BuddyBoss.
  8. Complete the release details and click Next or Save.
  9. Review the release and submit it to the closed testing track.

Important: Use an Android Release App build for this process. Do not upload a BuddyBoss Test App build because Test Apps use a different Application ID and are not intended for Google Play release or billing configuration.

Once Google Play recognizes the Release App and the required billing information is complete, return to your In-App Purchase configuration and continue creating or syncing your Android products.

Was this article helpful?

Related Articles

Subscribe to Our Newsletter

Stay In Touch

Subscribe to our Newsletter, and we’ll send you the latest news from BuddyBoss

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