Questions about your closed test
Find answers about setup, testers, payments and refunds. If your question is not here, ask us before choosing a plan.
Real testers. All 14 days. We’ll walk you through it.Illustrative conversation
The requirement
What Google actually asks for, and who is exempt.
If you created a personal Google Play developer account after 13 November 2023, you cannot publish to production until you have run a closed test with at least 12 testers opted in continuously for 14 days. Google introduced the rule with 20 testers in November 2023 and reduced it to 12 in December 2024. The 14-day window never changed.
Google describes this requirement as applying to personal Play Console accounts created after 13 November 2023. Organisation accounts and older personal accounts are not covered by this particular rule. Check your Play Console dashboard for the requirements that apply to your app. Keep testing future updates even after production access is granted.
How the service runs
From payment to production access.
Premium testing starts within 30 minutes after we receive a working closed-testing link. Your required testing period is counted from when the minimum tester target is active, not from when you created the track.
Add applime-testers@googlegroups.com under Google Groups in your Play Console track's Testers tab. Then submit your app name, Testing URL, app image and any testing instructions through the dashboard. We identify the package name from the URL. We never need your Play Console password.
In Play Console open Testing, then Closed testing, and open your track's Testers tab. Select Google Groups, add applime-testers@googlegroups.com, and save. Publish your testing release and share its Testing URL through the AppLime dashboard. Support can help with setup and never needs your Play Console password.
Keep the closed track live, do not remove testers or unpublish the release, and review the feedback and testing signals you receive. Google asks what testers did, what feedback they gave and what you changed, so keep brief notes and release fixes to the closed track when needed.
You apply for production access from the Play Console dashboard and answer questions about tester recruitment, engagement, feedback, changes and release readiness. Google says reviews usually take seven days or less, although they can take longer. Applime support stays available during the review.
Testers and legitimacy
Who the testers are, and whether this is allowed.
Yes. Every tester is a real person opting in with their own Google account and installing your app on a real Android device: Samsung, Xiaomi, Pixel, Realme, OnePlus, Vivo, Oppo and Motorola among them. Emulators and fake accounts do not satisfy Google and we do not use them.
Google's public requirement focuses on completing a closed test with enough opted-in testers and demonstrating meaningful testing. Google does not endorse Applime or certify third-party testing providers. A paid service is not a substitute for real use and honest feedback, so describe how you recruited testers truthfully in your production-access application.
Google's closed-test rule does not state that all testers must live in one specific country, but every tester must be eligible for the track and able to install the app. If your app or track has country restrictions, tell us before the test so availability can be checked.
Yes. Share Google's decision message so we can help you understand what needs attention. Google may ask for more testing because too few testers qualified or engagement was insufficient. Continue the closed test and address the reasons given before applying again. A policy issue needs its own fix; adding testers alone will not resolve it.
Price, payment and refunds
Why ₹249, and what happens if it goes wrong.
Applime keeps each purchase to one testing credit for one app. Choose 12, 15 or 25 testers and track the complete run from your dashboard.
Choose 12 testers for ₹249, 15 testers for ₹299 or 25 testers for ₹449. Standard and Premium provide extra testers and longer testing windows above Google's minimum.
Every plan includes our production-access guarantee: if access is rejected after your completed test, choose a full refund of your plan price or free retesting. Request it within 30 days of the rejection, under our refund policy. We issue approved refunds to the original payment method within 3 business days; the payment provider or bank can take a further 5 to 7 business days to credit the amount.
After a completed test, you can choose a full refund or free retesting for your full plan window under our refund policy. Exclusions include removing testers, stopping or deleting the track, applying too early, not providing a working link within 14 days of payment despite reminders, or Google removing your app or suspending your account during the test. Read the refund policy before paying.
Pay directly on our website through Razorpay using the payment methods available at checkout, including UPI, cards and netbanking. Each purchase adds one Basic, Standard or Premium testing credit to your account after payment is confirmed. There is no subscription.
Yes. Each app needs its own closed test, so buy and apply one credit per app. You can track every submitted app from the same dashboard.

Ready to start your closed test?
Create your account, buy one credit securely and submit your app from the dashboard.
12 real testers. 14 days. One payment.