Release checklist

Use this checklist for your app integration. It is not a certification that One’s public SaaS launch or your provider account is ready.

Configuration

Select the exact Live app and project. Confirm public keys, bundle identifier/browser origin, provider app mapping, and callback URLs.
Verify product identifiers, prices, entitlement mappings, and the chosen paid-access policy.
Preview paywalls and surfaces on each supported platform, language, and size.
Check campaign audiences, schedules, allocations, placement behavior, and explicit fallbacks.
Verify email sender setup, templates, notification actions, and outbound callback signatures.

Test new and returning customers, anonymous-to-authenticated identity, sign-out, session recovery, and account deletion using disposable Test data.
Test purchase, cancellation, pending purchase where supported, restore, expiration, and access after relaunch.
Exercise the app offline and after the connection returns. Check retry and cached-access behavior.
Open Support, send a deliberate test conversation, and verify the reply appears in the app.

Run One’s bounded release-readiness report for the exact Live app and SDK version.
Generate the app fallback from current One truth; include it in Copy Bundle Resources.
Verify the actual build’s package reference and resources.
Complete purchase and restore acceptance on devices. Simulator/build success alone is not StoreKit acceptance.

Ensure an owner can inspect failures, rotate credentials through supported procedures, and recover a failed integration.
Verify report freshness and explain known coverage limits.
Establish monitoring, support ownership, and a rollback procedure before external customers depend on a change.
Keep a record of what was tested, on which build, in which environment, and what remains unresolved.