This is my first time creating an app and submitting it for review to Apple. I build a SaaS management software that has 3 subscription tiers. while in the app, after the trial period they can upgrade to one of the 3 subscription models , if they do, it basically calls for a Stripe checkout where the subscriptions live. My app was rejected because of this I believe as stated by this message. 3.1.1 Business: Payments - In-App Purchase How do I fix this, of code around it.

Hi everyone, I’m currently experiencing an issue where my auto-renewable subscriptions are not loading during TestFlight and App Review. Setup: iOS app using StoreKit 2 + RevenueCat Subscriptions: Weekly Monthly Both are configured in: App Store Connect (attached to app version) RevenueCat (entitlement + offerings + packages) Current Status: Subscriptions show: “Waiting for Review” in App Store Connect Paid Apps Agreement is Active Banking + tax info is completed ⸻ What’s happening: In TestFlight → Paywall loads but: Products stay in loading state Prices never appear During App Review: Apple rejected with: “Unable to load plans” ⸻ Debug Info: RevenueCat logs confirm: Offerings are fetched successfully $rc_weekly and $rc_monthly packages exist However, StoreKit does not return product pricing in TestFlight ⸻ Question: Is this expected behavior when subscriptions are still in “Waiting for Review”? Or should products still fully load in sandbox/TestFlight even before approval? ⸻ What I’ve already verified: Subscriptions attached to app version ✅ Offerings configured in RevenueCat ✅ Product identifiers match exactly ✅ Using real device (not simulator) ✅ ⸻ Goal: I want to ensure: Subscriptions load correctly during App Review App is not rejected again for “Unable to load plans” Any guidance would be greatly appreciated 🙏

I would like to be able to price my app with different tiers with increasing number of increasing device installations ie smal 2 devices, family2-4, community - 100+ what is the best way to do this if it can be.

My InAppPurchases doesn't work because of, I assume, a country that's in my Entity Legal Information which is Russia. I no longer live in Russia and live in Serbia. This information is incorrect but it doesn't let me change it from Business section of App Store Connect. Changing the country is not available. Can you change it manually somehow or should I create a new developer account but in that case I have to pay another 100 dollars which I wouldn't want to do because I just recently purchased my current developer program. I assume that because my current address is set to Russia, it doesn't let me Sign the contract for InAppPurchases distribution. Help me to understand this, why is it that InAppPurchases are not available in my app.

I'm trying to create two new subscriptions for my app and I get a loader for quite awhile when I click on a subscription I'm trying to edit to add pricing info, introductory offer, etc. Once the subscription page finally loads, the Supscription Prices section shows this error: "An error has occurred. Try again later." It's showing 500's in the console logs too: /iris/v1/subscriptions/6764495098/prices?include=territory,subscriptionPricePoint&limit=500:1 Failed to load resource: the server responded with a status of 500 () I've tried clearing browser cache, restarting my browser/computer and trying other browsers..nothings working.

Dear all, This is my first post in this forum - and, in fact, my first app, too! I'm glad to be here, and thanks in advance for your help. I'm looking to offer an app for a one-time payment. I'd also like people to be able to try the app for a week. It seems that the "Pricing and Availability" section in App Store Connect is not the right place to configure this kind of offer. It does allow me to set a one-time price, but I cannot find a trial-period there (or am I missing something?) Two different strategies seem possible here: Using in-app-purchases: make the actual app free, but ask users after a week to buy a non-consumable IAP. The problem with that: I need to verify that the app has been installed for seven days ... even if it has been uninstalled at some point. Using subscriptions: There is a "free trial" option for subscriptions. But after that free trial, subscriptions are being payed periodically. I'd rather have the user only pay once for lifetime-access. Some apps seem to use strategy 1 - I believe the "Lap swim" app does. But still it seems like a bit of a hack - is there a more elegant way to achieve this?

After clicking on our subscription group name, app store connect is hanging and does not load. After a few minutes it will give an error. I've tried on Safari and Chrome and have tried on multiple computers. fter

I have been experiencing issues for over 24 hours with creating an App Store Connect subscription. I can make the subscription for my group, but when I scroll down to subscription pricing, it buffers for long and times out, resulting in this message: "An error has occurred. Try again later." No matter how many new subscriptions I create, only the subscription pricing section fails to load everytime.

Hello Apple Developer Support / StoreKit Team, We recently observed a behavior regarding the appAccountToken in App Store Server Notifications v2 that seems to completely contradict the official documentation. According to the Set App Account Token documentation: The same appAccountToken continues to apply to renewal transactions if the customer upgrades, downgrades, or cross-grades the subscription. However, we encountered a scenario where an active in-app crossgrade resulted in an updated/overwritten appAccountToken inside the subsequent JWSRenewalInfoDecodedPayload, despite our backend never calling the Set App Account Token REST API. Our Observation: A user subscribes to our 1-month plan (Product A). Apple generates an originalTransactionId bound to their initial appAccountToken (Token A). Later, a crossgrade to a 1-year plan (Product B) is initiated from within the app while the user is logged into a different account in our system (Token B), but using the same underlying Apple ID on the device. When the crossgrade takes effect at the next renewal date, we receive a DID_RENEW webhook. The Anomaly (See Attached Screenshots): Upon decoding the JWSRenewalInfoDecodedPayload from the webhook, we noticed that the appAccountToken had unexpectedly changed to the new token (Token B). As shown in the attached redacted screenshots: Screenshot 1 (Before/Original): JWSRenewalInfoDecodedPayload for Product 00001 shows the appAccountToken ending in ...e9a. Screenshot 2 (After Crossgrade): JWSRenewalInfoDecodedPayload for Product yearly_saver shows the appAccountToken has mutated to ending in ...507, even though the originalTransactionId remains exactly the same. To reiterate, our server did not call the POST /inApps/v1/subscriptions/appAccountToken/{originalTransactionId} endpoint to manually overwrite this token at any point. Our Questions: Is this the intended StoreKit 2 behavior? Does Apple automatically overwrite the base appAccountToken in the RenewalInfo if a new token is somehow associated during an active in-app crossgrade transaction? If this is intended, could the documentation be clarified? The current phrasing strongly suggests the token is permanently locked to the initial purchase and will never change during crossgrades unless the REST API is explicitly called. While this behavior is actually quite helpful for our backend to track multi-account users, we want to ensure we aren't relying on an undocumented bug that might be patched unexpectedly. Any insights from the StoreKit engineering team would be highly appreciated. Thank you!

I’m trying to manage pricing for auto-renewable subscriptions using the App Store Connect API (JWT). For In-App Purchases (non-consumable / consumable), I can: list price points set pricing using pricePointId However, for subscriptions: I can create subscription groups and subscriptions but I cannot find a clear way to: read current pricing (e.g. US price) set pricing via API I also tried using the asc-cli tool (v0.17.2), but it does not expose subscription pricing commands. Questions: Is subscription pricing accessible via the App Store Connect API? If yes, which endpoint should be used? If not, is this intentionally limited compared to IAP pricing? Any guidance or examples would be very helpful.

I’m experiencing an issue with subscriptions that behave differently between Xcode builds and TestFlight. Subscriptions work correctly when running the app directly from Xcode in a sandbox environment, but they do not work as expected when testing the same build through TestFlight. Has anyone experienced a similar issue with subscriptions working in Xcode but failing in TestFlight? Any guidance on what to check or debug would be appreciated. Additional details: iOS version: [ IOS 26] StoreKit version: [ StoreKit 2] TestFlight: When attempting to load the subscription products, the app returns “Product not found”. In some cases, it also shows the error “The subscription is unavailable in the current storefront”. This happens consistently in TestFlight, even though the same products load and work correctly when running the app from Xcode in the sandbox environment. Thanks

We had a work card attached to our developer's account. team ID 924RUYJZ34 dev ID 8771bf7b-31a9-4602-baae-02580fe5b6c4 Funds are debited from this card in other services, there are no problems with it, the amount in the account is sufficient. Our membership subscription did not renew automatically. The applications are blocked. We can't renew our subscription, there's no Renew button anywhere. There is no way to extend it on any device, web version, or anywhere else. We can't even cancel and re-arrange it, all the functions don't work. Please help us, how can we renew our subscription?!

The in-app subscription is failing to load. I've verified that all metadata and product IDs are correctly set up in App Store Connect and integrated into the source code.

Hello Support Team member - I hope you are having a good day. My app has been approved and I manually released it 8 hours ago. Currently users do not see the subscriptions available on the paywall, and the subscriptions do not show up under in-app purchases in the app store. When I look at my subscriptions in AppStoreConnect - they say "Missing Metadata". When I look inside the subscriptions - one of the two has a localization that is showing a status of "Prepare for Submission". The other subscription does not have a localization - and there is nothing within the subscription that has a yellow warning alert. How can I resolve this? Thank you much!

Hey my app subscriptions are currently in review whilst my app has been approved 2 times, i need this to be approved to start marketing it.

Hi, I’m having an issue where my auto-renewable subscriptions keep detaching from my app version after I submit the build in App Store Connect. Details: App ID: com.growthsync.app Platform: iOS (Capacitor build) Using auto-renewable subscriptions What’s happening: I attach all subscriptions to the app version under “In-App Purchases” Everything looks correct before submission After submitting, the subscriptions become detached or require localisation to be re-entered again This happens every time I resubmit Additional issue: Subscriptions are not working in TestFlight either It feels like they are not properly linked to the binary What I’ve already checked: Product IDs match exactly in code and App Store Connect Subscriptions are in the correct group All localisation fields are filled within character limits Products show as “Ready to Submit” before attaching I reattach them before every submission Questions: Why would subscriptions repeatedly detach after submission? Is this a known App Store Connect issue? Is there a specific order required when creating, localising, and attaching subscriptions? Could this be related to the binary not recognising the products? This is currently blocking release so any help would be appreciated. Thanks.

I added my first subscription to my app using StoreKit's SubscriptionStoreView. Everything worked as expected in the debug environment and also in TestFlight. So I submitted my app and subscriptions to App Store Connect, got everything Approved and released. After updating my app through App Store and checking the Subscription View, it just says "Subscription Unavailable. The subscription is unavailable in the current storefront." I waited around 3 days and still getting the same message. Now the very strange behavior starts. I went to App Store Connect, I made and edit to the subscription description, saved, removed the edit, saved, and submitted to review. 15 minutes later the subscriptions appear in my app and everything works as expected. After getting the edit approved, the Subscription View in my app again only showed the message "Subscription Unavailable. The subscription is unavailable in the current storefront." No user is able to see the subscriptions anymore, even though it worked as expected before the edit was approved. So I did the same as before. Again, make an edit to the subscription description, save, remove the edit, save, submit to review. 15 minutes later the subscriptions are again available in my app and it works as expected. This is definitely not the expected behavior and submitting the subscription edits every day is wasting the App Review Team's time as well as mine. I contacted Apple Developer Support but I didn't get any reply back (at least yet). I am not the only one experiencing this. I found a friend online who has the exact same issue, and is able to temporarily solve it by making an edit to the subscription description as well. So far it has been a huge headache, and we are losing customers this way. Please if anyone has experience with this problem, or has any suggestions, they will be greatly appreciated. Thank you so much, Tomas

I am trying to understand whether this is expected behavior or a configuration issue. My app has an auto-renewable subscription set up in App Store Connect. Current setup: Subscription type: Auto-Renewable Subscription Duration: 1 year Status: Approved Introductory offer: Free for the first week Introductory offer is active for the relevant storefront(s) Problem: On the App Store product page, the subscription only shows the normal price. There is no mention anywhere of the free 1-week trial. I tested this using a clean Apple ID that has never subscribed before and is in a region covered by the introductory offer. When trying to subscribe directly from the App Store flow (not the in-app paywall), the Apple purchase popup says “one-time payment”, even though this product is an auto-renewable subscription. What I thought would happen: The App Store page would show that eligible users get a free 1-week trial The purchase sheet would clearly indicate that this is a subscription, not a one-time purchase What I have already checked: Subscription is definitely created under Subscriptions, not as a non-consumable or one-time IAP Subscription status is Approved Introductory offer is active Product mapping appears correct Question: Is it normal that the App Store page does not mention the introductory free trial even for eligible users? Is it normal for the App Store purchase popup to say “one-time payment” for an auto-renewable subscription? Or does this suggest that something is misconfigured? If anyone has seen this before, I would appreciate guidance.

Hi everyone, Recently, a user purchased an annual subscription in one of my apps but hasn’t used the service much (I track usage through my backend). The user emailed me saying the purchase was made by mistake and had already submitted refund requests through the report portal. However, the requests were declined twice, and they can no longer submit another refund request. I suspect this may be because, in RevenueCat, I previously set the developer preference for refunds to “Prefer to decline,” due to users abusing AI trials. I have since changed the refund preference to “Prefer to grant,” but the user is no longer able to request a refund. May I know how I should proceed in this situation? I’ve already contacted Apple, but I’d appreciate hearing how others handle similar cases. Thanks!

I’m trying to find out whether anyone has seen this kind of App Store Connect issue remain unresolved for this long. This is for a first auto-renewable subscription. Timeline: Original support case opened: Feb 27, 2026 Support initially repeated the normal guidance that the first subscription must be submitted with the app version I explained that the issue was not the process itself, but a stuck review state On Mar 25, 2026, I was told the case had been escalated to the appropriate internal team Since then, I have sent follow-up emails asking for status / owner / ETA As of Apr 12, 2026 (KST), there has still been no meaningful update Current state in App Store Connect: App version 1.0.10 is still “Prepare for Submission” Previous 1.0.10 submissions show as “Deleted” There is no active app review submission for 1.0.10 The subscription previously showed “Waiting for Review” Now the subscription itself shows “In Review” But its localization still shows “Waiting for Review” So the state looks inconsistent: no active app review submission app version still draft subscription partially moved into review anyway At this point I’m not asking about the normal first-subscription submission flow. I already understand that. What I’m trying to understand is: Has anyone seen a case like this stay stuck for 6+ weeks? Has anyone had Apple say it was escalated internally and then go silent for weeks? Did Apple eventually fix it manually? Is this something that can remain stuck indefinitely unless the internal team intervenes? Any comparable experience would be helpful. Apple Support keeps saying that the internal team will follow up with me directly if they need anything. Is there anything I can do, or is all I can do just wait? Here are the relevant screenshots. App Review history: no active review for version 1.0.10, previous submissions are deleted Subscription page: the subscription itself is now “In Review” Localization on the same subscription page still shows “Waiting for Review” App version page: 1.0.10 is still “Prepare for Submission” There’s no subscription check.