Get Help with Google Play Closed Testing
Have questions about the 14-day policy, Play Console track configuration, or handling a previous rejection? Our team of Android developers is here to assist you.
How to Reach Us
Reach out via our secure contact form or email our advisory desk directly.
Was your app rejected by Google Play after testing on your own? Paste the text or attach Google\'s feedback message. We will diagnose the cause (e.g. low tester activity, lack of updates, vague answers) and recommend the fastest resolution path.
Frequently Asked Support Questions
How quickly does the OnTesters support team respond?
We typically reply within 2 to 4 hours during business days. For active testing campaigns, our developer advisory team monitors queries around the clock.
Can OnTesters review my rejection notice before I start a new campaign?
Yes. If you were previously rejected by Google after testing on your own or with another service, send us your rejection notice. We will diagnose the root cause and advise on the necessary telemetry and update strategy.
Do I ever need to share source code or Play Console login credentials?
Never. We will never ask for your Google Play Console password, developer credentials, or proprietary source code. Testers join exclusively through your official Play Console opt-in link.
What happens if a tester drops out during my 14-day test?
We monitor daily tester engagement and maintain a buffer of 2 extra testers. If any tester drops out, we automatically assign a replacement at zero extra cost so your count stays above 12.
Can I test multiple apps simultaneously?
Yes. Each app requires its own closed testing cycle with 12 testers. You can launch and manage multiple app campaigns concurrently from your single OnTesters dashboard.
How does the production access refund guarantee work?
If Google rejects your production access application citing tester engagement issues, we issue a 100% refund. Simply forward your rejection notice within 30 days of completing your test.