RevenueCat and Superwall in Expo

Choose one owner for purchase completion before writing code. Preserve the application's account and restore policy; a paywall integration is not permission to change who owns purchases.

Inspect and choose

Read the lockfile, Expo configuration, actual application root, auth coordinator, existing billing calls, product catalogue, and entitlement checks. Resolve public SDK keys through the project's environment handling; never embed secret API keys or webhook credentials in client code.

Use references/architecture-decision-tree.md to choose:

• RevenueCat owns purchase execution and entitlements: use Superwall's CustomPurchaseControllerProvider, exact RevenueCat purchase APIs, and a single full-entitlement sync into Superwall. The bundled integration examples cover this path.
• Superwall or an existing billing implementation owns completion: RevenueCat can observe through purchasesAreCompletedBy. This is a current architecture, not merely a deprecated migration workaround. Set the actual StoreKit version and prove receipt/entitlement propagation. Never let both SDKs finish a transaction.

Expo Go is not the native store-test environment. Install only required packages with the project's package manager and npx expo install; add expo-build-properties only when an actual override is needed. Do not lower platform minima to an old example's Android 23/iOS 15.1 values.

Implement the contracts