Does Updating Your App Reset the 14-Day Closed Test?
Updated 27 September 2026
No. Publishing a new version to the same closed testing track does not by itself restart the 14 days; the requirement follows testers staying opted in. What restarts the count is the number of opted-in testers dropping below 12, or testers being removed, for example by moving to a new track or changing the tester list.
Updating is expected
Closed testing exists so you can fix issues testers report. Shipping updates during the 14 days is normal, and Google's production access questions ask what you changed based on feedback. Releasing fixes is evidence of real testing, not a problem.
What does reset the 14 days
- Fewer than 12 testers opted in on any day.
- Removing or replacing the tester Google Group or email list on the track.
- Moving testing to a different or new closed track.
- A release that is halted or rejected so testers no longer have a working app on the track.
How to update safely
- 1Upload the new build to the same closed testing track as a new release.
- 2Keep the same tester list on the Testers tab.
- 3Roll out the release and check it passes review.
- 4Note what you changed: you will describe it when you apply for production.
Frequently asked questions
Can I change my app's version during closed testing?
Yes. Release new versions on the same closed track; keep the tester list unchanged so testers stay opted in.
Will changing the package name reset testing?
Yes. A different package name is a different app in Play Console, with its own closed test and its own 14 days.