Does Updating Your App Reset the 14-Day Closed Test?

Why updates don’t restart the count

The requirement in Google’s help is about people: a minimum of 12 testers who have been opted in continuously for at least 14 days. Opt-in belongs to the tester’s Google account and the testing track, not to a version code. When you roll out version 1.0.3 to the same closed track, your testers stay opted in and their days keep accumulating.

What does reset a tester’s 14 days

• The tester opts out, then back in. Google says the 14 days must be consecutive, so their count starts again.
• You remove the tester from the email list or Google Group the track uses.
• You switch tracks. Testers opted in to one closed track are not automatically opted in to a different track you create later.
• You swap the tester list on the track (for example replacing one email list with another) and people fall off it.

Updating safely mid-test

1. Upload the new app bundle to the same closed testing track.
2. Increase the version code. Play rejects a version code you have already used (see version code already used).
3. Write short release notes saying what changed and what testers should check (see release notes for test builds).
4. Wait for the release to be reviewed and published. Testers get the update through the Play Store like any other update.

Tip: keep a simple log of each update and the feedback that prompted it. “Tester X reported the widget not refreshing on day 4; fixed in 1.0.3 on day 6” is exactly the kind of evidence the production access form rewards.

Should you update during the test at all?

Yes, if you have something real to fix. Google’s questionnaire asks what you changed based on testing. A 14-day test with zero updates suggests either a perfect app or a test that did not surface anything. Avoid shipping a broken build in the last couple of days, though, because a crash spike right before you apply is not the story you want to tell.

Frequently asked questions