Hello,
I need guidance on App Store Connect product state vs StoreKit behavior during App Review.
Stack: iOS app (Expo / React Native), subscriptions via RevenueCat + StoreKit. Bundle ID matches App Store Connect.
RevenueCat API keys — what I’ve verified locally:
With the production RevenueCat API key (iOS appl_..., same as the submitted build), everything works on local device but not when I download it from TestFlight.
I have also tested with RevenueCat’s sandbox / test API key (the separate key intended for sandbox/testing). That setup works as well — I can load offerings and complete test purchases the same way
What RevenueCat (SDK / dashboard health) reports:
Product monthly is configured in RevenueCat.
Warnings that products aren’t approved in App Store Connect yet and that the default offering has configuration issues.
Apple’s product state: WAITING_FOR_REVIEW.
The SDK still states that test purchases are possible.
What App Review reports:
After onboarding a new business account, “Activate subscription” leads to an error (plans don’t load / purchase path fails).
Review suggested an app code issue.
Why this is confusing:
Locally, both RevenueCat key modes I tried (production and sandbox/test) work with Apple Sandbox on the device. The submitted build uses the production RevenueCat key. Review still sees a failure.
Questions:
For IAP in WAITING_FOR_REVIEW, should App Review always use an Apple Sandbox account to test subscriptions until the product is fully approved?
Is it documented that StoreKit may not return products during review without Sandbox while the product remains WAITING_FOR_REVIEW?
Has anyone else seen “works locally (prod + sandbox RevenueCat keys + Apple Sandbox) but Review fails” with the same WAITING_FOR_REVIEW state?
Thanks for any official documentation or similar threads.
Topic:
App & System Services
SubTopic:
StoreKit
Tags:
Subscriptions
App Review
StoreKit
In-App Purchase
1
0
86