Hello RevenueCat Team,
I’m facing a circular issue during the App Store review process and would appreciate your guidance.
I’ve implemented a hardcoded paywall UI on the client side (not relying on dynamic offerings), and completed all setup:
-
Subscription products are created in App Store Connect
-
These products are added to a new Offering in RevenueCat
-
The Offering is configured, but the product has not yet been approved by Apple
During app review, since the in-app purchase product isn’t approved, the Offering isn’t accessible via the RevenueCat SDK.
Because of that, Apple sees the paywall but encounters a missing product error when attempting to make a purchase, leading to a rejection under Guideline 2.1 - App Completeness.
Ironically, Apple is telling me they can’t approve the subscription product until it’s accessible in-app, but I can’t access it in-app until it’s approved and synced to RevenueCat.Despite explaining this situation to the App Store reviewers, our submissions continue to be rejected — so I'm stuck.
My questions:
-
In this situation, is there a way to manually test or expose a pending IAP product in the app during review, even if it’s not yet available through the
offeringsendpoint? -
Is there a workaround or recommended approach (e.g. static fallback + product identifiers) to handle this chicken-and-egg problem with RevenueCat and App Review?
-
What’s the proper order of operations when submitting a new app version and new IAP products, especially if I’m using RevenueCat for subscription management?
Any advice to ensure the app passes review while using RevenueCat would be extremely helpful.
Thank you!
