How to Push App Updates During the 14-Day Closed Test

TL;DR

Pushing an update during your 14-day test is safe and highly recommended. Simply increment your app's version code, create a new release inside your existing Closed Testing track, and roll it out. It will not reset your 14-day streak.

Updating Without Fear

Many developers are terrified to touch their Play Console once the 14-day closed test begins. They fear that uploading a new Android App Bundle (AAB) will break their streak and reset the clock back to Day 1.

This is a myth. Updating your app during the closed test is entirely safe, and actively encouraged by Google.

How to Safely Push the Update

Update Version Code: In your app's build.gradle (or equivalent configuration file), increment the versionCode and versionName.
Generate Bundle: Build a new signed AAB.
Create Release: Go to the Play Console > Testing > Closed testing. Click Manage track.
Upload: Click Create new release in the top right. Upload your new AAB.
Release Notes: Add brief notes explaining the bug fixes to your testers. Click Next and Save.

Tired of Console Configurations?

Managing email lists, tracks, and engagement metrics takes time away from coding. Let our professional team handle the testing process end-to-end.

Get 12 Testers for $39

The Review Process for Updates

When you submit the update, the new release goes into "In Review" status. Your 14-day clock does not stop during this review. Your testers simply continue using the older version of the app currently installed on their phones.

Once Google approves the update (usually within a few hours to 2 days), the Play Store will prompt your testers to download the new version.

Why Updates Improve Approval Odds

Google's goal with the 14-day rule is to force developers to do real Quality Assurance. If you run a 14-day test and push an update on Day 7 fixing a bug, you leave a highly visible paper trail of active development.

When you finally fill out the production application and state, "Testers found a bug on Day 5, and we deployed a fix in version 1.0.2," the human reviewer can see that exact release history in your track. This makes your QA effort undeniable.

Authored by our Lead QA Analyst

With over 10,000+ apps successfully pushed to production, our team tracks every Google Play policy update to bring you accurate, tested advice. Need help launching your app? Start a testing campaign today.