mcpField
R
rc-subscription-states

rc-subscription-states

github.com/revenuecatDevelopment76643 installsUpdated 1d ago
Repository

About rc-subscription-states

An Android development skill for checking RevenueCat subscription access and reflecting subscription states in the UI. It explains how to use entitlement fields, cached or fresh CustomerInfo, and update listeners.

Key features

  1. 01Gate access with entitlement activity
  2. 02Read renewal, expiry, and billing signals
  3. 03Use cached or freshly fetched CustomerInfo
  4. 04Update UI through customer info listeners
  5. 05Handle identified and anonymous users

Use cases

  1. 01Showing premium content based on subscription access
  2. 02Displaying billing issue or expiry notices
  3. 03Refreshing access after a server-side grant
  4. 04Keeping access UI updated after purchases or restores

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/revenuecat/ai-toolkit --skill rc-subscription-states

After installing, type/rc-subscription-statesin Claude Code to confirm it loaded.

Details

From the project README

Subscription States

Decide whether a user has access, and drive state aware UI, using CustomerInfo and EntitlementInfo on Android.

Phase 1: Discover

Confirm what you are actually checking before you write code.

  • Which entitlement identifier gates the feature? (for example pro_access)
  • Do you need a plain access boolean, or do you also need to explain why the user has or lacks access (billing issue, canceled but still paid, paused)?
  • Do you need the cached value (fast, possibly stale) or a freshly fetched value (server authoritative)?
  • Are you refreshing UI once on launch, or reacting to live changes (purchase, restore, background refresh)?

If you only need access on/off, you only need isActive. Everything else is optional context.

Phase 2: Plan

Google's seven states versus RevenueCat's boolean

Rolling your own tracker with the Google Play Developer API means mapping seven subscription states and deciding which grant access.

Google stateGrants access?
ACTIVEyes
IN_GRACE_PERIODyes
CANCELED (before expirationDate)yes
ON_HOLDno
PAUSEDno
EXPIREDno
PENDINGno

RevenueCat computes this on the backend from the Google SubscriptionPurchaseV2 resource and exposes the result as one field: EntitlementInfo.isActive. You read a boolean instead of implementing the state machine.

What to read, and when
NeedField
Does the user have access right now?entitlement.isActive
Will the subscription renew at period end?entitlement.willRenew
When does paid access end?entitlement.expirationDate
Is this a trial, intro, prepaid, or normal period?entitlement.periodType
Is there a payment problem?entitlement.billingIssueDetectedAt
Has the user canceled but still has time left?entitlement.unsubscribeDetectedAt
Which store issued the entitlement?entitlement.store
Decision rules
  • Gate features on isActive == true. Nothing else.
  • Use billingIssueDetectedAt != null to show a fix payment prompt.
  • Use unsubscribeDetectedAt != null with expirationDate to show a renewal reminder while access is still valid.
  • Use !willRenew (when no billing issue and no explicit cancel timestamp) to show a non renewing notice.

Phase 3: Execute

Read CustomerInfo and check access
val customerInfo = Purchases.sharedInstance.awaitCustomerInfo()
val hasAccess = customerInfo.entitlements["pro_access"]?.isActive == true

awaitCustomerInfo() returns the disk cache immediately, then refreshes from the network in the background. Entitlement checks stay fast, even offline.

Force a fresh fetch when you must

Use this after a server side grant (for example, a support agent issued a promo).

val fresh = Purchases.sharedInstance.awaitCustomerInfo(
    fetchPolicy = CacheFetchPolicy.FETCH_CURRENT
)
Drive state aware UI

isActive gates access; the other fields explain context.

fun updateUI(entitlement: EntitlementInfo?) {
    if (entitlement == null || !entitlement.isActive) {
        showSubscribeScreen(); return
    }
    showPremiumContent()
    when {
        entitlement.billingIssueDetectedAt != null -> showBillingIssueWarning()
        entitlement.unsubscribeDetectedAt != null ->
            entitlement.expirationDate?.let { showExpiryNotice(it) }
        !entitlement.willRenew -> showNonRenewingNotice()
    }
}
Messaging guide by signal
Signal on an active entitlementMessage to show
billingIssueDetectedAt != nullPayment problem, update method
unsubscribeDetectedAt != nullAccess ends on expirationDate
willRenew == false (no other signal)Will not renew this period
periodType == TRIAL or INTROTrial or intro pricing in effect
Identify the user for multi device
val result = Purchases.sharedInstance.awaitLogIn("your_user_id")
val customerInfo = result.customerInfo
val createdNewUser = result.created

awaitLogIn() merges anonymous purchases with the identified user. logOut() starts a fresh anonymous session.

Phase 4: Verify

Listen for CustomerInfo updates

Register a listener so UI reacts to purchases, restores, and background refreshes without manual polling.

Purchases.sharedInstance.updatedCustomerInfoListener =
    UpdatedCustomerInfoListener { info ->
        val active = info.entitlements["pro_access"]?.isActive == true
        updateAccessGate(active)
    }

The listener does not fire when the SDK starts with a cache hit and nothing changed. Always call awaitCustomerInfo() on launch in addition to setting the listener.

Test matrix

Walk through each case and confirm the UI responds correctly.

CaseExpected isActiveExpected UI
Fresh purchasetruePremium content
Grace period (billing issue, still granted)truePremium + billing warning
Canceled, still before expirationDatetruePremium + expiry notice
On holdfalseSubscribe screen
PausedfalseSubscribe screen
ExpiredfalseSubscribe screen
Pending (no payment yet)falseSubscribe screen
Sanity checks
  • Access gate flips correctly when the listener fires after a purchase.
  • FETCH_CURRENT updates CustomerInfo after a backend grant (promo, refund, support action).
  • After logOut(), CustomerInfo reflects an anonymous user and isActive resets accordingly.
  • Offline launch still returns cached CustomerInfo and gates access without a network call.

References

Comments

Markdown supported