Skip to main content
Google requires personal developer accounts created after November 2023 to complete closed testing before publishing to production. Create a closed test with at least 20 testers for at least 14 days to gain production access.

​
Why do I need to create a closed test?

In November 2023, Google updated their rules and regulations to require anyone with a newly created personal developer account to run a closed app test with at least 20 testers who’ve been opted-in for at least 14 days in order to gain production access to publish an app to the Google Play Store. This means you’ll need to create a closed test in Google Play if you created your personal Google Developer account after 12/1/23, or if you see an error message that “you don’t have access to production yet” when trying to publish your app into production: Production access error

​
Creating a closed test

To release the app to a closed test, first upload the application file (.aab file) to the Google Play Store. To upload the AAB file:
  1. Log into the Play Console and select the app you want to work on:
2 log into Play Console.png 3 select app.png
  1. Once you’ve loaded the specific app, navigate to the Release section in the left dashboard menu.
  2. From the menu options under Testing, select Closed testing:
Closed testing menu
  1. On the closed testing page, click the dark blue button at the top right labeled either Manage track or Create track:
5 manage or create track.png
  1. Select the Testers tab:
6 testers tab.png
  1. Add the name and email address of at least 20 people who will test the app before it goes live (i.e. yourself, members of your team, etc.):
In order to be approved for the Play Store and production, you will need at least 20 beta testers to opt-in and download the app. It is highly recommended to add more than 20 to make sure this requirement is met.
  1. Scroll down and click Copy link to copy the testing link and keep it handy:
8 copy testing link.png
  1. At the top right corner of the page, select Create New Release (if there is already a release in progress, the button text will say Edit Release instead).
  2. Navigate to the App bundles section.

​
Adding the build - Option 1

If you’ve previously uploaded the AAB file, or if Kajabi has successfully sent the build to the Store automatically:
  1. Click the Add from library link:
9 add from library.png
  1. Choose the newest build that was uploaded. (The newest build will have the highest version code.):
10 newest app build.png Once the build file is added, continue on to add release notes.

​
Adding the build - Option 2

If the build wasn’t automatically uploaded, follow these steps to do it manually.
  1. If you haven’t downloaded the AAB file yet, follow these instructions to download it. If you already have the AAB file, move on to the next step.
  2. Drag and drop the downloaded AAB file onto the box that says “Drop app bundles here to upload.” Or, click Upload and select the AAB file:
11 drop bundle here.png It may take a few minutes for the AAB file to upload. Once the file is uploaded, continue on to add release notes.

​
Add release notes

Once you’ve completed either Option 1 or Option 2 and added the AAB file:
  1. Scroll down to Release details and confirm that you see two input fields, Release name and Release notes:
12 release details.png
  1. A Release name will populate automatically after the AAB file upload completes. You can update it if desired.
  2. Add any Release notes you’d like to share with app users. We recommend keeping initial release notes simple, such as “Welcome to the app.” Don’t mention anything about users purchasing content in the Release notes section.
If you’d like to support multiple languages in release notes, include the language reference codes for those languages. Here’s an example of using language reference codes for multiple languages: 13 release notes.png
  1. After entering Release notes, click Next at the lower right.
  2. Click Save.
You can now access the closed testing app at the testing link you copied above. Once the app has been downloaded and opted into by at least 20 people for at least 14 days, you can apply for production access.

​
Android app submission process

The steps below walk you through submitting the Android app for approval and publishing it.

​
Submitting the app for approval

  1. Log in to the developer account: Go to the Google Play Console. Sign in with the Google Developer account credentials.
  2. Select the app: Click on the name of the developer account. Select the app from the list (e.g., “Kajabi Branded App”).
  3. Initiate production submission: On the dashboard, find the option to apply the app for production:
android-submission-process-google-docs.png
  1. Complete the Closed Beta Questionnaire: You will be redirected to Google’s Closed Beta Questionnaire. Answers can be updated if necessary based on your business needs.
Note: We recommend following the response guide provided via email from bma.support@kajabi.com. If you have not received a guide or need help with these responses, please reach out to us.
  1. Await review and response: After submitting the Closed Beta Questionnaire, the app will undergo another review by Google. Google will either approve and publish the app or request additional information. If further questions arise, the Kajabi Branded App team will handle them.
By following these steps, you’ll ensure that the app is properly submitted for review and publication on the Google Play Store.

​
Publishing the production app

To publish the app once the production app has been approved:
  1. Log into the Google Play Console.
  2. In the left dashboard menu, navigate to the Release section.
  3. From the menu options under Testing, select Closed testing. (Or, if you used a different Testing option, such as Internal testing, select that option.)
  4. At the middle of the page, click Promote Release.
  5. Select Production:
14 production release.png You’ll be directed to a Production page with the app file already copied over: Production page
  1. Fill out release notes in the Release details section like you did above.
  2. Click Next at the lower right.
  3. On the next page, confirm that there are no errors.
  4. Click Save at the lower right.
Finally, you’ll see a popup asking if you want to navigate to the Publishing overview:
  1. Click Go to overview.
  2. Click Send changes for review to submit the app.