Blog
Google Play closed testing guide
Guides to Google Play closed testing: the 12-tester, 14-day requirement, applying for production access, ways to find testers, and how to use DUIRE.
Requirements
Human testers or automated real devices for Google Play closed testing: what each one gives you
Both can keep 12 testers opted in for 14 days. They differ in what you get for the production access questionnaire: feedback from people, or reliable daily runs with records. How Google reviews your test, the trade-offs of tester panels, swaps, and device-based services, and how to combine them.
31. okt 2026
Requirements
Closed testing countries/regions: why testers see 'not available in your country' and how to fix it
A closed testing track has its own countries/regions list, separate from your production release. Testers outside that list can't find or install your app — including the devices of a testing service. Where to change it in Play Console, how long it takes, and why removing a country later is safe.
31. okt 2026
How-to
Best Google Play closed testing services: 12 testers for 14 days
Fiverr gigs, Testers Community, PrimeTestLab, 12 App Tester, and DUIRE compared on price, real testers vs automated runs, what happens if Google rejects you, and what records you get. Taken only from each provider's own page on October 27, 2026; anything not on the page is marked "Not stated on their page."
21. okt 2026
Requirements
How to delete an app in Google Play Console: requirements, steps, 7-day restore, and package names
To delete an app in Play Console, you have to unpublish it and meet conditions such as having fewer than 1,000 active devices. Based on Google's Help Center documentation, we cover where the delete option is and what to enter, how to restore it within 7 days, whether you can reuse the package name afterward, and how to clean up apps and releases in testing.
14. okt 2026
Requirements
How to write your Google Play store listing: app name length, screenshot sizes, and icon specs
Character limits for the app name (30 characters), short description, and full description in your Google Play store listing, plus specs for the app icon, feature graphic, screenshots, and preview video — all in one place, based on Google's Help Center documentation. We also cover screenshot sizes that help with recommendations and what to watch for when changing your app name.
14. okt 2026
Requirements
How to fill out the Data safety form in Google Play Console: what 'collection' and 'sharing' mean, including SDKs
You have to complete the Data safety form even if your app doesn't collect any data, and apps on closed testing tracks are included. Based on Google's Help Center documentation, we cover the definitions of 'collection' and 'sharing', the steps to fill it out, data taken by third-party SDKs, and what happens if you get it wrong.
14. okt 2026
Requirements
How to run internal testing in Google Play Console: from adding testers to install links and ending the test
Internal testing is a track you can use even before finishing app setup, to quickly install builds for up to 100 testers. We cover the steps to add testers, upload a release, and send the install link, what to watch for when it overlaps with closed testing, and how to end the test. Internal testing doesn't count toward the 12-tester, 14-day requirement.
14. okt 2026
Requirements
Google Play Console App access: how to provide login details for review
If your app requires a login, you must provide login details in Play Console so Google's review team can access every feature. Based on Google's Help Center documentation, we cover when it's needed, what the credentials must meet (reusable, location, 2-step verification, English, QR codes), and what happens if the password expires.
14. okt 2026
Requirements
Privacy policy for Google Play apps: is it required, and where and how do you add it?
To publish an app on Google Play, you need to enter a privacy policy URL in Play Console. We cover whether apps that don't handle personal data need one, when you must link it in your store listing and inside the app, what the URL must meet, and where to enter it in Play Console.
14. okt 2026
Requirements
Can you delete a closed testing track? Pausing, deleting releases, and the effect on your 14 days
The Play Console Help Center doesn't describe a way to delete a testing track; to end a test, it tells you to pause the track. We cover what happens to testers when you pause, how to clean up wrong releases and testers, and what not to do during the 14 days.
14. okt 2026
Requirements
Google Play developer account fee: a one-time $25 — creating your account, identity verification, closing and refunds
The Google Play (Play Store) developer registration fee is a one-time payment of US$25, and there's no annual fee. Based on Google's Help Center documentation, we cover paying it by credit or debit card, the steps to create your account, the difference between personal and organization accounts, identity and device verification, and when you can get the registration fee refunded.
14. okt 2026
How-to
How to write a call for app testers: example posts you can adapt
The clearer your call for testers is about what you're asking and for how long, the more people stay until the end. We list seven things every post needs, example texts you can adapt — the recruiting post, opt-in confirmation, mid-test reminder, and thank-you message — and tips for reducing dropouts over the 14 days.
14. okt 2026
Requirements
How to publish an app on Google Play and what it costs: the full process for personal developers
From the US$25 developer registration fee and identity verification to app setup and the store listing, closed testing with 12 testers for 14 days, applying for production access, and launch — the whole process, costs, and timeline for personal developers publishing on Google Play, in one place.
14. okt 2026
Requirements
How to add testers in Google Play Console: email lists, CSV, Google Groups, and the opt-in link
Three ways to add testers to a Play Console closed test (typing emails, uploading a CSV, or Google Groups) and the steps from saving the list to sharing the opt-in link. We cover common CSV format problems, cases where people on the list don't count, and what to check when testers can't join.
14. okt 2026
Requirements
'Testers were not engaged with your app during your closed test': what it means and how to reapply
If your production access request was rejected with this message even after 12 testers and 14 days, Google decided there wasn't enough sign that the app was actually used during the test — not that you were short on testers. We explain what the message means, the causes that often overlap, and what to change before you apply again.
14. okt 2026
Requirements
How to apply for production access on Google Play and how long it takes: from eligibility to launch
The steps for applying for production access after 14 days of closed testing. We cover when you can apply, how long it takes from submitting the questionnaire to getting a result, what not to do while you wait, and how to release to production once you're approved.
14. okt 2026
Requirements
Closed testing stuck 'In review'? How long it takes and what to check
Closed testing releases and tester lists have to pass Google's review before they reach testers. Until review is done, the opt-in link doesn't appear and the 14 days don't start. We cover what to check first, such as whether you actually sent it for review and whether managed publishing is on, and what to do while you wait.
14. okt 2026
Requirements
Can you update your app during closed testing? The 14 days keep going — how and how often to update
Uploading a new version during closed testing doesn't break your 14 days. In fact, it's better to update, because the production access questionnaire asks what you changed. We cover how to upload an update in Play Console, how often and what to ship, and how updates can break your test.
14. okt 2026
Requirements
Internal vs. closed vs. open testing on Google Play: only one counts toward the requirement
Play Console has three testing tracks, but only closed testing counts toward the 12-tester, 14-day requirement. We explain who joins each track and when you can use it, why 14 days in internal testing don't count, and the order to use them in.
13. okt 2026
Requirements
Does Google Play closed testing need 12 or 20 testers?
The current requirement is 12. 20 was the number when the requirement was first introduced, and Google has said 12 since December 2024. We explain why older posts and paid services still say 20, why aiming for exactly 12 is risky, and how to keep a buffer.
13. okt 2026
How-to
Closed testing tester swaps: where to find them and where they fall apart
In a tester swap, developers join each other's apps as testers. It costs nothing and fills up quickly, but if your partner finishes first and uninstalls your app, your 14 days get longer again. We cover where to find swaps, how they work, four places they break down, and how to keep one going to the end.
13. okt 2026
How-to
What's in a closed testing final report, and where it helps in the production access questionnaire
When your closed test ends, we compile the device run records from the whole test into a single report. We go through what it contains and which questionnaire question each item supports. You can open a realistic sample report.
13. okt 2026
Requirements
How to answer the production access questionnaire (examples for each question)
When you apply for production access after your closed test, you have to answer questions about your testing. A person reads and evaluates your answers, so weak answers get rejected. We go through Google's three-part questionnaire one question at a time, with weak and strong answers side by side so you know what to write.
20. sept 2026
Requirements
Closed Testing 14 Days Not Counting? When It Starts and Resets
The 14 days start when your 12th tester opts in and count in full 24-hour blocks. What resets the count, and why Play Console may show 0 or not count your days.
7. okt 2026
Requirements
Google Play production access rejected? 7 reasons and fixes
Production access not approved after closed testing? It's usually fewer than 12 opted-in testers, a broken 14-day run, testers not engaged with your app, or thin questionnaire answers. Here's what each rejection means and what to fix before you reapply.
7. okt 2026
How-to
How to Get 12 Testers for Google Play Closed Testing (4 Ways)
Where to find 12 testers for Google Play closed testing — friends, Reddit and Discord, tester swaps, or paid services — and how to keep them opted in for 14 days.
13. okt 2026
Requirements
Why PWA, TWA, and WebView apps struggle in closed testing
Apps built with PWA, TWA, or WebView face the same Google Play closed testing requirement (12 testers, 14 days). The requirement doesn't care what kind of app you build, but apps that fill the screen with web content load their first screen slowly, making it hard for testers to really try them. We explain why the tester engagement Google reviews tends to suffer, the symptoms it causes, and how to prepare, such as cutting first-load time.
13. okt 2026
Requirements
When you don't need Google Play closed testing: affected account types and creation dates
The Google Play closed testing requirement applies to personal developer accounts created after November 13, 2023. Organization accounts and accounts created before then can release straight to production, while affected accounts must meet the requirement for every app. We cover the fastest way to check whether your account is affected and the points people often confuse.
13. okt 2026
Requirements
Google Play closed testing requirements: 12 testers, 14 days
To release an app on Google Play from a personal developer account, you must first run a closed test with at least 12 testers opted in for 14 days in a row. This guide covers who it applies to, how to create a track and add testers in Play Console, how the 14 days are counted, applying for production access and common rejections, and ways to find testers.
13. okt 2026