In-App Subscription with RevenueCat (iOS + Server Gate)

Full-stack RevenueCat subscription system — ASC product setup, RC dashboard wiring, iOS SDK integration (identity-synced appUserID, entitlement stream, paywall), server-side entitlement gate with webhook-driven source of truth, plus a battle-tested debugging playbook for never-published apps (StoreKit Configuration local testing without certificate upload)

Pro

Included in ShipSwift Pro: $89 a year, or $199 for life.

Get Pro

Copies a short instruction with your private download link. Paste it into your agent: it downloads the whole skill (the source code, the setup steps and the mistakes we already made for you) and builds the screen.

Works with

+70

What it does

End-to-end RevenueCat integration for a subscription + lifetime product mix, with the server (not the client) as the real gate for member-only features. Crucially, it encodes the debugging playbook for a first-launch app: how to test purchases before the app has ever been published, which errors are false alarms, and which official docs are stale. Battle-tested on Spotby (2026-07-30, RC SDK v5 / StoreKit 2 / Hono on Cloudflare Workers + Supabase).

What you get

✓102 lines of source code, ready to paste
✓Architecture
✓App Store Connect Setup
✓RevenueCat Dashboard
✓iOS Integration (RC SDK v5, SwiftUI)
✓Server Gate (Hono on Workers + Supabase shown; any stack works)
✓Debugging Playbook (the part that saves you a day)
✓Integration Checklist
✓Known Pitfalls

subscriptionRevenueCatin-app purchasepaywallmonetizationentitlementwebhookStoreKit testingsandboxAPI v2transferapp version

Architecture

appUserID = your business user id (e.g. Supabase uid). Configure once at app init; logIn/logOut on auth changes. Server-side entitlement lookups then share the same axis.
Webhook as trigger, not as state: on any RC event, re-fetch the subscriber from RC and overwrite the row. Immune to event ordering.
Gate on the server: client paywall is guidance only. The member-only route checks the table first (zero external calls on the hot path), falls back to RC API once on miss, and applies a grace rule on RC outages.