I have been rejected twice under Guideline 2.1(b) because my In-App Purchase subscriptions are not submitted for review. I cannot figure out how to attach them to my submission. Here is my situation: I have 6 auto-renewable subscriptions fully configured in App Store Connect under "Barrel Pro Subscriptions" — all have screenshots, pricing, descriptions, and review notes My app is iOS only, built with React Native/Expo My current version is 1.1, Build 10 (1.1.0) The problem: The "In-App Purchases and Subscriptions" section does not appear anywhere on my version page. I have scrolled to the very bottom and it is not there. I cannot find any way to attach my subscriptions to my submission before clicking "Submit for Review." The blue info box on the Subscriptions page says: "Your first subscription must be submitted with a new app version. Select it from the app's In-App Purchases and Subscriptions section on the version page." But that section does not exist on my version page. What I have tried: Cancelling the rejected submission and starting fresh Creating a new version (1.1) manually Uploading a new build (Build 10) Checking both "In-App Purchases" and "Subscriptions" sections in the sidebar Has Apple removed this section from the version page? How do I attach my subscriptions to my submission in 2026? Any help is greatly appreciated. Thank you.

My first auto-renewable subscription submission is permanently blocked by a stuck subscription group version, and there appears to be no developer-side way to fix it. What happened: A review submission was removed on July 17. That removal left our subscription group's version (subscriptionGroupVersion ID a1e6a10c-e087-4de4-bd9d-e43e6c20bd48, subscription group 22173172, app ID 6762031417) stuck in "In Review" — but it is attached to NO review submission. We verified via the App Store Connect API by listing the items of every review submission on the account: no group-version item exists anywhere. So no reviewer will ever process it. Because the group has no approved version yet, submitting our subscriptions returns STATE_ERROR.SUBSCRIPTION_SUBMISSION_REQUIRES_GROUP_VERSION ("A subscription must be submitted with its subscription group version when the group has no prior approved version"). Attempting to attach the group version to our draft submission returns STATE_ERROR.SUBSCRIPTION_GROUP_VERSION_NOT_SUPPORTED ("is using an older format that is not supported for review submission. Please update before submitting") plus STATE_ERROR.SUBSCRIPTION_GROUP_VERSION_INVALID_STATE (only Prepare for Submission or Developer Rejected states can be submitted). In the App Store Connect UI this surfaces only as the generic banner "There are errors with one or more of your items. To fix them, you need to remove the items and add them again," with one subscription outlined red. Removing and re-adding it does not help. Everything we have tried: Modify or delete the group localization: 409 (NAME cannot be modified / "Cannot delete localization, version is not editable") Modify or delete the group version: 403 (resource only allows CREATE and GET_INSTANCE) Create a fresh group version: 409 STATE_ERROR.ALREADY_EXISTS ("There is already an inflight version...") Rebuild the review submission draft from scratch: identical failure Both subscriptions are READY_TO_SUBMIT with complete metadata; the app version is READY_FOR_REVIEW. Everything else validates clean. Support case 102946032452 is open with all of these details. Request: could someone from the App Store Connect team reset subscriptionGroupVersion a1e6a10c-e087-4de4-bd9d-e43e6c20bd48 to "Prepare for Submission" (and migrate it off the deprecated format)? As far as we can determine, this jammed record can only be cleared server-side.

I'm submitting my first app version along with my first auto-renewable subscription group, and running into an issue. My app version (1.0) submits for review fine on its own — no problems there. But I also need to submit my subscription group for the first time, and Apple requires the first subscription group to be submitted together with an app version. I've created two subscriptions inside one subscription group. For both subscriptions I've completed: Product ID and duration Subscription pricing App Store localization (display name + description) An App Review screenshot (uploaded under Review Information) On the subscription group's "Prepare for Submission" page, when I try to add it to a submission, I get this warning: "Unable to Submit for Review New subscription groups must be submitted with an auto-renewable subscription from within that group. To submit your items for review, add an app version for the selected platform." The "Submit for Review" button stays greyed out. Even though both subscriptions inside the group show "Prepare for Submission" status (not yet "Ready to Submit"), and I don't see where to add the app version to this same submission so they go together. Has anyone run into this? What's the exact sequence to get a subscription group and its subscriptions to actually become submittable alongside a first app version? Is there a step I'm missing on either the subscription pages or the app version page? Any advice appreciated.

Build 1 of my first app was rejected. With it I submitted a monthly subscription IAP. For build 2 I made the corrections outlined in the rejection letter but also change the UI of my payment sheet, therefore I wanted to update the app screenshot and notes for the reviewer, and edit the localization. But, the fields are locked and the IAP is marked as under review. I haven't found a way to remove it from review for editing and resubmission with build 2. I successfully added a new annual subscription IAP for build 2 for my submission but when I pressed submit it said there was an error and I had to try re-attaching it. Very buggy and frustrating experience. Any help is appreciated. Already emailed apple about these issues.

Since the 15 July App Store Connect submission-flow change, I cannot submit my app. Posting the API-level diagnosis because I haven't seen it stated in the other threads, and the UI is actively misleading. What the UI shows: subscription group "In Review", both subscriptions "Prepare for Submission", Add for Review greyed out. Submitting fails with HTTP 409 on POST /iris/v1/reviewSubmissions/{id} (SUBMIT_REVIEW_SUBMISSION_RESPONSE). What the App Store Connect API actually shows: My subscriptionGroupVersion (version 1) is in state IN_REVIEW. No reviewSubmissionItem in any submission references it. All prior submissions are COMPLETE with every item REMOVED. It is orphaned — it went into review with a submission that was rejected, and was never released when that submission completed. Both subscriptions report READY_TO_SUBMIT; their subscriptionVersions are READY_FOR_REVIEW. The products themselves are healthy. The UI's "Prepare for Submission" is wrong. Controlled test: submitting the app version alone succeeds. Re-adding the two subscription versions and submitting → 409, every time. The group version never changes state through that cycle. So the 409 is caused specifically by attaching subscriptions whose parent group version is locked. There is no developer-side fix. subscriptionGroupVersions exposes only POST and GET — no PATCH, no DELETE. Clearing this requires server-side intervention. Same symptoms in posts 838340, 838348, 838369, 838384, 838421, 838425, 838456, 838465, 838473, 838509, 838596. Unfortunately there was no reply from apple that I could find yet. Two asks: has anyone had a stuck group version actually reset, and what did Support do? And if an Apple engineer is reading please confirm whether resetting a subscriptionGroupVersion from IN_REVIEW is something Developer Support can action, or whether it needs a Feedback report.

Hello, Our latest build of our app (App Apple ID: 6741421159) was just approved, but the two new subscription products it supports are still stuck in "Waiting for Review" after 5 days — despite us flagging them in the review notes for that build. The products, both in our "All States Access Plans" subscription group: Yearly Explorer Plan — Product ID: yearlybasic, Apple ID: 6790315023 Monthly Explorer Plan — Product ID: monthlybasic, Apple ID: 6790318915 We have publicly launched this plan. Our paywall loads products dynamically from StoreKit, so the unapproved products don't appear at all — customers responding to the launch cannot see or purchase the plan they came for. We are losing sales and generating support tickets while the launch is live. There are no Resolution Center messages and no requests for additional information. Five other subscription products in the same group are already approved. Could someone from App Review please take a look at these submissions? Happy to provide any additional information needed. Thank you.

Hello, I have two subscriptions stuck in "Waiting for Review" status for 14 days now and I cannot update, edit or remove them. I emailed Apple Support 6 days ago with the specific details but have not received a response as yet. Is there anything I can do as this is blocking an app update. Thank you.

Hey everyone, I'm dealing with a strange issue with auto-renewable subscriptions in my app, and hoping someone can help or point me to the right direction. Here's what happened: Earlier I got my initial app version approved and released with monthly and yearly subscriptions in App Store Connect. And I checked that the app went live, and I could see the subscriptions in a fresh App Store install. But a few weeks after that, I noticed the subscriptions were gone from the app, then I went checking in App Store Connect, and found subscriptions were in some developer attention required state (something along the line). I then submitted a new app version with an additional subscription item, hoping I could reselect the prev 2 subscriptions and the new one for review, together with the new app build. And the subscriptions were in Waiting for Review status. But app reviewer responded that they can't see any subscription for review, and can't proceed with the review. And I noticed that the Subscriptions page shows the banner Your first subscription must be submitted with a new app version. Create your subscription, then select it from the app’s In-App Purchases and Subscriptions section on the version page before submitting the version to App Review., as if I had never got any subscription approved & released before. Now I'm completely stuck. App reviewer can't see the subscriptions, and I see in App Store Connect my subscriptions are in Waiting for Review status. Thanks a lot for any help!

I'm trying to submit my app version together with two auto-renewable subscriptions (both in the same subscription group), and one of the two subscriptions will not submit, while the other submits with no issue. Setup One subscription group ("Crucibull Pro") with two subscriptions: Annual — $49.99/year — submits fine Weekly — $1.99/week — fails to submit Both are being submitted together with a new app build in a single review submission. The errors I get (they vary, none are field-specific) "There are errors with one or more of your items. To fix them, you need to remove the items and add them again to your submission." "Sorry, something went wrong. Try your request again." "An unexpected error was encountered when submitting for review. If the issue persists please contact us." Critically, there is no red/field-level error anywhere on the Weekly subscription's page — its status is "Prepare for Submission" and every field is filled. What I've tried (nothing has worked) Verified every field on Weekly: reference name, product ID, 1-week duration, availability (all countries), price ($1.99 with a valid start date), localization (display name + description), tax category, and an App Review screenshot. Compared Weekly side-by-side with Annual (which submits fine) and matched every field. Changed Weekly's Tax Category to "Match to parent app" to match Annual. Removed and re-added the items to the submission (per the error message's advice) multiple times. Configured the subscription group ranking/levels. Deleted the original Weekly subscription and recreated it from scratch with a new Product ID — same result. Confirmed App Store Connect is stable (System Status all green) and still errors. Tried fresh submissions, different browser/incognito, and re-uploading the screenshot. Current state The Annual sub and the app build are ready and submit fine. The Weekly sub is fully configured, identical to Annual, freshly recreated, on a stable platform — and still throws generic submission errors with no indication of what's actually wrong. Question Has anyone seen an auto-renewable subscription that's fully configured (and identical to a working one in the same group) fail to submit with only generic errors and no field-level detail? Is there a known backend/propagation issue, or a hidden requirement I'm missing? Any way to see the actual validation failure? Thanks in advance.

I'm unable to submit my first auto-renewable subscriptions and I'm stuck in what looks like an App Store Connect backend inconsistency. Hoping someone has hit this and found a workaround. Setup App: existing app, version 1.0.0 already approved and live. New version 1.0.1 (build 7) uploaded, currently in "Prepare for Submission". Two first-time auto-renewable subscriptions in one subscription group: family_monthly and family_pro_monthly. Both fully configured: pricing, availability in all regions, localizations, and review screenshot. The problem The "In-App Purchases and Subscriptions" section does NOT appear on the app version page. The page goes straight from the Build section to Game Center — the IAP/subscription selection section is missing entirely, so I cannot attach the subscriptions to the version submission (required for a first submission). Both subscriptions are stuck in "Waiting for Review" (the group now shows "In Review"), even though they are NOT part of any submission. In App Review > Submissions, my only two submissions ever are 1 item each (1.0.0 completed, and a 1.0.1 that I deleted) — neither ever contained the subscriptions. Because I can't attach them, submitting the app alone yields a 1-item submission and gets rejected under Guideline 2.1(b) (reviewer can't locate the in-app purchases). This has happened twice. What I've already tried (no effect) Hard refresh; Chrome and Safari. Removing and re-adding the build to the version. Deleting the review submission (version returned to "Prepare for Submission"). The "Cancel" button on the subscription group (does nothing). Editing + saving the subscriptions to force a state recompute. Environment Paid Apps Agreement is active. Roles are correct (Account Holder). The subscriptions never entered "Ready to Submit" — they appear to have jumped straight to "Waiting for Review", which seems to be why the version page's IAP section never renders (it only offers subscriptions in "Ready to Submit"). Questions Has anyone recovered subscriptions stuck in "Waiting for Review" that aren't attached to any submission — back to "Ready to Submit"? Any known way to force the "In-App Purchases and Subscriptions" section to appear on the version page? I've also opened a case with Developer Support for this. Any pointers appreciated.

I submitted my app, PerkPulse, for review and it got rejected due to EULA agreement not being in app description, and for the subscriptions not being attached to the subscription. Currently, when I try to submit my app and two subscriptions, I get the error, "There are errors with one or more of your items. To fix them, you need to remove the items and add them again to your submission." and it highlights one of my subscriptions. This is very frustrating and is blocking me from submitting my app for review. PerkPulse Pro Annually - product ID: app.perkpulse.mobile.pro_annual_v3 PerkPulse Pro Month - product ID: app.perkpulse.mobile.pro_monthly_v3 When I open the subscription group, it shows as "In Review", but I do not see any option for removing it from review so that I can attach my subscriptions. I have also had a phone call with apple support and could not get the issue resolved. I have: Deleted and recreated the subscriptions Checked all input fields, agreements to sign, etc. and cannot find an empty field Removed and re-added the subscriptions to draft submission Please any help would be appreciated.

I have an app update that is completely ready for submission. This update incorporates a subscription for new functionality. I'm unable to submit as the subscription is stuck in the "Prepare for submission" state instead of going to "Ready to submit" and I'm unable to include it with my app. After doing some research, I found that the banking information on my developer account is broken. I tried to update and fix this information. However, I get an error saying that it is unable to find "Bank of America". I suspect this is causing everything else to be stuck in the "Prepare for submission" state. Does anyone know how to work around this issue or can someone at Apple give me an ETA as to when things will be fixed. This issue is delaying my release. - Ken

I have two subscription in the same group and the same level 1. One is a monthly one and the other a yearly one. I also have an IAP for Lifetime Unlock. When my app requests for these it only loads Monthly. Debugging reveals that the ASC doesn't return the yearly subscription and the lifetime IAP. When I added a StoreKit config to the app, it correctly show the Yearly subscription as well and the view loads it appropriately. But the storekit config doesn't load IAP. I have checked things several tiles in ASC and in code. What can I do to fix this?

I'm trying to submit my app version together with two auto-renewable subscriptions (both in the same subscription group), and one of the two subscriptions will not submit, while the other submits with no issue. Setup One subscription group ("Crucibull Pro") with two subscriptions: Annual — $49.99/year — submits fine Weekly — $1.99/week — fails to submit Both are being submitted together with a new app build in a single review submission. The errors I get (they vary, none are field-specific) "There are errors with one or more of your items. To fix them, you need to remove the items and add them again to your submission." "Sorry, something went wrong. Try your request again." "An unexpected error was encountered when submitting for review. If the issue persists please contact us." Critically, there is no red/field-level error anywhere on the Weekly subscription's page — its status is "Prepare for Submission" and every field is filled. What I've tried (nothing has worked) Verified every field on Weekly: reference name, product ID, 1-week duration, availability (all countries), price ($1.99 with a valid start date), localization (display name + description), tax category, and an App Review screenshot. Compared Weekly side-by-side with Annual (which submits fine) and matched every field. Changed Weekly's Tax Category to "Match to parent app" to match Annual. Removed and re-added the items to the submission (per the error message's advice) multiple times. Configured the subscription group ranking/levels. Deleted the original Weekly subscription and recreated it from scratch with a new Product ID — same result. Confirmed App Store Connect is stable (System Status all green) and still errors. Tried fresh submissions, different browser/incognito, and re-uploading the screenshot. Current state The Annual sub and the app build are ready and submit fine. The Weekly sub is fully configured, identical to Annual, freshly recreated, on a stable platform — and still throws generic submission errors with no indication of what's actually wrong. Question Has anyone seen an auto-renewable subscription that's fully configured (and identical to a working one in the same group) fail to submit with only generic errors and no field-level detail? Is there a known backend/propagation issue, or a hidden requirement I'm missing? Any way to see the actual validation failure? Thanks in advance.

Hello everyone, We have a SaaS product and are currently transitioning our business model. Previously, we used a standard recurring subscription model implemented via StoreKit 2 in our iOS app. Recently, we changed our pricing to a performance-based model, where we charge a percentage fee based on the user's specific usage and performance. On our web platform, we use Stripe to calculate and accept these dynamic percentage-based payments. I have two questions regarding this transition for our iOS app: Payment Gateway: Since our new pricing model is a variable, performance-based percentage rather than a fixed subscription, does Apple allow us to integrate Stripe directly into the iOS app to process these payments? The service provided is digital. Removing Old Subscriptions: We have completely commented out all StoreKit code in our app build since we are no longer offering those plans. However, we cannot find a "Delete" option in App Store Connect to remove the old subscription items. What is the proper way to completely remove these from our app's backend and store listing? Any guidance on the best way to handle this transition and remain compliant with App Review would be greatly appreciated. Thank you!

Hello, We are experiencing an issue with App Store Connect and would like to know if anyone has encountered the same problem. Current status: Our app is already approved and live on the App Store. We created three new auto-renewable subscriptions. All three subscriptions have been stuck in "Waiting for Review" for several days. The subscriptions can no longer be edited (localization and review information are locked). The app review has already been completed, so there is no active app review in progress. During this period, Apple System Status reported an App Store Connect incident affecting submission of In-App Purchases and subscriptions. Since that incident was resolved, the subscriptions are still stuck in Waiting for Review. We have already contacted Apple Support and App Review multiple times but have not yet received any response. Has anyone experienced subscriptions remaining permanently in "Waiting for Review" after the App Store Connect maintenance? Is there anything that can be done from the developer side, or does this require Apple to manually reset the review state? Thank you.

I have implemented subscription renewals in my app and now want to integrate a referral system. Each user should receive a unique referral code that they can share with others. When a new user signs up using a referral code, both the referrer and the referred user should receive a bonus. What is the best approach to implementing this feature efficiently?

Hi all — hoping someone from the App Review team can help with this. App: ContentCam: Dual Camera Video (App ID 1281521467) Submitted two auto-renewable subscriptions (Annual + Monthly) under subscription group "ContentCam Premium" over a week ago (App version 2.0 as well as 2.0.1). App version 2.0 and 2.0.1 was reviewed and approved independently. The subscriptions have not moved from "Waiting for Review" despite the binary being approved. No rejection message, no metadata flag, nothing actionable showing on my end. This matches reports I've seen from other developers here: once an app version is rejected and later resubmitted/approved, the attached subscriptions can get stuck in "Waiting for Review" indefinitely, disconnected from the binary review outcome. I've contacted Apple Developer Support (case open, no resolution yet). Posting here in case this needs engineering visibility, or if anyone has a workaround that's actually worked (not just "wait" or "resubmit a new build" — already tried the latter with no effect). Thanks in advance.

M y app was approved and is now live on the App Store, but all four auto-renewable subscriptions are still Waiting for Review in App Store Connect. Because of this, the production app's StoreKit 2 call to Product.products(for:) returns 0 products, and users see: "No subscription products were returned by the App Store." There are no metadata errors or warnings—only Waiting for Review. My questions are: Is it normal for an app to be released before its subscriptions are approved? While subscriptions are in Waiting for Review, is it expected that Product.products(for:) returns an empty array? Has anyone experienced this, and how long did it take for the subscriptions to be approved after the app was already live? I've attached: App Store Connect screenshot showing all four subscriptions in Waiting for Review. App screenshot showing the "No subscription products were returned by the App Store." message. Any insight would be greatly appreciated. Thanks!

Hi all, Reporting an active production issue in case anyone else is seeing the same pattern, or has insight into what could cause this. Symptom As of 2026-05-09 morning, one specific auto-renewable subscription product is silently absent from Production StoreKit responses on our live App Store build. The product is still 'Approved' in App Store Connect, all metadata is intact, no error code is returned — the product simply does not appear in the products array. The other 3 products in the same subscription group continue to work normally. 100% of production users are affected. Setup App: live on App Store, version 1.0.0 (build 8) Subscription group with 4 auto-renewable products: standard_monthly_799 ✅ returns correctly standard_annual_6999 ✅ returns correctly unlimited_monthly_1299 ❌ MISSING from production response unlimited_annual_9999 ✅ returns correctly SDK: purchases_flutter (RevenueCat) → StoreKit Same physical device, same code, same RC config behaves correctly in Sandbox — all 4 products are returned and a sandbox purchase of unlimited_monthly_1299 succeeds. Timeline 2026-05-08: working correctly, purchases succeeding normally 2026-05-09 morning: product silently disappears from production StoreKit responses No app update was submitted between those dates No App Store Connect changes were made Onset was simultaneous across all production users at one timestamp What I've verified App Store Connect: Product status: Approved All territories enabled, all prices configured (no N/A in any territory) Subscription group correctly contains all 4 products No 'Submit for Review' pending changes Product attached to live app version 1.0.0 (8) Tax category: Match to parent app Family Sharing: Off (consistent with the working products) Paid Applications Agreement: Status: Active Banking and Tax forms: Active RevenueCat dashboard: All 4 products show Store Status: Approved Default offering contains all 4 packages iOS attachment for the affected product is intact No warnings or sync errors Sandbox StoreKit (today): flutter run (debug) on physical device → all 4 products returned flutter run --release on physical device → all 4 products returned Sandbox purchase of unlimited_monthly_1299 succeeds Production StoreKit (today, broken): App Store-downloaded 1.0.0 (8) on multiple users' devices Multiple Apple IDs / multiple devices / multiple regions — all reproduce Only unlimited_monthly_1299 affected; other 3 products fine Why this looks server-side Sudden simultaneous onset across all users No code or config change preceded onset Sandbox unaffected, only Production affected Single product affected, not the whole subscription group or app No error returned — silent omission only Cannot reproduce with locally signed builds, only with App Store-distributed binary This pattern is consistent with a server-side product indexing or fronting issue specific to one product in Production StoreKit. As a developer I don't have visibility into Apple's product-serving infrastructure to investigate further — looking for guidance from anyone who has seen this before. Questions for the community Has anyone else seen a single auto-renewable subscription silently drop out of Production StoreKit responses while remaining Approved in ASC, with no error code returned? Is there any internal product-state flag (beyond what's exposed in the ASC UI) that could cause Production StoreKit to silently omit a product? Anything similar to a hidden 'review hold' or 'price tier reconciliation' state? Has the asymmetry between RevenueCat package identifiers (Standard uses RC's $rc_monthly/$rc_annual default identifiers, Premium uses custom premium_monthly/premium_annual identifiers) ever been implicated in this kind of failure? RC support has been notified, but worth asking publicly. For anyone who has resolved a similar issue: what action ended up clearing it — ASC re-save, RC re-sync, Apple Support escalation, or did it self-resolve after Apple-side cache propagation? Filings in progress ASC Contact Us ticket: filed Apple DTS technical incident: filed RevenueCat support ticket: filed Feedback Assistant report: in progress Will update this thread with the resolution path once we have one. Thanks, — Kin Pong Lo (developer, Alice: AI English Tutor)