How to Prepare Your App for Closed Testing

Your testers' time is a limited resource: 12 people, 14 days minimum, one shot at a clean window. The more baseline problems you fix before uploading, the more of that window goes to genuine issues — and the better your production access application looks.

Do a functional walkthrough first

Before any tester sees the app, run every core flow end to end yourself — and ideally on a device you don't develop on. Login and signup, in-app purchases if you have them, all primary navigation, and at least one complete user journey like 'register → use feature → log out'.

• Install and launch from a clean state — no crashes, no white screens
• Login and signup work with fresh accounts
• Purchases or any payments flow complete without errors
• Core feature journeys finish successfully
• The app survives backgrounding and relaunching

Fix issues that waste the window

Prepare your store listing basics

The app's listing elements — privacy policy, data safety, content rating — should be in place before your test window runs, because they're part of the app as reviewers see it. Testers also see the Play Store listing when they install, so a complete listing builds trust.

Sign and package the release

1. 1

   Use an app bundle

   Upload an Android App Bundle (AAB) so Play can generate the optimal APKs per device. Split-package builds without the right architectures can make installs fail for some devices.

1. 1

   Sign with your upload key

   Play requires a release signed with your upload key. A build signed with a debug or test key will be rejected and slow your window down.

1. 1

   Bump the version code

   Each upload needs a version code higher than the previous release, across all tracks on your account — otherwise the upload fails until you correct it.