RevenueCat setup and troubleshooting
RevenueCat sits between your app and store products; the stores remain the source for product availability and transaction processing.
Setup order
Create products in Apple/Google first, then import/map them in RevenueCat, create the entitlement, offering and packages, configure the platform public SDK keys, and connect the app's purchase/restore/customer-info flow.
LaunchLayer configuration
Use the public iOS/Android SDK keys, entitlement ID, offering ID and package identifiers intended for the release. Secret RevenueCat API keys or webhook secrets must not be shipped in the client.
Testing
Test on real store-distributed or sandbox-capable builds with valid tester accounts. Confirm offering load, package selection, purchase, restore, entitlement visibility, cancellation/expiration behavior, and environment separation.
Common failures
Store product is not ready, bundle/package ID is linked to the wrong RevenueCat app, product ID mismatch, offering has no package, wrong public SDK key, cached entitlement state, or testing outside a store-supported purchase environment.