TestFlight, Play testing tracks, review, and rollout
Use store testing to verify the same release candidate you intend to submit or promote.
Apple
Upload the exact release build, wait for processing, configure TestFlight information and tester access, verify purchases with sandbox/TestFlight accounts when used, then select the tested build for App Review. External testing may require Apple beta review.
Use internal or closed testing before production when appropriate. Verify the exact version code, tester groups, app-access instructions, Data Safety/content declarations, purchase products, and device behavior before promoting the release.
What to test
Authentication, account creation/deletion, navigation, safe areas, permissions, deep links, uploads/downloads, notifications if used, purchases/restores, subscription state, offline/network failure, support/privacy links, and any reviewer credentials.
Common problems
Testing a different binary than the one submitted, expired tester access, missing reviewer credentials, products unavailable to test accounts, incomplete declarations, wrong track, or promoting an unverified version code.