Does uploading an update during the test reset the clock?

In short: nothing on Google's official pages says that a new release resets the 14 days. On the contrary, Google recommends updating your app in closed testing before production. What's explicitly stated to break the 14 days is a tester leaving the test.

Last checked: Source: Play Console Help

Leave the test to us

12 testers plus 3 backups, 14 days in a row. Follow every day on a live table.

See packs

What does Google look at?

Google's help pages don't define a “clock”; the rule is written relative to the moment you apply: “At least 12 testers must be opted in to your closed test when you apply for production access, and they must have been opted in continuously for the preceding 14 days.”

So the count is per person. When you apply, at least 12 people must each have been opted in continuously for the last 14 days.

Uploading a new release

Google's pages on testing requirements, test setup, release preparation and review say nothing about how a new release affects the 14 days. Google ties eligibility to the testing program: a tester must “actively opt into the corresponding test program”. Nothing ties the opt-in to a release or says a new release removes it.

Google recommends updating: “Updating your app in closed testing before releasing to production helps minimize low ratings and negative reviews.” Part 3 of the application form also asks what you changed in the app based on what you learned in the closed test.

What breaks the 14 days?

The only case Google states explicitly is leaving the test:

“Testers who opt in, test for fewer than 14 days, and then opt out do not count toward the requirement. If a tester opts out and opts back in later, the 14 days must be consecutive to count toward the minimum requirement of 12 continuous opted-in testers.”

Play Console Help, testing requirements page, frequently asked questions

What follows from the rule: for someone who leaves and comes back, the 14 days start from their return. If someone new replaces a tester who left, they also need their full 14 days. Before applying, make sure at least 12 people who have completed their 14 days are still there.

Watch out when updating

  • A new release goes through review. According to Google, this takes from a few hours to 7 days, longer in exceptional cases. Testers only get the new release after that.
  • You can't start a new release while one is outstanding. “You cannot create a new release when you have outstanding releases.”
  • Don't pause the track. Google describes the Pause track button in the “End a test” step, which is how you “remove users from your app's test and end a testing track”. Don't press it while the test is running.
  • Don't change the tester setup. Attaching a new email list or Google Group to the track is a change you send from the Publishing overview. Adding members to an existing group, by contrast, requires no action in Play Console; Google's publishing page counts group membership changes among the changes that managed publishing doesn't hold back.
Not in the official sourcesHow a new release, or switching from an email list to a Google Group, affects the 14 days. (In our test, when the track switched from an email list to a group, 6 earlier opt-ins who were also in the group kept counting; November 2026.) Whether uninstalling the app from the phone counts the same as leaving the test: Google's text only talks about opting in and opting out.

Sources

All are Play Console Help pages. Quotes are taken verbatim from the English help pages.

Leave the test to us

12 testers plus 3 backups, 14 days in a row. Follow every day on a live table.

See packs