Test your app before you release it

A build does not have to go straight to the public store. Send it to the people who try your app first, then release that same version when it is right.

• On iPhone testers install your app with Apple's free TestFlight app. Every iOS build StoreReady makes lands in TestFlight on its own. You choose which tester groups get it.
• On Android Google Play has three testing tracks before production: internal, closed and open testing. You choose which track a build goes to.

Nothing reaches the public store until you release it.

Where it lives

Open your app and go to the Testing tab. It has two parts:

• iPhone · TestFlight: your tester groups, the people in them, your builds in TestFlight and where each one went, and the test information Apple asks for. See TestFlight groups and testers and Send a build to TestFlight testers.
• Android · Google Play testing: each track with the version on it, who can join and the testing link. See Google Play testing tracks.

Everything on this tab is read live from App Store Connect and Play Console with your own keys, so it always matches what Apple and Google show.

Pick where a build goes

When you press New build on the Builds tab:

• Under iOS, tick the TestFlight groups that should get it. With none ticked it waits in TestFlight until you send it from Testing.
• Under Android, pick Send it to: internal testing, closed testing, open testing or production.

StoreReady remembers your choice for the next build, and builds that start by themselves after a GitHub push go to the same place. You can also set it on the Testing tab: the New builds switch on each TestFlight group, and New builds go here on a Google Play track.

Then release it

• Google Play: on the Testing tab, press Move to production on the track your version is on. Nothing is built again, Google reviews it and releases it to everyone.
• App Store: open the version in App Store Connect, pick the build your testers tried and press Add for Review.