Expo 54 uses react compiler ~ Does it work?

[disrae]

Hi,

Looking to upgrade to expo 54, has anyone done it? Did it break IAP?

Edit: It works!

I do get an onPurchase error that fires, but the transaction actually works since onPurchaseSuccess fires and the backend validates it I think... 🤔

ERROR  Purchase Failed An error occurred while processing your purchase 

Code: index.tsx
  184 |                     console.log('User cancelled purchase');
  185 |                 } else {
> 186 |                     console.error('Purchase Failed', 'An error occurred while processing your purchase');
      |                                  ^
  187 |                 }
  188 |             },
  189 |         });

Edit: Expo-iap does not like hot reload though. 👇

 ERROR  [Expo-IAP] Error fetching products: [Error: Connection not initialized. Call initConnection() first.] 

Code: construct.js
  2 | var setPrototypeOf = require("./setPrototypeOf.js");
  3 | function _construct(t, e, r) {
> 4 |   if (isNativeReflectConstruct()) return Reflect.construct.apply(null, arguments);
    |                                                                 ^
  5 |   var o = [null];
  6 |   o.push.apply(o, e);
  7 |   var p = new (t.bind.apply(t, o))();
Call Stack

[disrae]

Woof, just a few days ago I upgraded to Xcode 16.4, now Xcode 26 awaits.

[hyochan]

Expo 54 (with React Compiler) works fine with expo-iap. The compiler doesn’t affect native billing.

About your “error then success” logs
It’s common to see onPurchaseError fire around the same time as a successful purchase (sandbox quirks / retries). Make your flow idempotent and prefer success over error:

• Keep a handledIds set (iOS: transactionId, Android: purchaseToken).
• If onPurchaseSuccess arrives, validate → grant → finishTransaction → mark handled.
• In onPurchaseError, early-return if the transaction is already handled or the code is a benign case (e.g., user cancelled, item already owned).