ERROR [RevenueCat] 🍎‼️ Error fetching offerings - The operation couldn’t be completed. (RevenueCat.OfferingsManager.Error error 1.)
There's a problem with your configuration. None of the products registered in the RevenueCat dashboard could be fetched from App Store Connect (or the StoreKit Configuration file if one is being used).
1. I am working on an expo project on my linux machine
2. I have apple developer account
3. created the subscription product, it is ready to submit state
4. have added the the keys in revenue cat dashboard which imported the product
5. the entitlement is attached with the product
6. Paywal has both android and ios offering
I have been trying to debug this but i am going no where, please help.
Question
Please help! Paywall not showing, offering not fetching.
This post has been closed for comments
+6Hey
Looking at your configuration everything seems to be configured properly as I can see some Android requests coming through, but iOS (especially in an Expo environment) can be a bit more tricky.
We have a great blog by Perttu, a Developer Advocate at RevenueCat, with best steps and some tips on how to get this working properly: https://www.revenuecat.com/blog/engineering/how-to-add-in-app-purchases-to-your-bolt-generated-expo-app/
Summary: Bolt-generated apps previewed in Expo Go cannot support RevenueCat subscriptions due to missing native modules. To enable in-app purchases, developers must export the project, configure EAS Build, and install the RevenueCat SDK locally. Subscription products should be created in Google Play Console, linked to RevenueCat, and assigned to offerings. Subscriptions are then managed via entitlement checks, which control gated content access.
Building with EAS enables full subscription functionality for production Android apps.
It’s written based on a Bolt setup, but it should hopefully help too. We also have some internal documentation that can add extra context: https://www.revenuecat.com/docs/getting-started/installation/expo#create-an-expo-development-build
Additionally, how are you testing your iOS build? Is it in a simulator? I ask, as in specific iOS versions of 18.4 and 18.5 (simulators only) there is a known StoreKit Issue that would cause the behavior you’re seeing.
Could you double check how you’re looking to run your iOS app and the testing devices used?
Went through the whole steps, and then saw that paid apps agreement was not approved, once it is done, after 24hr it started to work. Thank you.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.