Release checklist

Goal: Adapty renders paywall, users can purchase products, access unlocks, and restoration flow works.

• Your app displays the paywall from the same placement you will ship.
  • Paywall displays on the screen. If loading takes too much time (e.g., if you or your users deal with unstable internet), consider adjusting your fetch policy.
  • Paywall matches expected variant (audience/locale if applicable). You can change the audience priority if needed.
• Products and prices appear on the paywall. Note that Apple’s API can occasionally provide inaccurate prices during testing (especially with different region configurations), so prioritize testing the purchase flow functionality over price accuracy since Adapty doesn’t affect Store prices.
• Sandbox purchase completes successfully. Successful purchase callback is received.
• Access unlocks and persists. Confirm that paid access is granted based on the current Adapty profile.
  • After purchase, the Adapty profile has an active access level.
  • Paid features unlock when the profile contains that access level (not just on the purchase callback).
• Restoring purchases works. When you reinstall the app or install it on a new device, the automated purchase restoration works according to the Sharing paid access setting. If you don’t have any backend authentication, purchases are restored automatically regardless of the setting. On other cases, ensure that users can restore their purchases after reinstalling the app.
• Store review requirements:
  • The Restore purchases button is on the paywall. You can add it in the paywall builder, and it will process purchase restorations automatically when tapped.
  • Terms of Use + Privacy Policy are accessible from the paywall screen, and clicking these links opens them in a browser.

Goal: You render UI; Adapty handles purchases, profile updates, and restorations.

• Products IDs are not hardcoded in your app code. You only hardcode placement IDs.
• Your app fetches products from the same placement you will ship.
  • Product list loads successfully. If loading takes too much time (e.g., if you or your users deal with unstable internet), consider adjusting your fetch policy.
  • The fetched products match the expected variant (audience/locale if applicable). You can change the audience priority if needed.
• Products and prices appear on the paywall. Note that Apple’s API can occasionally provide inaccurate prices during testing (especially with different region configurations), so prioritize testing the purchase flow functionality over price accuracy since Adapty doesn’t affect Store prices.
• Sandbox purchase with makePurchase completes successfully:
  • Successful purchase result is handled.
  • Pending/failed/cancelled outcomes are handled gracefully.
• If you use a remote config, its values are pulled correctly to your paywall.
• When a paywall is presented, the logShowPaywall method is called.
• Sandbox purchase completes successfully. Successful purchase callback is received.
• Access unlocks and persists. Confirm that paid access is granted based on the current Adapty profile.
  • After purchase, the Adapty profile has an active access level.
  • Paid features unlock when the profile contains that access level (not just on the purchase callback).
• Restoring purchases works. When you reinstall the app or install it on a new device, the automated purchase restoration works according to the Sharing paid access setting. If you don’t have any backend authentication, purchases are restored automatically regardless of the setting. On other cases, ensure that users can restore their purchases after reinstalling the app.
• Store review requirements:
  • The Restore purchases button is accessible and handles restorations.
  • Terms of Use + Privacy Policy are accessible from the paywall screen, and clicking these links opens them in a browser.

Goal: You handle purchases, profile updates, and restorations yourself; Adapty receives transaction reporting.

• Your app completes purchases using your own purchase flow (StoreKit / BillingClient / backend):
  • Sandbox purchase succeeds in the store UI.
  • Pending/failed/cancelled outcomes are handled gracefully in your app.
• Transactions are reported to Adapty.
  • The observer mode is enabled in your app code.
  • The purchase appears in the Adapty Event Feed.
  • Renewals, cancellations, and refunds are reflected over time (as applicable).
• Paywall views are tracked. The logShowPaywall method is called when a paywall is shown.
• Restore purchases works for your implementation. Reinstalling the app or switching devices restores access correctly.
• Store review requirements:
  • The Restore purchases action is accessible and triggers your restore flow.
  • Terms of Use + Privacy Policy are accessible from the paywall or purchase screen and open in a browser.