Google Rejected My Play Store Production Access After 14 Days of Closed Testing (Here's What I Learned)
If you're an indie Android developer, you've probably run into one of the biggest hurdles in publishing on Google Play:
12 closed testers for 14 consecutive days.
Like many solo developers, I wanted to get through this requirement as quickly as possible.
I joined several "tester exchange" communities (including Testers Community and similar platforms), where developers install each other's apps to satisfy the requirement. I completed the process, waited the full 14 days, and confidently applied for Production access.
Instead, I received this email:
More testing required to access Google Play production
Possible reasons:
- Testers were not engaged with your app during your closed test.
- You didn't follow testing best practices, including gathering feedback and improving your app through updates.
That rejection forced me to rethink how closed testing actually works.
Why Tester Exchange Communities Didn't Work (At Least for Me)
On paper, these communities sound perfect:
- Get 12 testers quickly.
- Everyone helps each other.
- Wait 14 days.
- Publish.
In reality, my experience was very different.
1. Very little real engagement
Most people simply installed the app and never opened it again.
From a developer's perspective, that technically satisfies the install requirementùbut it doesn't look like genuine testing.
2. Almost no feedback
My closed testing track had almost no meaningful feedback:
- No private reviews
- No bug reports
- No discussions
- Very little evidence that anyone actually used the app
Whether Google explicitly checks these signals or not, the result was clear: my application was rejected.
3. No testing cycle
Real testing usually looks something like this:
- Users find issues
- Developer fixes them
- New version is released
- Testers verify the fixes
My testing period didn't resemble that process.
Looking back, I probably should have shipped at least one or two updates during the 14 days and encouraged testers to provide actual feedback.
What I'm Doing Differently
After the rejection, I'm treating the next closed test more like a real beta.
My plan is:
- Recruit people who are genuinely willing to use the app.
- Ask testers to leave private feedback in Google Play.
- Release updates based on that feedback.
- Keep communicating with testers throughout the 14-day period instead of simply waiting for the countdown to finish.
Hopefully that demonstrates an actual testing process rather than just meeting the minimum number of installs.
My Biggest Challenge
Finding 12 real, engaged testers is much harder than writing the app itself.
Friends and family usually install the app once and forget about it.
Tester exchange communities make it easy to get installs, but (in my experience) they don't necessarily provide meaningful testing.
So I'm curious how other indie developers are handling this in 2026.
- Where do you find engaged beta testers?
- Have you successfully passed the 12-tester requirement?
- Are there communities that focus on genuine testing rather than simply exchanging installs?
I'd really appreciate hearing your experiences.
I'm sure many solo Android developers are running into the same problem.
Top comments (0)