What to test before app store submission

24 published product types ship through an app store, and all 24 carry the store rejection risk in their risk map: 4 at primary evidence grade and 20 at secondary evidence grade. This guide lists the checks their test plans repeat before a build goes to review, so a team can run them on any store build.

What the 24 store plans share

• Release smoke tests, compliance checks and end-to-end functional tests are mandatory on all 24.
• The release smoke test carries the store rejection risk id on all 24. Compliance checks carry it on 11. Device and browser compatibility is mandatory on 12, and carries it on all 12.
• 16 of the 24 release smoke done conditions run "on the release build". 3 run "on every store build" and 3 "on every build".

Procedure before you press submit

1. Build the exact binary you will submit. Run the release smoke test from section 4 of your playbook on that binary before any other test. On the mobile banking app that means a fresh install, a login to a test customer, a check that only that customer's accounts show, and a transfer between two of them.
2. If the app takes money, finish the smoke path with a test card or sandbox payment. 5 store release smoke tests name one, including the ecommerce store, grocery delivery app and mobile game.
3. Compare what the build collects with the privacy labels or data declarations on the store listing. 5 store compliance done conditions require that match, on the mental health app, grocery delivery app, travel booking app, ride-hailing app and kids app.
4. If people meet or post content in the app, open report and block on the profile and chat screens. 7 done conditions across the online marketplace, social network, dating app and messaging app require both controls, each carrying the store rejection risk id.
5. If the app sells points, credits or other digital value, check paid sales against the store billing rules. The loyalty program app checks that paid point sales follow them, against the store rejection risk.
6. If children can reach the app, try each purchase, chat and outbound link and confirm a parental gate or parent consent step stops it. The kids app mentions a parent or parental control in 5 of its mandatory done conditions; on the mobile game a tester acting as a child is stopped at a parental gate before buying currency or chatting with strangers, and the language learning app routes under-age users to a parent at its age gate.
7. If the app controls hardware, open it with no device paired. The wearable companion app and smart home or IoT app both open to a demo mode without hardware, and the EV charging app gives store review a demo station and test account, so a reviewer can use the app.
8. Install and run the core path on the oldest OS version named on your store listing. 6 of the 12 store compatibility done conditions name the oldest supported version.
9. For a desktop build, run notarization and store certification on every build. The desktop application is the only store type whose compliance done condition repeats per build.
10. Record pass or fail per done condition and the build number, and attach the checklist for your type to the submission ticket.

What this guide does not cover

Store rules change, and each store's guideline page takes precedence over this summary. The evidence behind each risk, with its verification date, is listed on the store rejection risk page and in section 11 of each playbook.