compatcompatSign in
RevenueCat

RevenueCat SDK migration

Upgrade react-native-purchases and purchases-js: configure(), CustomerInfo, entitlement checks.

Try compat freeSee a real pull request

1 repository · 3 migrations a month · no card

What compat detects

  • react-native-purchases
  • react-native-purchases-ui
  • @revenuecat/purchases-js
  • @revenuecat/purchases-capacitor

RevenueCat renamed its core types and setup call across majors. compat updates configure, CustomerInfo and the entitlement reads, and flags the native minimum-version changes it cannot edit as manual steps.

What breaks across majors

  1. 01

    Purchases.setup to Purchases.configure({ apiKey }); PurchaserInfo to CustomerInfo; purchaserInfoUpdateListener to customerInfoUpdateListener.

  2. 02

    Entitlement checks moved to customerInfo.entitlements.active; product identifiers under package.product.

  3. 03

    Native SDK majors require matching iOS and Android minimums, a manual step.

  4. 04

    The web SDK uses configure(apiKey, appUserId) and a different offering shape than React Native.

Typecheck catches the renames. Purchase flows need a sandbox-account test on device, listed as a manual step.

What a react-native-purchases 7 to 8 run looks like

Illustrative

compat renames the types and listeners, updates entitlement reads, leaves native build settings for you with a note, and opens the pull request. Illustrative; no public run recorded yet.

  1. 01

    Detect

    compat finds the RevenueCat packages your code imports and the upstream releases that affect them.

  2. 02

    Migrate and verify

    It edits only the affected code in a disposable sandbox, regenerates the lockfile, and runs your existing tests, type checks, lint and build where available.

  3. 03

    Pull request

    It opens a PR with the diff, verification results, warnings and manual steps. A person merges.

Questions

Does compat merge the RevenueCat migration automatically?
No. compat has no merge capability. It pushes a branch and opens a pull request with the diff, the recorded checks and any manual steps. A person on your team reviews and merges.
Which checks run?
Your repository's own: install, typecheck, lint, test and build where the scripts exist. Each is listed in the pull request as passed, failed or not run. A check that did not run is never shown as passed.
Does compat need my production credentials?
No. Migrations run in a disposable sandbox with your code and package manager, not your environment. Checks that need live credentials are reported as not run.
How does compat know a release affects my repository?
It watches the RevenueCat packages your code imports, reads new release notes, and judges relevance against the files that actually use the SDK. Irrelevant releases are dismissed with the reason; relevant ones become a proposal or, if you allow it, a run.

Other providers