How a misconfigured RevenueCat entitlement silently charged users and unlocked nothing

Globie Earth, a tree-adoption app built with Capacitor, uses a single RevenueCat facade to handle in-app purchases across both Android and web platforms via two separate SDKs. The team discovered a critical silent failure where users were successfully charged but received no access, because the entitlement 'guardian_premium' was linked to the wrong product instead of the one the app actually sold. RevenueCat's purchasePackage call resolved without throwing any error, leaving no visible indication that the unlock had failed. The fix required just one dashboard change — attaching the entitlement to the correct product — alongside a code-level check to never assume a successful transaction means an active entitlement. The incident highlighted a key pitfall: RevenueCat does not error on mismatched entitlement-product configurations, making explicit post-purchase validation essential.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in