Can you update your app during the 14-day closed test?

Short answer: yes. You can publish a new version to the same closed-testing track during the 14-day period. Existing eligible testers receive the highest compatible version code available to them. Keep the track running and do not remove testers while releasing the update.

Use a higher version code

Every Android App Bundle uploaded to Play Console needs a unique, increasing version code. Build the fix, increment the version code, create a new release in the same closed track, add clear release notes and roll it out.

What testers need to do

Testers normally receive the new test version through Google Play within minutes after it becomes available, although reviews and propagation can take longer. Ask them to update from the Play Store and retest the feature that changed.

What not to change mid-test

• Do not pause the closed track.
• Do not remove the active tester list or Group.
• Do not move testers to internal testing.
• Do not change the package name; an uploaded package name is fixed.

Why an update can strengthen the production application

Google asks what you changed based on tester feedback. A real fix gives you a precise answer: the issue reported, the version that fixed it and how testers verified the result. Do not publish a meaningless update just to create activity; ship a change the test genuinely justified.

Official sources

Google Play: testing tracks and version-code eligibility · Google Play: production-readiness questions