revenuecat-troubleshoot

Diagnose RevenueCat integration failures using MCP dashboard inspection and SDK debug logs.

58|5|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/RevenueCat/ai-toolkit --skill revenuecat-troubleshoot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revenuecat-troubleshoot
Source: https://github.com/RevenueCat/ai-toolkit/tree/main/revenuecat/skills/revenuecat-troubleshoot
Command: npx skills add https://github.com/RevenueCat/ai-toolkit --skill revenuecat-troubleshoot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Fixes RevenueCat integration issues where your app does not get the expected offerings, products, entitlements, or sandbox purchases reflected correctly, often after configuration or store-side mismatches.

Core Features & Use Cases

  • Universal troubleshooting workflow: Guides you through debug logging, verifying API key correctness, bundle/application ID alignment, dashboard offering/package configuration, store product live status, tester setup, network checks, and appUserID consistency.
  • Dashboard inspection via MCP: Uses the RevenueCat MCP to inspect projects, apps, products, entitlements, offerings, packages, and (optionally) webhook integrations, then proposes actionable fixes.
  • Platform-specific gotchas: Adds targeted checks for iOS, Android, Kotlin Multiplatform, Flutter, and React Native (including common StoreKit/Play Console testing pitfalls).

Quick Start

Tell the skill: "My iOS offerings are empty and purchases succeed but entitlements never activate—diagnose it using the RevenueCat MCP and my debug logs."

Frequently Asked Questions about revenuecat-troubleshoot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why are my RevenueCat offerings empty or showing unexpected products in my mobile app?

Empty or mismatched RevenueCat offerings usually stem from dashboard configuration errors, incorrect API keys, or bundle ID mismatches. You can diagnose this by using the RevenueCat MCP to inspect list-offerings and list-packages, then validating your SDK debug logs against the dashboard configuration.

How do I debug RevenueCat sandbox purchases that succeed but fail to activate entitlements?

Debug RevenueCat sandbox entitlement failures by verifying appUserID consistency, checking platform-specific StoreKit or Play Console tester setups, and inspecting list-entitlements via the RevenueCat MCP. Cross-reference SDK debug logs with dashboard entitlement mappings to identify configuration mismatches.

Does RevenueCat troubleshooting support cross-platform mobile billing setups like Flutter and React Native?

Yes, RevenueCat troubleshooting covers iOS, Android, Kotlin Multiplatform, Flutter, and React Native. It applies platform-specific checks for StoreKit and Play Console testing pitfalls, ensuring offerings, products, and entitlements behave correctly across all supported mobile and cross-platform environments.

What is the best way to diagnose RevenueCat integration breakages after a store-side configuration update?

The best way to diagnose RevenueCat integration breakages is to inspect live store product statuses, verify webhook integrations, and use the RevenueCat MCP to call list-projects, list-apps, and list-products. This validates whether store-side mismatches are causing your paywall or entitlement failures.

How do I validate RevenueCat product and entitlement mappings when paywalls display the wrong items?

Validate RevenueCat product and entitlement mappings by using the RevenueCat MCP to run get-products-from-entitlement and list-products. Compare these dashboard results against your SDK debug logs and platform-specific setup to find the configuration mismatch causing incorrect paywall items.