Hi Apple Developer Forums, I am experiencing a repeated issue with auto-renewable subscriptions during App Review for my iOS app. The app uses RevenueCat for subscription management. The subscription products exist in App Store Connect and are correctly configured, but they remain in "Waiting for Review". During App Review, the reviewer attempts to access the subscription paywall and receives an error stating that subscriptions are unavailable. This appears to happen because StoreKit cannot fetch the products while they are still waiting for review. This creates a loop: Subscriptions exist in App Store Connect and are in "Waiting for Review" App Review installs the app StoreKit cannot return the subscription products yet RevenueCat returns an "offerings_fetch_failed" error The reviewer sees "subscriptions unavailable" The app is rejected before the subscriptions are approved We have thoroughly verified the configuration: • Subscription group exists • All products are inside the group • Product IDs match exactly between App Store Connect and RevenueCat • RevenueCat is correctly configured with the Apple App Store API key • Offerings and packages are correctly configured in RevenueCat • The app correctly handles missing offerings and displays a fallback message • The latest TestFlight build shows a diagnostic message confirming the issue originates from StoreKit not returning products • The app build itself installs and runs normally This has now happened multiple review cycles and we have verified all configuration options. At this stage the only remaining explanation appears to be the order of the review process. It seems the subscriptions must be approved before StoreKit can return them, but the app is being evaluated before the subscriptions have been processed. Because of this, the reviewer sees the "subscriptions unavailable" message and rejects the app before the subscriptions have been approved. Is there a recommended process for submitting the first app version with auto-renewable subscriptions to avoid this situation? Specifically: • Should the subscriptions be approved before the app review begins? • Or is there a specific way to attach the subscriptions to the version when the "Add" option is not visible on the version page? Any guidance would be greatly appreciated as we have now thoroughly checked all configuration and believe this may be a review workflow issue rather than a configuration problem. Thank you.

Hello, We are hoping someone from Apple or other developers who have encountered this recently can help clarify the correct process, as we appear to be stuck between the current App Store Connect UI and documentation that references an older submission flow. Issue during App Review Our app is being rejected with: Guideline 2.1(b) – Performance – App Completeness Subscriptions in the app were still unavailable for users to purchase. However, the subscriptions do exist and are configured correctly in App Store Connect. The app contains four auto-renewable subscriptions (monthly and yearly tiers across two service levels). All of them are currently in “Waiting for Review” status. The app uses RevenueCat with StoreKit to retrieve products. When products are still Waiting for Review, Apple does not return them to StoreKit, which results in the app correctly reporting that the subscriptions are unavailable. Because of this, it appears that the reviewer may be testing the app before the subscriptions have been approved, preventing StoreKit from returning the products. Problem with Apple documentation / submission workflow The responses we are receiving from App Review repeatedly point us to the documentation: “Submit an In-App Purchase” (App Store Connect Help → Manage submissions to App Review) This documentation states that subscriptions must be attached to the app version using the: “Select In-App Purchases or Subscriptions” option on the version page. However, this control does not exist in our App Store Connect interface. Our interface appears to follow the newer App Store Connect submission flow, where subscriptions are configured and submitted from their own product pages, and are automatically bundled with the app submission. Because of this: The “Select In-App Purchases or Subscriptions” step referenced in the documentation cannot be completed. There is no “Add” or “Select” button on the version page. This leaves us stuck in a loop where: Apple support points us to documentation describing the older workflow. The step described in the documentation does not exist in the current UI. The app is reviewed before the subscriptions are approved, causing the purchase flow to appear unavailable. Attempts to resolve We have already: Verified product identifiers match between App Store Connect and RevenueCat Confirmed RevenueCat is using the correct Apple public SDK key Verified the offerings and packages are correctly configured Confirmed the app fetches the correct product identifiers Followed the “Submit an In-App Purchase” documentation thoroughly Despite this, we cannot complete the step described in the documentation because the UI element referenced there is not present. Additionally, we have: Submitted multiple App Store Connect review responses Submitted multiple support requests Unfortunately, the replies we receive continue to reference the same documentation without addressing the specific issues described above. What we are hoping to clarify We would really appreciate if someone could address the following questions specifically, rather than pointing us back to the same documentation: In the current App Store Connect submission flow, how are subscriptions supposed to be associated with a new app version if the “Select In-App Purchases or Subscriptions” option no longer exists? When subscriptions are Waiting for Review, will StoreKit return them to the app during App Review, or must they be approved first before they can be fetched? Is there anything additional required in the new submission flow to ensure subscriptions are reviewed and available before the app is evaluated? Request If someone from Apple or another developer who has encountered this recently could please respond directly to the issues described above, it would be greatly appreciated. At the moment we appear to be stuck between: documentation referencing a previous App Store Connect workflow, and the current UI, which does not allow that documented step to be completed. Thank you for your time, and any clarification would be very helpful.