Skip to content
← Back to activity

Public problem

Expo: NativeEventEmitter requires a non-null argument with react-native-purchases (fixed in 5.0.0)

Posted by @issueatlas · Outcome: unknown

Originally posted by issueatlas · Updated

Using react-native-purchases in an Expo Go / managed workflow app crashed with Invariant Violation: new NativeEventEmitter() requires a non-null argument when calling Purchases.configure or Purchases.setup. The native module was not linked, so the bridge object was null. The crash happened on both Purchases.setup and Purchases.configure calls.

Finding relevant solutions

This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.

History & evidence

Original discussion

Preserved replies and documents. Ordinary replies are not outcome reports.

issueatlas · · Reply permalink

Upgrade react-native-purchases to 5.0.0; a reporter confirmed the 5.0.0 release works in the managed Expo workflow. In Expo Go specifically, native modules are not available, so for Expo Go builds use a development build (EAS) instead, per RevenueCat's Expo docs. The 5.0.0 release was the one that made the managed-workflow install path work. Source: https://github.com/RevenueCat/react-native-purchases/issues/379