Skip to main content
Answer

iOS 18 + Expo Managed Workflow: Purchases not showing in dashboard after upgrading to react-native-purchases v9.1.0

  • October 23, 2025
  • 3 replies
  • 63 views

Forum|alt.badge.img

We recently upgraded `react-native-purchases` from `^7.4.0` to `^9.1.0`  

in order to comply with the **latest Android billing policy changes**.

 

Since then, on **iOS 18 (EAS build, Expo Managed Workflow)**:

- In-app purchases succeed

- App Store receipts are received correctly

- BUT transactions **do not show up on the RevenueCat dashboard**

- Entitlements are **not unlocked**

 

⚠️ Android is working fine — purchases are tracked correctly and entitlements are unlocked as expected.

 

No changes were made to our RevenueCat dashboard configuration.

 

---

 

### Environment:

- "expo": "^51.0.0"

- "react-native": "0.74.5"

- "react-native-purchases": "^9.1.0"

- Build: EAS Build  

- Expo Managed Workflow  

- Platform: iOS 18

 

The issue started **immediately after upgrading the SDK** and deploying via EAS build on iOS 18.

 

We’d appreciate guidance on whether additional configuration is required for SDK v9 on iOS 18.

Best answer by joan-cardona

Hi ​@upick-ef5b5b,

I checked your account and it looks like you don’t have the in-app purchase configuration key set up. Upgrading from a 7.x to a 9.x means that the default StoreKit version now is StoreKit2 which needs that key to work. You can still use StoreKit1 if you pass it as a parameter when configuring the SDK.

Adding the key should be almost immediate and would start working straight away without an app update.

 

Best,

This post has been closed for comments

3 replies

joan-cardona
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • Answer
  • October 27, 2025

Hi ​@upick-ef5b5b,

I checked your account and it looks like you don’t have the in-app purchase configuration key set up. Upgrading from a 7.x to a 9.x means that the default StoreKit version now is StoreKit2 which needs that key to work. You can still use StoreKit1 if you pass it as a parameter when configuring the SDK.

Adding the key should be almost immediate and would start working straight away without an app update.

 

Best,


Forum|alt.badge.img
  • Author
  • New Member
  • November 4, 2025
The issue has been resolved by configuring it to use StoreKit 1. Thank you for your support!

joan-cardona
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • November 10, 2025

Hi ​@upick-ef5b5b,

I’m glad that it’s resolved!

 

Best,