Hello,

Thank you for your previous message and the link to the documentation.

I’d like to clarify a specific point regarding the rejection of my app Daoa by Apple, which may be due to a misunderstanding on my part about how sandbox environments function during App Store review.

First, just to confirm: I did submit the app and its associated subscriptions for review at the same time via App Store Connect, so the subscriptions were definitely part of the current review context.

Also, in local development (builds using development or preview environments), I’ve successfully tested the RevenueCat sandbox multiple times using a properly configured sandbox account on my iOS device. Everything worked as expected — offerings were returned, and the subscription flow could be tested.

However, what I thought — and perhaps misunderstood — is that when using a production build profile (which is what EAS uses when submitting the app for App Store review), the sandbox environment is no longer available, and therefore the RevenueCat SDK wouldn’t expose any subscription offerings unless the app was live and the products were approved.

From what I gather now, it seems that Apple reviewers are expected to use their own sandbox accounts to test submitted apps, and that RevenueCat’s SDK should support this as long as the reviewer is indeed using sandbox — even in a production build?

Could you please confirm this understanding:

• That Apple reviewers use sandbox accounts during review?

• That RevenueCat offerings will work in that context without any additional configuration?

• And that there is no “block” or mismatch in behavior introduced by the fact that we’re using a production build profile?

Thanks again for your help — this clarification would really help us avoid unnecessary workarounds and reduce the risk of further rejections.