My first Android app was ready in January.
I didn't get production access until March.
Not because of bugs. Not because of rejections. Because I reset the 14-day closed testing clock three times in a row, and each time I didn't understand why until it was too late.
Here's what happened, and what I'd do differently.
Reset #1: I recruited exactly 12 people
The Google Play requirement says 12 testers. I recruited exactly 12.
On day 8, one of them texted me: "Hey, I needed to free up storage, I deleted your app. Want me to reinstall?"
I now had 11 active testers.
Clock reset.
Lesson: Recruit 16-18 people and treat 12 as your floor, not your target. The extra testers are insurance. When someone inevitably drops off, you absorb it.
Reset #2: Wrong Google account
Three of my 12 testers had multiple Google accounts. Personal and work, or two personal accounts.
I added their primary email to the list in Play Console. I sent the opt-in link. They clicked it.
But they clicked it while signed into their secondary account. Not the one I added.
They showed as opted in on their end. They showed as zero on mine.
I thought I had 12 testers for 2 weeks. I had 9.
Lesson: When you send the opt-in link, explicitly tell each tester: "Use this exact email address: [email]. If you're signed into a different account on your phone, sign out first and sign back in with this one."
Reset #3: I thought 14 days was automatic
After fixing the account issue, I hit 12 real testers. I checked Play Console on day 1 and saw the testing period was active.
I stopped checking.
On day 14, I went to request production access and found my testing period had ended on day 11. One tester's device had become incompatible after an Android update. Their status flipped to inactive. I didn't notice. By the time I caught it, the clock had already reset and was at day 3 of a new attempt.
Lesson: Check your active tester count daily. Not weekly. Not whenever you remember. Every day. Set a reminder.
What the third time looked like
By this point I'd spent 6 weeks on closed testing alone. I was done with the DIY approach.
I used TestLaunch Pro for the second attempt. They delivered 12 testers same day, and they replace anyone who goes inactive automatically. I didn't have to check anything. On day 14, all 12 were still active and I submitted production access that afternoon.
App went live 5 days later.
Total time with professional testers: 19 days. Total time doing it myself: 6 weeks of pain plus missed launch window.
The things nobody tells you
Google sends testers zero notification. When you add someone to your list, Google sends them nothing. You have to send the opt-in link manually. They have to click it on their phone. They have to install from the Play Store after. Every step matters.
Internal testing doesn't count. I spent 2 weeks on the internal track before I realized it had no effect on production access. The requirement is specifically closed testing. Learn from my mistake.
The feature graphic is not your app icon. When I finally submitted and got rejected, one reason was a missing feature graphic. I had no idea what that was. It's a separate 1024x500px banner image shown at the top of your Play Store page. Not the icon. A completely separate asset you have to create.
Summary
If you're in the middle of closed testing right now:
- Check your active tester count every day
- Recruit 16+ people, not 12
- Double-check every tester is using the right Google account
- Make sure your store listing is fully complete before you even think about submitting
If you haven't started yet:
- Start today ” waiting until "the app is done" costs you weeks
- Decide early whether you're recruiting yourself or using a service
TestLaunch Pro handles the testers so you don't have to. 12 verified testers in 6 hours, dropout replacement included. From $49.99.
Top comments (0)