React Native Data, Purchases, and Cache - AppActor

React Native mirrors the wrapper purchase surface closely and keeps a few Android-only or iOS-only returns explicit.

Core reads

getOfferings()
getCustomerInfo()
activeEntitlementKeysOffline()
getCachedOfferings()
getCachedRemoteConfigs()
getCachedCustomerInfo()
canMakePurchases()
getStorefront()
getStoreCapabilities()

const offerings = await AppActor.instance.getOfferings();
const info = await AppActor.instance.getCustomerInfo();
const hasPremium = info.hasActiveEntitlement('premium');

Fallback offerings

await AppActor.instance.setFallbackOfferings(fallbackBytes);

setFallbackOfferings(...) accepts Uint8Array or ArrayBuffer.

Purchase and recovery

Use:

purchasePackage(pkg, options)
restorePurchases({ syncWithAppStore })
syncPurchases()
quietSyncPurchases()
drainReceiptQueueAndRefreshCustomer()

purchasePackage(...) can carry offeringId, oldPurchaseToken, replacementMode, quantity, and placement.

Platform return differences

canMakePurchases() always matters most on Android
getStorefront() is Android-oriented and returns null on unsupported platforms
getStoreCapabilities() is Android-oriented and returns an empty set on unsupported platforms

That is intentional wrapper behavior, not a documentation omission.