“I Purchased But My
Entitlement Isn't Active”

This is the most common cause by a wide margin. RevenueCat's architecture separates what a user bought (a product) from what they can access (an entitlement). The purchase can succeed at the store level, but if the product isn't linked to an entitlement in the RevenueCat dashboard, the SDK will never report the user as entitled.

Verify that every store product ID is listed under the correct entitlement. This includes both your App Store and Google Play products — they need separate entries. A missing product here produces no error and no warning. The purchase completes, the user is charged, and CustomerInfo.entitlements simply won't include the entitlement.

The product identifier in RevenueCat must exactly match what you configured in App Store Connect or Google Play Console. This is case-sensitive. Common mistakes:

• Trailing whitespace when pasting the ID into the dashboard
• Using the subscription group name instead of the product ID (App Store)
• Confusing the base plan ID with the product ID (Google Play — these are separate since Billing Library 5.0)
• Creating the product in RevenueCat before creating it in the store (the store product must exist first)

RevenueCat doesn't push entitlement updates from the server to your device in real time. The SDK caches CustomerInfo and refreshes it automatically on app foregrounding, purchases, and restores — but if your code keeps its own separate copy of the entitlement state, it can go stale.

The purchase(package:) method returns fresh CustomerInfo in its completion handler — use that directly. Don't call getCustomerInfo() separately after a purchase — if it resolves concurrently before the purchase flow completes, you'll get stale data.

Also set up the PurchasesDelegate (iOS) or UpdatedCustomerInfoListener (Android) to catch entitlement changes that happen outside your app — subscription renewals, family sharing, promo codes, and server-side grants.

This is the subtle one. purchasesAreCompletedBy is set during Purchases.configure() and determines whether RevenueCat or your app finishes (acknowledges/consumes) transactions with the store.

The default is .revenueCat — RevenueCat handles everything. If you've set it to .myApp (for observer mode, migration from another billing system, or custom server-side validation), then your code is responsible for calling Transaction.finish() (StoreKit 2) or acknowledgePurchase() (Google Play). If you don't, the transaction stays pending. On iOS, StoreKit will keep resurfacing the purchase dialog. On Google Play, the purchase auto-refunds after 3 days.

If you're not sure why this is set to .myApp, it probably shouldn't be. This isn't a toggle — it's an architectural decision that affects Offline Entitlements, observer mode behavior, and migration paths. Change it back to .revenueCat unless you have a specific reason not to.

RevenueCat tracks entitlements per app user ID. If the user purchased on an anonymous ID (the auto-generated $RCAnonymousID:<uuid>) and your app later calls logIn() with a custom user ID, the entitlement lives on the anonymous profile — not the identified one.

The fix: call logIn() before the purchase, not after. If the user already purchased on an anonymous ID, configure your project's restore behavior setting (Dashboard → Project → Restore Behavior) to control how anonymous purchases are transferred when a user identifies themselves, or have the user call restorePurchases() after logging in to trigger profile merging.