revenuecat-testing

Generates QA test plans for RevenueCat purchases, subscriptions, and restore flows.

628|64|Updated Apr 22, 2025
One-click install
npx skills add https://github.com/evanca/flutter-ai-rules --skill revenuecat-testing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: revenuecat-testing
Source: https://github.com/evanca/flutter-ai-rules/tree/main/skills/revenuecat-testing
Command: npx skills add https://github.com/evanca/flutter-ai-rules --skill revenuecat-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Verifying that a RevenueCat integration actually works before shipping is hard: sandbox purchases, trials, restores, and account transfers each have subtle platform differences, and most failures are misconfiguration rather than code bugs. This Skill turns "does my IAP work?" into a concrete, checkable QA plan tied to verifiable dashboard signals.

Core Features & Use Cases

  • QA test plan generation: Produces a copy-pasteable checklist of relevant use cases, each row mapping an action to its expected event (INITIAL_PURCHASE, TRANSFER, EXPIRATION, PRODUCT_CHANGE, CANCELLATION) and where to see it.
  • Failure diagnosis: Debugs broken purchases by checking prerequisites first (debug logs before configure(), Invalid Product Identifiers, sandbox accounts) and matching observed behavior against expected signals.
  • Restore/transfer walkthroughs: Covers the account-switching matrix — syncPurchases(), restore-to-new-ID, three-ID conflicts, and transfer-disabled behavior — the most bug-prone area of RevenueCat integrations.
  • Use case: A Flutter developer adding subscriptions asks whether their upgrade/downgrade flow works; the Skill produces a sandbox test plan verifying PRODUCT_CHANGE events with correct old and new product IDs, and points them at RevenueCat's official Purchase Tester sample app.

Quick Start

Ask the agent to create a RevenueCat sandbox testing plan for your iOS and Android subscription app, covering purchase, trial, restore, and account-switching scenarios.

Frequently Asked Questions about revenuecat-testing

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

FAQPage Schema
How do I test RevenueCat purchases in sandbox mode?▼

Enable debug logs before calling configure(), set up sandbox test accounts, and make a test purchase. Verify success by checking for the expected event (such as INITIAL_PURCHASE) in the RevenueCat customer history rather than just confirming the app did not crash.

How do I test RevenueCat restore purchases and account switching?▼

Use multiple sandbox test IDs: purchase on one ID, log out, log in with a new ID, then restore or call syncPurchases(). A TRANSFER event in the customer history confirms the transfer; if transfers are disabled, you should see an error and no TRANSFER event.

Why does my RevenueCat purchase fail in sandbox testing?▼

Most failures are configuration problems visible before any purchase attempt. Check debug logs for "Invalid Product Identifiers" and error-level messages, confirm the sandbox account is set up correctly, and verify offerings load in the debug overlay before debugging purchase code.

Can I test RevenueCat refunds on iOS sandbox?▼

No, iOS sandbox refunds are not possible because the App Store routes refund requests to Apple support. The CANCELLATION event with reason CUSTOMER_SUPPORT can take about 24 hours to appear; Google Play refunds can be tested directly from the dashboard.

Does RevenueCat testing differ between iOS and Android?▼

Yes. Google Play uses PRORATION modes for subscription tier changes and supports dashboard-driven refunds, while iOS follows Apple's upgrade/downgrade timing and cannot sandbox-test refunds. Debug overlay APIs also differ: debugRevenueCatOverlay() on iOS versus DebugRevenueCatBottomSheet on Android.