Mobile release gates
In-app purchase untested in the store sandbox
The purchase code was only run against a mock, so restore, failed payment and receipt validation break on real devices.
Termsstore sandbox (Apple's and Google's test environments where purchases run without real money) · client bundle (the JavaScript your app sends to the browser or ships inside the mobile app; anyone can read it) · verdict (a one-word release result (pass, pass with findings, fail) with the findings and the checklist version behind it)
criticalseverity if found in a releasesources verified 2026-09-21
Why AI-assisted code produces it
Apple's sandbox and Google Play's license testers exist because purchase behaviour cannot be observed locally; generated purchase code is written against the SDK, not the store.
Apple's sandbox environment lets a team test in-app purchases with real product information without charges, including auto-renewable subscription behaviour at accelerated renewal rates, failed renewals and billing grace periods, interrupted purchases, refund requests and Ask to Buy.
Source: Apple Developer Documentation, 2026-09 · verified 2026-09-21
Google Play test purchases use the same purchase flow as real purchases without charging money; test subscriptions renew on shortened periods (a one-month subscription renews every 5 minutes) and at most six times; license testers can sideload builds, and test tracks let a QA team qualify unreleased versions.
How we detect it
Complete purchase, restore and failed-payment paths with a sandbox account on the oldest and newest supported OS.
Most associated with
Tools: Cursor, GitHub Copilot, Claude Code, Windsurf, Lovable, Bolt
Stacks: React Native, Expo
Checklist items that catch it
Purchase flows verified in sandbox on target OS versions
manual Complete each purchase and restore flow with an Apple sandbox account and a Play license tester on the oldest and newest supported OS versions.
Every purchase, restore and failed-payment path ends in the entitlement state the written rules specify on both OS versions.
Dots: Starter, Growth, Scale. The item runs on every release for the plans marked.
More in mobile release gates
- high
- high
- high
- high
Check your codebase for this pattern
The coverage audit lists which catalogue patterns apply to your critical flows. 5 business days, $1,200, credited to a first month.