Summary After setting a single auto-renewable subscription product (not the app) to "Developer Removed from Sale" in App Store Connect, the next scheduled renewal for an existing active subscriber failed with DID_FAIL_TO_RENEW v2 and expirationIntent = 5 ("expired for some other reason"). I expected expirationIntent = 4 ("product wasn't available for purchase at the time of renewal"), since the product was, in fact, not available for purchase. I would like to confirm whether 5 is the documented/expected value for this scenario, and how to deterministically distinguish "developer removed product from sale" from other renewal failures using the notification payload. Reproduction / observed sequence Day 15: Changed product annual_promo (auto-renewable subscription) status from "Approved" to "Developer Removed from Sale" in App Store Connect. The app itself remained Approved and on sale. Other subscription products in the same group remained Approved. Day 16: An existing active subscriber on that product had a scheduled automatic renewal date. Result: Renewal did not occur. We received a DID_FAIL_TO_RENEW v2 notification. Payload (relevant fields): JWSRenewalInfoDecodedPayload.expirationIntent = 5 JWSRenewalInfoDecodedPayload.autoRenewStatus = 0 Questions Is expirationIntent = 5 the correct/expected value when a renewal fails because the developer removed the product from sale? Or should it have been 4 ("product wasn't available for purchase at the time of renewal")? If 5 is intentional, what is the engineering rationale for not using 4 in this scenario? Given that expirationIntent = 5 is documented as a catch-all ("some other reason"), which other fields in the DID_FAIL_TO_RENEW payload (e.g., subtype, autoRenewStatus, gracePeriodExpiresDate, signedTransactionInfo) should we inspect to deterministically classify the failure cause and isolate "developer removed product from sale" from billing failure / customer cancel / price-increase not accepted / etc.? Context I'm aware of the docs page In-App Purchase statuses and Set availability for an auto-renewable subscription, but they describe the status semantics, not the resulting notification payload. Product has been reverted to "Approved" to avoid further impact on subscribers while this is clarified. Thanks in advance.

Getting 2.1(b) rejection. Reviewer sees "Purchase Failed" alert. Products configured correctly in ASC. Does App Review sandbox use same sandbox environment as developer testing? Can reviewer sandbox accounts trigger purchase failures that developer sandbox accounts cannot? Any known issues with first-time IAP products failing specifically during App Review sandbox session?

Hi all, Trying to submit my first-ever auto-renewable subscription (Pro Monthly) together with my app version (1.0.2, App ID 6789196311). App Store Connect's Draft Submission UI just shows the generic 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." Removing and re-adding the subscription (tried multiple browsers, multiple review screenshot sizes/formats) does not fix it. Inspecting the actual API response via DevTools Network tab, the real error is: STATE_ERROR.ENTITY_STATE_INVALID "subscriptionVersions with id '...' is not in valid state." Associated error: 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." This is the first subscription ever in this subscription group, so the group has no prior approved version — which matches the error message. But there's no visible UI option anywhere in App Store Connect to create or attach a subscription group version to the draft submission. Has anyone hit this exact error and found a fix? I found one similar thread where someone got STATE_ERROR.ALREADY_EXISTS when trying to create a group version via the API (an "inflight" version already existed), and then SUBSCRIPTION_GROUP_VERSION_NOT_SUPPORTED when trying to attach that existing version, because it was in an "older format." Wondering if this is a known backend issue. Already ruled out: Paid Applications Agreement (Active), banking/tax info (Active), screenshot format (RGB, no alpha, multiple official sizes tried). Any help appreciated — also filed a formal Contact Us case for this (App, Build and Version Management). Thanks!

Hello, We are using Apple’s Advanced Commerce API and are seeing intermittent failures when reactivating a subscription from the app using REACTIVATE_SUBSCRIPTION. Reproduction flow: Purchase a regular StoreKit auto-renewable subscription. Migrate the subscription to Advanced Commerce. Disable auto-renewal from Apple’s native subscription settings. Return to the app and try to reactivate the subscription from our subscription settings page. This exact flow was working successfully few days ago. The payload structure has not changed, but the same flow now sometimes works and sometimes fails with: Error Domain=StoreKit.InvalidRequestError Code=1 The operation couldn’t be completed. (StoreKit.InvalidRequestError error 1.) userInfo=[:] We reproduced this with a newly created Sandbox Apple Account and a newly purchased/migrated subscription. Questions: Is there a known issue with Advanced Commerce reactivation? What does StoreKit.InvalidRequestError code 1 mean in this context? Is there a way to get the underlying rejection reason? Thank you.

My iOS app's first submission (ThymeBlock, Apple ID 6779269775) was rejected under 2.3.2 solely over the OPTIONAL promotional images on my two auto-renewable subscriptions. The required fix, deleting the images, was impossible: both subscription records were locked in "Waiting for Review" and the image field disabled. My reply in the submission thread went unanswered for 48+ hours, so I cancelled the submission (standard advice). The cancel completed, no submission exists anymore, and both subscriptions REMAIN locked in "Waiting for Review", held by nothing. I cannot edit them and cannot delete the flagged images, so resubmitting the app version cannot satisfy the rejection: the change App Review required is impossible to make. Developer Program Support has so far responded with unrelated information, and on a call suggested the subscriptions are in review due to "pending charges from July 18", which seems impossible since the app has never been released and has zero customers. This matches threads 705460 and 717024 (same lock; resolved only by Apple server-side). Case number: 20000117635283. Could App Review or App Store Connect staff release my two subscription records to an editable state, or remove the two promotional image as the rejection requested?

I'm stuck on this and genuinely don't know what's wrong. I have two auto-renewable subscription groups in one app. I pass all six product IDs to a single Product.products(for:) call. It succeeds, doesn't throw, and returns three products — all from group A. The three from group B just aren't in the array. No error, they're simply absent. All six show Approved in App Store Connect. [PlusStore] probe — storefront: USA [PlusStore] probe — OK ...plus.monthly (group A) [PlusStore] probe — OK ...plus.quarterly (group A) [PlusStore] probe — OK ...plus.yearly (group A) [PlusStore] probe — MISSING ...plus.founding.monthly (group B) [PlusStore] probe — MISSING ...plus.founding.quarterly (group B) [PlusStore] probe — MISSING ...plus.founding.yearly (group B) Retried three times with backoff, so it isn't cold-launch timing. I don't think it can be the Paid Applications Agreement, the sandbox account, a network failure, or a wrong bundle prefix, since group A comes back fine. I've checked the group B IDs character-for-character against the Product ID field in App Store Connect, confirmed United States is enabled with an active price and no future-dated schedule on all three, and confirmed there's no .storekit file attached to the scheme. So the only difference I can find between the two groups is the group itself.

I'm trying to enroll in the Apple Developer Program. Following Apple's instructions, I developed an app on my Mac, signed in with the Apple ID that I want to use for the Developer Program, and attempted to enroll. However, I consistently receive the following error: "Unable to continue. Contact support at https://developer.apple.com/contact/." I contacted Apple Developer Support and a support ticket (102918021274) was created during the first week of June 2026. Since then, I've provided all the requested information, including screen recordings and other evidence. The support team later informed me that the case had been escalated to the Operations team and was being handled as a priority. It has now been more than two weeks since the escalation, and I still haven't received any update or resolution. Has anyone else experienced a similar issue? Is it normal for the Operations team to take this long to investigate an enrollment problem after all the required evidence has already been provided? Also, does Apple have any service-level agreement (SLA) or expected turnaround time for resolving Developer Program enrollment cases? Any insights or suggestions from others who have gone through this process would be greatly appreciated. Thank you.

I am unable to load newly created auto-renewable subscriptions in the StoreKit sandbox environment. The issue occurs in multiple apps under my developer account and is reproducible both in the iOS Simulator and on a physical device. StoreKit consistently returns an empty product list without reporting an error. I have attempted to load the subscriptions in two ways: Directly using their product identifiers Using SwiftUI’s SubscriptionStoreView with the subscription group ID Neither method returns any products. Troubleshooting steps already completed Confirmed that the bundle identifiers and app versions match between Xcode and App Store Connect Confirmed that the subscription groups and subscriptions are in the Prepare for Submission state Added all required subscription metadata, including review screenshots Changed the bundle identifier in both Xcode and App Store Connect Created new subscription groups with new product identifiers Confirmed that the Paid Apps Agreement is active Confirmed that the scheme’s StoreKit configuration is set to None Tested on an iOS 17.5 Simulator Tested on a physical device running iOS 26.5.2 Confirmed that my Apple Developer Program membership is active and has several months remaining Because the same issue affects two separate apps, I suspect that it may be related to my developer account or the StoreKit sandbox rather than an app-specific implementation problem. Developer account Team ID: 2H346S9B67 First app Bundle ID: com.sajjadalhusseini.photo-cleaner Apple App ID: 6794888780 First subscription group Group ID: 22266157 Product IDs: quest_monthly quest_annual Second subscription group Group ID: 22267268 Product IDs: quest_weekly2 quest_annual2 Second app Bundle ID: com.sajjadalhusseini.babyjournal Apple App ID: 6795026684 Subscription group Group ID: 22267241 Product IDs: com.sajjadalhusseini.babyjournal.monthly com.sajjadalhusseini.babyjournal.yearly Anyone has faced this issue before and know how to fix it? it's seems to be new because I didn't face it with an app I made two weeks ago. Would really appreciate help with this.

Summary: Product.products(for:) returns an empty array with no thrown error for every in-app purchase, across multiple subscription groups, on a physical device with a valid storefront. This is blocking App Review — the reviewer reports the same "products cannot be loaded" symptom (rejected under 2.1(b)). No version of the app has been approved yet (first version is in review). What I've confirmed is NOT the cause: Paid Apps Agreement: Active. Bank Account: Active and verified. Tax Forms: Active. Storefront: confirmed correct on-device via Storefront.current. Product IDs match exactly between the app and App Store Connect. Key evidence (controlled test): There are 4 subscription products across 3 groups: 2 products in REJECTED state 2 fresh products in READY_TO_SUBMIT state, in separate groups, never submitted Requesting all four IDs in a single Product.products(for:) call on a physical device returns zero products and throws no error. So it is not the rejected state of the first two, not a single corrupt record, and not a group-level issue — brand-new READY_TO_SUBMIT products in independent groups also fail to load. The only thing all products share is the app/account. Questions: Beyond an Active agreement + verified banking + verified tax forms, what else must be complete before StoreKit will vend any product for an app whose first version has not yet been approved? Is there a known condition where READY_TO_SUBMIT products in a never-approved app return an empty array (rather than an error)? If review requires products to load, but products won't load before some precondition is met, how is that circular dependency intended to be resolved? NOTE: A prior impossible to submit subscription was working no problem it just throw a red unknown error. Minimal repro available on request. Thank you.

Hi everyone, I'm hoping someone from Apple or another developer has seen this before because I'm completely blocked from submitting my first auto-renewable subscription. Setup First app submission App version: 1.0 (Build 34) One auto-renewable subscription Five consumable IAPs Everything configured in App Store Connect StoreKit works correctly in TestFlight Subscription purchases complete successfully in TestFlight RevenueCat configuration has been verified Subscription review screenshot is uploaded and processed successfully Problem App Store Connect shows: "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." The draft contains: App Version 5 Consumable IAPs 1 Subscription When I submit through the App Store Connect API I receive: 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. That makes sense because this is my first subscription. However, when I attempt to create a subscription group version I receive: STATE_ERROR.ALREADY_EXISTS Version already exists. There is already an inflight version with id: bf2f7b5b-7fbd-44fc-9c67-af1297f3d76a So I then attempted to add that existing SubscriptionGroupVersion to the review submission. Apple responds with: STATE_ERROR.SUBSCRIPTION_GROUP_VERSION_NOT_SUPPORTED Subscription group version bf2f7b5b-7fbd-44fc-9c67-af1297f3d76a is using an older format that is not supported for review submission. Please update before submitting. and also: STATE_ERROR.SUBSCRIPTION_GROUP_VERSION_INVALID_STATE Subscription group version bf2f7b5b-7fbd-44fc-9c67-af1297f3d76a cannot be submitted. Only versions in Prepare for Submission or Developer Rejected can be submitted. The issue I'm now stuck because: Apple says I must submit a SubscriptionGroupVersion. Apple says one already exists. Apple will not allow me to create a replacement. Apple will not allow me to submit the existing one. Apple says the existing one is using an older format. I cannot find any way in App Store Connect to update, replace or delete this SubscriptionGroupVersion. Things I've already verified Build 34 is attached correctly. Subscription Product ID is correct. RevenueCat configuration is correct. StoreKit loads the subscription successfully. Purchases work in TestFlight. Subscription review screenshot exists and is COMPLETE. Localizations, pricing and availability are all configured. The issue occurs both in App Store Connect and when submitting via the App Store Connect API. Question Has anyone encountered this before? Is there a way to regenerate or migrate a SubscriptionGroupVersion into the new format from App Store Connect, or is this something Apple Developer Support has to reset on the backend? Any advice would be greatly appreciated. Thanks!

I'm using TestFlight to test an app with payment/subscription functionality. I created sandbox accounts in AppStore Connect accordingly to be able to test the subscriptions. I'm logged in with the sandbox account. When I try to subscribe in the App the wrong account (this is my actual real AppleID) is used for the subscription although it is recognized that this is just a sandbox subscription. I tried: logging off/on into the sandbox account creating a totally new sandbox account trying to trigger the payment with no logged in sandbox account The result is always: in the payment popup it is stated that the purchase account will be my original AppleID and not a sandbox account. How can I switch the accounts? Is this a bug at Apple's side somehow?

I ran into a strange issue while testing my subscriptions through TestFlight. RevenueCat returned the correct monthly and yearly product IDs, but StoreKit returned zero products. Pricing, availability, agreements, bundle ID, and product configuration were all correct. The problem was the order I added items to the App Review draft. I initially added the subscription products first and the subscription group afterward. What fixed it, Removed everything from the draft. Added the subscription group first. Added the monthly and yearly products afterward. The products then appeared in TestFlight sandbox and purchases worked. No new build or App Review approval was needed. Has anyone else experienced this? I couldn’t find this ordering requirement in Apple’s documentation.

Hi everyone, I’m currently stuck with a blocking issue in App Store Connect and would really appreciate any guidance or insight. Issue: My app version (iOS App 1.0) is missing the “In-App Purchases and Subscriptions” section entirely. Because of this, I cannot attach my subscriptions to the version, which is preventing me from submitting the app for review. Additionally, I also do not have the option to create a new version, so I can’t work around the issue by moving to 1.0.1. What happened before this: I uploaded a build (Build 24) Submitted the app for review Then removed the submission After that, the IAP section disappeared completely Since then, I cannot attach subscriptions or create a new version Current state: Subscriptions are created and show “Waiting for Review” New Build is attached to Version 1.0 All metadata and screenshots are complete “In-App Purchases and Subscriptions” section is missing “Add Version” option is not available What I’ve tried: Removing and re-adding the build Waiting for UI refresh/processing Contacting Apple Developer Support (case has been escalated for 6 days with no response) Impact: This is currently blocking my app launch because I would be rejected since the subscriptions are not linked, as I cannot submit my first subscription with the app. Questions: Has anyone experienced a missing IAP section after removing a submission? Is there any way to force reset the app version state from the developer side? Is this a known App Store Connect issue? Any help or suggestions would be greatly appreciated. Thanks in advance.

I am unable to submit updated subscription information for review (details below). Any help with what I might be doing wrong would be appreciated. Background We have had a macOS available on the App Store for about 2 years. I am currently adding new features that require a subscription. The app reviewer rejected the app because the subscription view The auto-renewable subscription promotes the free trial, introductory pricing, or introductory period for the subscription more clearly and conspicuously than the billed amount. I have updated the subscription view in the app, and I updated the screenshots in the metadata at App Store Connect. Unable to submit subscription update for review But now I cannot submit the updated subscription for review, with an error saying Your first auto-renewable subscription myst be submitted with a new app version. I have updated both the app version and build numbers, but I still get the same error. I completed deleted the subscriptions and subscription group and recreated them, but I am still get the same error. The attached image shows the error message. The "Submit for Review" button is disabled The warnings say it needs to be submitted with a new app version I have updated the app's version and build numbers Any idea what I am doing wrong?

Hello, My Apple Developer Program membership expired because the payment method on file was no longer valid. I am the Account Holder of an Organization account, but I have no option to renew my membership. There is no "Renew Membership" button anywhere: Apple Developer website Apple Developer app App Store Connect I also cannot accept the updated Apple Developer Program License Agreement because there is no option to review or accept it. I've already tried different browsers and devices with the same result. Has anyone experienced this issue? How was it resolved? Thank you.

I've hit several walls and this one I cannot get past.I don't understand how subscriptions work for an app I've published and am unable to get them live. I've followed the docs online about setting up a subscription, they've been submitted and approved, I've removed the base price for my app so people aren't gated from downloading it, yet, when a person downloads the app, they have full unrestricted access without having to subscribe. I don't get it. It seems to me that I may be responsible for building a gate in my own app that requires choosing a subscription. Is that right? If so, what is the purpose and use of the subscription the App Store Connect offers? If it is incorrect and Apple should actually be directing people to choose a subscription - what am I doing wrong? I think the hole in the wall cannot get any bigger from hitting my head with it at this point. I need help that isn't just "have you read this article?" or "follow the instructions on this help page". I've done it. I've read it. Yet here I am, pleading for some actual guidance on how to get this done.

I have created a set of offer codes for 1 year free for existing app users. The app use to be a one-time download and is now on a subscription model. When existing users try the code, a message indicating that they are not eligible for this offer pops up. I set up the offer code within the subscription group and indicated that it is for existing users. Any step I might be missing?

Hello! My app beFamily (version 1.0.0) is already live on the App Store and has active users. I have developed and completed the subscription functionality, but I have been unable to release it because my auto-renewable subscriptions have been stuck in review for more than a month. The current state is inconsistent: The subscription group "beFamily Plans" is marked as In Review. Both subscriptions remain Waiting for Review. There is no active App Review submission containing these subscriptions. My app version 1.0.1 is in Prepare for Submission, but the "In-App Purchases and Subscriptions" section is missing, preventing me from attaching the subscriptions to the app version. If I submit the app without them, it is rejected under Guideline 2.1(b) because the reviewer cannot locate the subscriptions. This issue has now been blocking my subscription launch for over a month, preventing my users from purchasing subscriptions and preventing my business from generating subscription revenue. I have already: Opened a Developer Support case. Submitted Feedback Assistant report FB23817386. Posted the issue on the Apple Developer Forums. Performed all recommended troubleshooting steps without success.

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.