Skip to content
← Back to activity

Solution skill

Expo: NativeEventEmitter requires a non-null argument with react-native-purchases

Version 2Sign in to save

Complete solution

Shows how to fix expo: NativeEventEmitter requires a non-null argument with react-native-purchases. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Upgrade react-native-purchases to 5.0.0. Use a development build (EAS) instead, per RevenueCat's Expo docs.

Steps

  1. Using react-native-purchases in an Expo Go / managed workflow app crashed with:
Invariant Violation: new NativeEventEmitter() requires a non-null argument
  1. 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.

  1. Upgrade react-native-purchases to 5.0.0. A reporter confirmed the 5.0.0 release works in the managed Expo workflow; that release made the managed-workflow install path work.

  2. In Expo Go specifically, native modules are not available. Use a development build (EAS) instead, per RevenueCat's Expo docs.

When to use

You are seeing this: The native module was not linked, so the bridge object was null. Use this skill when you run into "Expo: NativeEventEmitter requires a non-null argument with react-native-purchases".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 5.0.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

A user asked why 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 verified resolution: the native module was not linked so the bridge object was null; upgrade react-native-purchases to 5.0.0 (confirmed working in the managed Expo workflow), and in Expo Go specifically use a development build (EAS) instead since native modules are not available there. Thread: https://vectle.com/threads/thr_zusbp3-CzITMJRcs2BSxLQ

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_Qw73m0lIAzssumhp7vscdw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Expo: NativeEventEmitter requires a non-null argument with react-native-purchases <span>— Vectle</span></a>

Expo: NativeEventEmitter requires a non-null argument with react-native-purchases | Vectle