{"id":10494,"date":"2025-09-22T20:07:05","date_gmt":"2025-09-23T00:07:05","guid":{"rendered":"https:\/\/learndash.com\/support\/?post_type=docs&p=10494"},"modified":"2026-04-22T08:30:00","modified_gmt":"2026-04-22T12:30:00","password":"","slug":"configure-google-play-closed-testing","status":"publish","type":"docs","link":"https:\/\/learndash.com\/support\/kb\/learndash-app\/uncategorized\/configure-google-play-closed-testing\/","title":{"rendered":"How to Configure Google Play Store Closed Testing"},"content":{"rendered":"\n

Introduction<\/strong><\/h2>\n\n\n\n


<\/strong>As of November 13, 2023<\/strong>, Google requires all new Individual Google Developer Accounts<\/strong> to complete a closed testing phase<\/strong> before publishing apps to the Production track in the Play Store. This process includes having at least 12 internal testers<\/strong> use the app for a minimum of 14 days<\/strong> before you can unlock production access.<\/p>\n\n\n\n

This requirement does not apply if your Google Developer Account was registered before November 13, 2023, or if you are using an Organization Account<\/strong>.<\/p>\n\n\n\n

Create a Closed Testing Track<\/strong><\/h2>\n\n\n\n
    \n
  1. Log into the Google Play Console<\/strong> and select your app.
    <\/li>\n\n\n\n
  2. In the left sidebar, go to Release > Testing > Closed Testing<\/strong>.
    <\/li>\n\n\n\n
  3. Choose from your active tracks:
    \n
      \n
    • If an existing track is available, click Manage Track<\/strong>.
      <\/li>\n\n\n\n
    • To create a new one, click Create Track<\/strong>.
      <\/li>\n<\/ul>\n<\/li>\n\n\n\n
    • Enter a Track Name<\/strong> and click Create Track<\/strong>.
      \n
        \n
      • If this is your first time uploading a build to a test track, you may need to accept Google\u2019s terms and conditions.
        <\/li>\n<\/ul>\n<\/li>\n\n\n\n
      • Go to the Countries\/Regions<\/strong> tab and select where your app should be available for testing.
        \n
          \n
        • To enable testing globally, check the box to select all countries.
          <\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n

          Add Testers to Your Closed Test<\/strong><\/h2>\n\n\n\n
            \n
          1. Go to the Testers<\/strong> tab.
            <\/li>\n\n\n\n
          2. Select an existing email list or click Create Email List<\/strong>.
            <\/li>\n\n\n\n
          3. Enter a List Name<\/strong> and add at least 12 email addresses<\/strong>.
            <\/li>\n\n\n\n
          4. Click Save Changes<\/strong>, then Create<\/strong>.
            <\/li>\n\n\n\n
          5. Add a Feedback URL<\/strong> or email address so testers can send feedback. Click Save<\/strong>.
            <\/li>\n\n\n\n
          6. Click Go to Overview<\/strong> when prompted.
            <\/li>\n<\/ol>\n\n\n\n

            Important:<\/strong><\/p>\n\n\n\n

              \n
            • Google requires a minimum of 12 testers<\/strong> to opt in to your closed test.
              <\/li>\n\n\n\n
            • The Copy Link<\/strong> option for the test will only appear after Google approves your release.
              <\/li>\n<\/ul>\n\n\n\n

              Create a New Release for Closed Testing<\/strong><\/h2>\n\n\n\n
                \n
              1. In your closed testing track, click Create New Release<\/strong>.
                <\/li>\n\n\n\n
              2. Under App Bundles<\/strong>, upload your .aab<\/strong> file or select one from your library.
                <\/li>\n\n\n\n
              3. Click Add to Release<\/strong>.
                <\/li>\n\n\n\n
              4. In Release Details<\/strong>, confirm the auto-filled version number and add Release Notes<\/strong>.
                <\/li>\n\n\n\n
              5. Click Next<\/strong>, then Save<\/strong>.
                <\/li>\n\n\n\n
              6. In the popup, click Go to Overview<\/strong>.
                <\/li>\n\n\n\n
              7. Click Send Changes for Review<\/strong>, then confirm again.
                <\/li>\n<\/ol>\n\n\n\n

                Google typically reviews a closed test release in 3\u20135 days<\/strong>. Once approved, you\u2019ll receive a Test Link<\/strong> to share with testers.<\/p>\n\n\n\n

                Configure License Testing<\/strong><\/h2>\n\n\n\n

                While waiting for approval:<\/p>\n\n\n\n

                  \n
                1. From the left sidebar, return to All Apps<\/strong>.
                  <\/li>\n\n\n\n
                2. Under Setup<\/strong>, click License Testing<\/strong>.
                  <\/li>\n\n\n\n
                3. Add license testers from your email lists and click Save Changes<\/strong>.
                  <\/li>\n<\/ol>\n\n\n\n

                  License Testing ensures only authorized testers can install and access the app.<\/p>\n\n\n\n

                  Run the 14-Day Closed Testing Period<\/strong><\/h2>\n\n\n\n

                  Once your closed test release is approved:<\/p>\n\n\n\n

                    \n
                  1. Share the Test Link<\/strong> with your 12+ testers.
                    <\/li>\n\n\n\n
                  2. Testers must opt in and use the app for at least 14 days<\/strong>.
                    <\/li>\n\n\n\n
                  3. Collect feedback to improve the app before production release.
                    <\/li>\n<\/ol>\n\n\n\n

                    Apply for Production Access<\/strong><\/h2>\n\n\n\n

                    After meeting the closed testing requirements:<\/p>\n\n\n\n

                      \n
                    1. In your app\u2019s Dashboard<\/strong>, click Apply for Production<\/strong>.
                      <\/li>\n\n\n\n
                    2. Answer questions about:
                      \n
                        \n
                      • Your closed test process.
                        <\/li>\n\n\n\n
                      • Your app\/game details.
                        <\/li>\n\n\n\n
                      • Production readiness.
                        <\/li>\n<\/ul>\n<\/li>\n\n\n\n
                      • Submit your request for review.
                        <\/li>\n<\/ol>\n\n\n\n

                        Review Timeline:<\/strong><\/p>\n\n\n\n

                          \n
                        • Usually 7 days or less<\/strong>.
                          <\/li>\n\n\n\n
                        • Once approved, the Production<\/strong> tab will be unlocked so you can upload your final build for public release.
                          <\/li>\n<\/ul>\n\n\n\n

                          After Gaining Production Access<\/strong><\/h2>\n\n\n\n
                            \n
                          1. Create a release in the Production<\/strong> track.
                            <\/li>\n\n\n\n
                          2. Upload your final app build.
                            <\/li>\n\n\n\n
                          3. In WordPress, go to Learndash App > Publishing Service > Google Play Store<\/strong>.
                            <\/li>\n\n\n\n
                          4. Submit a publishing request.
                            <\/li>\n\n\n\n
                          5. The Publishing Team will manage the app submission and provide updates via email.
                            <\/li>\n<\/ol>\n\n\n\n

                            Troubleshooting and FAQs<\/strong><\/h2>\n\n\n\n

                            Q: Do I need closed testing if I have an Organization Developer Account?<\/strong>
                            <\/strong> A: No, this applies only to new Individual Developer Accounts<\/strong>.<\/p>\n\n\n\n

                            Q: Can I skip the 14-day testing period?<\/strong>
                            <\/strong> A: No, Google enforces this for all new individual accounts.<\/p>\n\n\n\n

                            Q: What happens if I add fewer than 12 testers?<\/strong>
                            <\/strong> A: You will not meet Google\u2019s requirement, and production access will remain locked.<\/p>\n\n\n\n

                            Q: When can I share the test link?<\/strong>
                            <\/strong> A: Only after Google approves your closed test release.<\/p>\n\n\n\n

                            Q: How long does Google take to review a closed test release?<\/strong>
                            <\/strong> A: Usually 3\u20135 days<\/strong>, but it can take longer in some cases.<\/p>\n\n\n\n

                            Q: How long does production access review take?<\/strong>
                            <\/strong> A: Normally 7 days or less<\/strong> after you apply for production.<\/p>\n","protected":false},"excerpt":{"rendered":"

                            Introduction As of November 13, 2023, Google requires all new Individual Google Developer Accounts to complete a closed testing phase before publishing apps to the Production track in the Play Store. This process includes having at least 12 internal testers use the app for a minimum of 14 days before you can unlock production access….<\/p>\n","protected":false},"author":58,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_helpful_status":1,"_kad_blocks_custom_css":"","_kad_blocks_head_custom_js":"","_kad_blocks_body_custom_js":"","_kad_blocks_footer_custom_js":"","_swpsp_post_exclude":false,"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"footnotes":""},"doc_category":[],"doc_tag":[],"knowledge_base":[283],"class_list":["post-10494","docs","type-docs","status-publish","hentry","knowledge_base-learndash-app"],"year_month":"2026-04","word_count":662,"total_views":"1312","reactions":{"happy":"0","normal":"0","sad":"0"},"author_info":{"display_name":"Stephanie Liy","author_link":"https:\/\/learndash.com\/support\/author\/stephaniei\/"},"doc_category_info":[],"doc_tag_info":[],"taxonomy_info":{"knowledge_base":[{"value":283,"label":"LearnDash App"}]},"featured_image_src_large":false,"comment_info":0,"knowledge_base_info":[{"term_name":"LearnDash App","term_url":"https:\/\/learndash.com\/support\/kb\/learndash-app\/","term_slug":"learndash-app"}],"knowledge_base_slug":["learndash-app"],"_links":{"self":[{"href":"https:\/\/learndash.com\/support\/wp-json\/wp\/v2\/docs\/10494","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/learndash.com\/support\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/learndash.com\/support\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/learndash.com\/support\/wp-json\/wp\/v2\/users\/58"}],"replies":[{"embeddable":true,"href":"https:\/\/learndash.com\/support\/wp-json\/wp\/v2\/comments?post=10494"}],"version-history":[{"count":1,"href":"https:\/\/learndash.com\/support\/wp-json\/wp\/v2\/docs\/10494\/revisions"}],"predecessor-version":[{"id":10495,"href":"https:\/\/learndash.com\/support\/wp-json\/wp\/v2\/docs\/10494\/revisions\/10495"}],"wp:attachment":[{"href":"https:\/\/learndash.com\/support\/wp-json\/wp\/v2\/media?parent=10494"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/learndash.com\/support\/wp-json\/wp\/v2\/doc_category?post=10494"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/learndash.com\/support\/wp-json\/wp\/v2\/doc_tag?post=10494"},{"taxonomy":"knowledge_base","embeddable":true,"href":"https:\/\/learndash.com\/support\/wp-json\/wp\/v2\/knowledge_base?post=10494"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}