Rejected Because Testers Weren't Active for 14 Days — Causes & Fixes
Common reasons Google doesn't count your 14 active days, and how to fix them so you don't restart from zero.
How Google counts "active testing"
Many developers assume that as long as a tester installs the app, that's enough. It isn't. Google wants evidence that the app is genuinely used on real devices — meaning testers need to open and interact with the app, not just install it and leave it idle. A device that has the app installed but never runs it may not count as active.
The 14-day clock only starts once you reach the minimum 12 opted-in testers, and it keeps running as long as the active condition holds. If you don't clearly understand the definition of "active," it's easy to believe you've met the requirement while Google hasn't recorded it yet.
Common reasons the count resets
The most common cause is the active tester count dropping below 12 midway. You might start with exactly 12, but if just a couple uninstall or stop opening the app, the number falls to 10–11 and the clock can stall or reset. Starting right at the threshold is the riskiest mistake.
Other causes include: testers actively opting out of the program, users switching phones and forgetting to reinstall, or the developer mishandling a track change or bundle swap. Some seemingly harmless configuration changes can interrupt the counting cycle. Be cautious whenever you touch a running track.
How to fix each situation
The foundational fix is to always keep backup testers. Don't start with exactly 12 — have 14–15 so that when a few drop out, you remain safely above the threshold. This is the single most effective way to guard against a reset.
Next, monitor your dashboard daily to catch early signs of a declining active count, and act immediately (remind or add testers) before it falls below 12. Finally, build a standard process: don't swap bundles or change track configuration carelessly during the 14-day window unless truly necessary and you understand the consequences.
Prevention with stable real testers
The root of most resets is unreliable testers: people forget, get busy, or simply lack the motivation to keep going. The most thorough prevention is to use a stable, professionally managed tester source.
BetaBox runs centrally managed real devices kept continuously active for the full required period, so you virtually eliminate human-side reset risk. If you've ever been rejected because testers weren't active enough, let BetaBox handle this part for your next cycle.
Need 12 real testers for closed testing?
BetaBox provides real Android devices, unique Google accounts, and guaranteed 14 continuous active days.
