Where is your closed test stuck?
Who needs 12 testers for 14 days?
Google requires personal developer accounts created after 13 November 2023 to run a closed test with at least 12 testers opted in continuously for the preceding 14 days before applying for production access. Check your own Play Console requirements and Google's current requirements.
An email-list entry, a Google Group membership, an install and an actual Play opt-in describe different steps. Keep your recruitment list separate from the opted-in count shown in Play Console. Reaching a number alone does not describe whether people could use your app or what you learned from their feedback.
AppFledge normally uses a 16-day testing window for new campaigns. That is the platform workflow, not a change to Google's 14-day requirement. Each participant's platform clock starts when they confirm their Play opt-in in AppFledge. Those self-reported confirmations do not verify Google's clock or production eligibility.
Prepare the release before inviting testers
- 1
Make a testable build
Choose a small set of important journeys: creating an account, completing the main task and recovering from a mistake. Try those journeys yourself and fix blockers before asking others to spend time on them.
- 2
Check the Play Console release
Complete the app setup and publish a release on the intended closed-testing track. Check its publication status, supported devices and country availability. Use Google's test-track setup instructions for the current Console controls.
- 3
Choose an access method
Use an email list for individually added testers or a Google Group for membership-based access. Configure the correct list or Group on the same track as the release. Sharing a Group's join link does not configure that track for you.
- 4
Send a complete invitation
Include the access instructions, Play opt-in link, device requirements, testing commitment and a few practical tasks. If your app needs a login, provide an appropriate test account without sharing private production credentials.
- 5
Walk through the invitation
Ask one eligible person to follow your instructions using the Google account on their Android device. Resolve confusing steps before inviting the rest of the group.
How do you find closed testers?
Start with people who can use the app on a supported Android device and tell you what happened. For a specialised app, invite people with the relevant interest or experience. Developer peers can help with usability and technical feedback, while intended users can reveal problems with the actual use case.
If finding and coordinating peers is your blocker, AppFledge offers a community exchange: add your app, test another builder's app and follow participation and updates from one workspace. The first app is free during beta, with testing time contributed in return. A fixed tester count or arrival date is not promised.
Compare practical ways to find Google Play testers and see the community workflow →
How do you solve common closed-testing problems?
Before recruiting more people, ask one affected tester where the process fails. Request the error text and device/Android version; avoid asking them to post their Google email or private screenshots in a public thread.
| Problem | What to check | Next step |
|---|---|---|
| The app is unavailable | Release status, track, country and device compatibility. | Confirm access in Play Console and retry the official opt-in link with an eligible tester. |
| The invitation works for some people | The Google account used in the browser, Group and Play Store. | Have the tester use the account that was actually granted access. |
| Group members cannot install | Actual membership and the Group configured on the release's track. | Complete the Group step, then the separate Play opt-in step. |
| Your list is full but opt-ins are low | Whether people only accepted your invitation or also joined through Play. | Follow up with clear instructions. Compare platform confirmations with the Console count. |
| People stop participating | Access blockers, task size, app stability and the original commitment. | Resolve the blocker, agree manageable tasks and ask for a useful update. |
| More testing is requested | The actual decision and instructions in Play Console and the account email. | Address the stated issue, keep testing and document what changed. |
Use the detailed access and installation checklist →
AppFledge can help coordinate testers and feedback. It cannot fix a broken build, change Google Group permissions or override a Play Console decision.
Make participation useful beyond the tester count
Give testers a concrete question for each session. For example: “Create a reminder, change its time, close the app and check whether your change is saved.” Ask for the steps, expected result, actual result and device details when something fails.
Respond to feedback while the test is running. Tell the tester which build contains a fix and ask them to try the same steps again. A record showing the original problem, a change and a follow-up is more useful than a collection of “done” messages.
In AppFledge, check-ins record reported activity and testing updates capture feedback. Credit rewards depend on the platform's activity and update requirements; a check-in alone does not earn credits. These community rules do not replace Google's own assessment.
Prepare your production-access answers from real evidence
Keep a short record of the app version tested, the journeys attempted, recurring problems, changes made and anything still unresolved. Review the current questions in Play Console and write about what actually happened in your test.
AppFledge provides an owner-only testing report and editable answer drafts based on recorded activity. Review those drafts against your own notes and Play Console. Missing evidence should remain missing rather than being replaced with an assumed success.
See an illustrative workflow and report example →
If production access was rejected, work through the recovery guide →
Official references and the community workflow
- Google: testing requirements for new personal developer accounts
- Google: set up an open, closed or internal test
- How testing works in AppFledge
This guide is published by AppFledge, an independent community service. Google Play controls its testing requirements and production-access decisions.
Have an Android app ready for closed testing?
AppFledge connects builders who test each other's apps. Your first app is free during beta; you contribute testing time in return. Tester availability and Google Play approval are not guaranteed.