An iOS and Android release checklist for cancellation, expiry, billing failures, restore flows, and entitlement changes.
A subscriber opens a mobile app, cancels an auto-renewing plan in the store, returns to the app and still sees the Premium badge. The first reaction might be: “Cancellation is broken.”
But that conclusion may be wrong.
For a typical auto-renewing subscription, stopping future renewal is not the same event as ending the paid entitlement. A customer who has paid through a future date may correctly retain access until that period expires. Google Play's subscription lifecycle guidance explicitly distinguishes a cancelled but still-entitled subscription from an expired one. Apple likewise provides subscription status and renewal-state information rather than a single universal yes/no switch. Google Play subscription lifecycle [[1]] · Apple auto-renewable subscriptions [[2]].
This makes subscription testing a state-transition problem. The goal is not to force every “cancelled” user into the free tier immediately. The goal is to confirm the app grants and removes the right features at the right time, communicates the state clearly, and updates consistently across devices and sessions.
Define the entitlement contract before testing
Write down the expected access for each product and account state. Does a monthly plan stay active through its paid-through timestamp after auto-renew is disabled? Which premium features are included? When does a plan change take effect? Can a person have a separate subscription purchased on another platform? Which account identity should own the entitlement? What should happen when a refund or revocation is issued?
The product owner should approve those answers, including the timing of grace periods and how the app describes them. Testers cannot infer a product's commercial rules from a paywall screenshot.
Ten release scenarios that expose lifecycle defects
1. New purchase: Start from a verified free account. Purchase in a configured store test environment; check that the correct plan and features become available once the transaction is confirmed. Record the store product ID, test account and app build.
2. Cancel before renewal: Turn off auto-renew through the supported store-management flow. Confirm that the app updates its renewal messaging without incorrectly removing an entitlement that is still valid through the paid-through date.
3. Expire at the actual boundary: Advance the sandbox or test clock using supported controls. Once entitlement truly ends, verify premium-only actions are blocked or downgraded according to the approved design, and the account clearly displays the next action.
4. Payment failure: Simulate an unsuccessful renewal using a supported test scenario. Confirm the message and feature access correspond to the actual billing state, not simply the last successful payment UI.
5. Grace period versus account hold: If enabled, test continued access during an eligible grace period, then the transition after that period ends. Google Play differentiates grace period from account hold; Apple also offers a configurable Billing Grace Period. Do not assume the same timings or behavior across stores. Google lifecycle [[1]] · Apple Grace Period [[3]].
6. Recovery after failed renewal: Use a permitted sandbox recovery path. Check that an account that legitimately regains entitlement can use the feature again and that confusing stale “payment failed” prompts disappear.
7. Restore purchases: Reinstall or sign in on a second device using the intended store/account combination. Check the restore entry point, correct feature unlocks, and useful error handling when nothing is restorable.
8. Upgrade or downgrade: Move between plan tiers and durations. Verify effective dates, displayed benefits and feature limits against the store's chosen replacement behavior and the app's approved pricing rules. Do not assume all plan changes apply immediately.
9. Sign-out, account switching and two devices: Purchase with one test identity, sign out, then sign in with another. Ensure the app does not display a previous account's premium state as the new user's entitlement. Repeat with two devices after a state change.
10. Cold launch and delayed state refresh: Cancel or expire while the app is backgrounded or closed. On return, refresh or relaunch, confirm the displayed tier and actions are derived from current valid entitlement data, not only cached purchase text.
Use store-controlled test environments
On iOS, Apple documents StoreKit Testing in Xcode, Sandbox and TestFlight for different stages. Supported cases include renewals, cancellation, expiry, upgrades, restoration and failed-payment scenarios. TestFlight in-app purchases use sandbox transactions rather than real charges. Use the tool that matches the flow being tested and record its configuration. Apple's test-environment guide [[4]].
On Android, Google recommends license testers and Play Billing Lab for billing integration tests. Test accounts can simulate failed payments and accelerated subscription lifecycle events. Be careful: a non-license tester on a testing track can make real purchases, so obtain the correct test-account setup before executing any payment case. Google Play billing test guide [[5]].
A platform sandbox does not fully represent every production timing or external system. Record whether a scenario was directly observed, simulated, blocked by the test environment or not executed.
Report observable evidence, not imagined revenue loss
An actionable defect could say: “After the subscription's confirmed expiry in the Google Play test environment, the app still permits the premium export action after force-close and relaunch.” Include the test account type, plan/product ID, observed status, relevant timestamps, build, device, reproduction steps, screen evidence and expected behavior. This is an illustrative example, not a Testers HUB client finding.
Another observation may be entirely correct: “Auto-renew is off, but Premium access remains until the paid-through date.” That should be recorded as a pass if it matches the documented requirements. The distinction prevents false positives and helps the engineering team spend time on real inconsistencies.
Make lifecycle coverage a planned QA activity
A single successful purchase does not validate a subscription product. Before a launch or billing change, agree a compact matrix of states, transitions, devices and evidence. Give priority to the flows that could mislead customers or produce inconsistent access. Bring developers and billing owners into triage when the app and store records disagree.
Testers HUB provides independent manual and exploratory iOS/Android testing on real devices, with reproducible defect reporting and regression according to the agreed scope. If your team needs a focused subscription-flow QA pass, see "Testers HUB Mobile App Testing Services" (https://testers-hub.com/mobile-app-testing-service/) and share the builds, plans, supported stores and test-account access.
A cancellation tap, a payment event and a premium badge are three different signals. Test the entitlement lifecycle between them.



