@entitlehub/react-native

EntitleHub for React Native & Expo — one call to purchase and unlock entitlements. It opens the native store sheet (via expo-iap), validates the receipt with EntitleHub server-side, and hands you the updated entitlements. The RevenueCat developer experience, on EntitleHub.

npx expo install expo-iap
npm install @entitlehub/react-native @entitlehub/sdk

Use

import {
  configureEntitleHub, purchaseProduct, getCustomerInfo, restorePurchases, isEntitled,
} from "@entitlehub/react-native";

// once, after your own login:
await configureEntitleHub({ apiKey: "pk_live_…", appUserId: user.id });

// gate a feature:
if (await isEntitled("pro")) unlockPro();

// buy — opens the native sheet, validates, returns entitlements:
const info = await purchaseProduct("app_pro_monthly", { isSubscription: true });
if (info.isActive("pro")) unlockPro();

// restore:
const restored = await restorePurchases();

| Function | What it does | |---|---| | configureEntitleHub({ apiKey, appUserId, baseUrl? }) | Configure + open the store connection. | | purchaseProduct(productId, { isSubscription? }) | Native purchase → validate with EntitleHub → returns CustomerInfo. | | restorePurchases() | Re-validate the store's purchases, return CustomerInfo. | | getCustomerInfo() / isEntitled(id) | Read entitlements. | | getOfferings() / getProducts(ids) | Catalog metadata / live store prices. | | logIn(appUserId) | Switch the acting user. | | addCustomerInfoUpdateListener(fn) | React to entitlement changes. |

Only your publishable key (pk_) ships in the app. EntitleHub validates the Apple/Google receipt server-side, so a forged one is rejected — no secret key on the device.

How it works

purchaseProduct calls expo-iap to open the StoreKit / Play Billing sheet, then reports the resulting receipt to EntitleHub: the iOS StoreKit 2 JWS, or the Android purchase token. EntitleHub verifies it (Apple root CA / Google Play API), writes the entitlement grant, and returns the customer info. Renewals/refunds stay current via server-to-server notifications.

Full guide: entitlehub.com/docs/purchases.

Choosing / pinning the store library

The on-device purchase runs through expo-iap (OpenIAP). That native layer is the store library's responsibility, not EntitleHub's — and a given version can have platform-specific native bugs. If you hit a native IAP crash (e.g. an EXC_BAD_ACCESS in the store module), it's the store library, not this SDK or your app code, and no JS change can catch a native exception thrown off the JS thread.

Two levers, both without changing this SDK:

• Pin a working version: npm install expo-iap@<version> — this package uses whatever expo-iap is installed (peer dependency).
• Supply your own module: pass any OpenIAP-compatible library to configureEntitleHub:

  await configureEntitleHub({ apiKey, appUserId, iap: require("expo-iap") }); // or react-native-iap

Fully decoupled fallback: skip this package and use @entitlehub/sdk directly — open the purchase with any billing library you've verified on your target OS, then call eh.reportPurchase({ signedTransaction | purchaseToken }). See Purchases → manual.

Requires a development build (Expo Go has no in-app-purchase native module). The entitlement layer is @entitlehub/sdk; this package adds the purchase flow on top.