Hi, we are trying to have our app approved since 2 weeks now with the subscription attached, now we are in a very strange situation where the app is approved but the subscription is still "Waiting for review" and we don't understand how is possible considering the app binary have the subscription flow inside. Can you help us? We also asked an expedited review today for the app due to business needs and just the app is approved without the subscription. The app is "Hey Clary" ID: 6752716476 Thanks

When my app tries to access a subscription, StoreKit's products(for:) always returns zero results. Similarly, SubscriptionStoreView always shows "Subscription Unavailable" followed by "The subscription is unavailable in the current storefront". The app is a watch-only app (no iPhone companion app). The app and the subscription product were each approved in App Store Connect over two weeks ago. The problem occurs when the app is installed from TestFlight, when the app is installed from the App Store (production), and when run in the Xcode debugger. The only time the app successfully accesses the subscription when simulating it in Xcode with a .storekit file. How should my app access the subscription? Repro: App Store bundle ID: com.toolsay.hoopref Phone app target (unused) bundle ID: com.toolsay.hoopref Watch app bundle ID: com.toolsay.hoopref.watchapp Subscription product ID: com.toolsay.hoopref.pro.annual Subscription availability: All countries and regions App Store listing let products = try await Product.products(for: ["com.toolsay.hoopref.pro.annual"]) products.count is 0.

We are developing a platform (Ferve) where users subscribe to individual artists to access exclusive content. We use a user-centric remuneration model: each artist has an independent income pool, and funds from a specific subscription must be attributed solely to that artist. We have two critical challenges regarding our integration: Granular Financial Reporting for User-Centric Payouts As the Merchant of Record, Apple provides aggregate Financial Reports. However, these reports do not provide a breakdown of taxes, commissions, or exact exchange rates used for individual transactionId records. Though we can keep records of each transaction in our database, thus linking them with which artist they belong to, we are unable to collect fees/taxes applied to each individual transaction. Because our payouts are artist-specific, we need to deduct the exact regional taxes and Apple commissions from each transaction to calculate the artist's due balance. Currently, we can only see the final consolidated balance in BRL (Brazilian Reals) at the end of the month. Is there an API or report that provides the net proceeds and tax breakdown per transaction ID? How can we retrieve the exact exchange rate applied to foreign currency sales (e.g., EUR to BRL) before the final consolidation? Supporting Multiple Concurrent Subscriptions Our current App Store Connect configuration uses a single 'Subscription Group' for all artist 'Clubs' since they share the same price points. However, we have found that users cannot subscribe to more than one product within the same group simultaneously (the App Store treats this as an upgrade/downgrade). On our platform, a user must be able to subscribe to Artist A and Artist B at the same time. What is the recommended architecture for this? Should we dynamically create a unique Subscription Group for every artist onboarded to our platform? If we use unique groups, is there a limit to the number of Subscription Groups one app can have? We appreciate the help, Ferve

My subscriptions have a status of "developer action needed", but when I attempt to save an edit I receive an error "There was an error with editing your App Store localization. Try again later." Refreshing the page doesn't change anything. I have 2 localizations, one of them has a status of "waiting for review". I am unable to attach the subscription group to my binary as the ready to submit status required for the In-App Purchases and Subscription section to become active is not achievable. I have emailed and received no response. My app has been approved and is live on the app store with subscriptions that do not function. I understand I made an error, this is my first time releasing on the app store.

**To offer apps or other in-app purchases, you must update your legal entity information prior to signing the Paid Apps Agreement. Edit Legal entity ** Hello everyone, i have for days and weeks tried to change this so i can update my address, but i cannot change it by my own. And all i see is message above Does anyone know exactly how long it takes to be updated by apple support? what other alternatives there to sign up for business agreements so i can not loose much time ? Thanks

I’m submitting the first auto-renewable subscriptions for my iOS app. Apple’s documentation says the subscriptions should be selectable from the app version page under ‘In-App Purchases and Subscriptions,’ but that section does not appear on my version page even though the build is attached and the subscriptions exist in App Store Connect. The subscriptions currently show ‘Waiting for Review.’ Please advise how to attach the subscriptions to the app version so I can complete first-time subscription submission.

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.

We are implementing promo/offer codes for our iOS app’s subscription in-app purchases and have several technical questions regarding validation, receipt data, and integration. Could you please provide guidance on the following points? Testing/Validating Custom Codes Without Production Release: How can we validate custom promo/offer codes in a non-production environment? Current documentation indicates promo codes only work in production, requiring app submission and future release date setup for testing. Receipt Data for Redeemed Codes: The receipt currently includes only offer_code_ref_name, not the exact redeemed code (e.g., “ABC123”) entered by the user. Is there a way to retrieve the specific offer code used via receipts, App Store Server API, or other endpoints? Server-Side Validation Best Practices: What are the recommended best practices for server-side validation of offer codes, including using App Store Server API for transaction verification? Passing appAccountToken for Coupons: How can we pass an appAccountToken when users redeem coupon/offer codes (e.g., via presentOfferCodeRedeemSheet or redemption flows)? StoreKit purchase options support it for regular purchases but not redemption sheets. Callbacks on Coupon Redemption: Is there a client-side callback or notification (e.g., via updatedTransactions or StoreKit observers) when a user successfully redeems a coupon code in the app? Server notifications are received, but app-side feedback appears unreliable.

Thanks!

Hello, We are facing an issue with In-App Purchases (subscriptions) in two iOS apps built with React Native + react-native-iap. Issue Some users receive the error: E_CONNECTION_CLOSED during the purchase flow. However: The payment is successfully deducted via the App Store. The subscription appears in the user's Apple ID subscription list. But on our side: The app does not receive the StoreKit transaction callback No receipt or transaction ID is delivered Our backend cannot validate the purchase. Restore Purchases When affected users try Restore Purchases, StoreKit returns: No purchases found even though the subscription is visible in their Apple ID. Most affected users are from India, and many payments are made via UPI through App Store billing. Has anyone experienced a case where: *the user is charged *the subscription exists in Apple ID *but StoreKit never returns the transaction or receipt? Any suggestions on how to recover these transactions would be greatly appreciated. Thanks!

Hello, My app TouCal: AI Calorie Tracker seems to be stuck in the App Review process and I’m trying to understand if something might be wrong with the submission. App ID (Apple ID): 6698870692 Timeline: First submission: March 9 Since then the app has been in “Waiting for Review” for 4 days (as of March 13) Normally my app reviews are approved within 1–2 days, so this delay seems unusual. Please help review this submission as soon as possible! My users are currently facing a bug that should have been fixed in this version. Any guidance would be greatly appreciated. Thank you.

Hello, We are facing an issue with In-App Purchases (subscriptions) in two iOS apps built with React Native + react-native-iap. Issue Some users receive the error: E_CONNECTION_CLOSED during the purchase flow. However: The payment is successfully deducted via the App Store. The subscription appears in the user's Apple ID subscription list. But on our side: The app does not receive the StoreKit transaction callback No receipt or transaction ID is delivered Our backend cannot validate the purchase. Restore Purchases When affected users try Restore Purchases, StoreKit returns: No purchases found even though the subscription is visible in their Apple ID. Most affected users are from India, and many payments are made via UPI through App Store billing. Has anyone experienced a case where: the user is charged the subscription exists in Apple ID but StoreKit never returns the transaction or receipt? Any suggestions on how to recover these transactions would be greatly appreciated. Thanks!

Another Limbo with IAP. I'm genuinely baffled by this. My app " Tapix - AI Writing Keyboard " was reviewed, approved, and is currently live and downloadable on the App Store. Great except the auto-renewable subscription that I submitted at the same time is STILL sitting in "Waiting for Review." Let me spell out what this means for real users: A user finds my app on the App Store They download it They open it and hit the subscription screen Nothing works. They can't subscribe. The core functionality is locked behind a paywall that Apple hasn't approved yet. They think the app is broken They leave a 1-star review and delete it. This is an absolutely terrible first impression and there's nothing I can do about it from my side. Everything is configured correctly metadata, pricing, review screenshots, subscription group, product IDs all of it. The app was approved. The subscription just... wasn't. How is it possible that Apple approves and distributes an app but leaves the IAP that the app literally depends on in limbo? Shouldn't these be reviewed together? Why would you release an app to users in a state where its core monetization is non-functional? Every hour this sits in "Waiting for Review" is real damage and a launch that's essentially sabotaged through no fault of my own. I'm asking for any guidance on how to escalate this. This needs urgent attention. Thank you. App Name - Tapix AI Keyboard

Hello, I am investigating a case where two different transaction IDs appear to refer to the same purchase, and I would like clarification on whether this behavior is expected. Additional context StoreKit version: StoreKit 1 (SKPaymentTransaction) Environment: Production Product type: Auto-renewable subscription Transaction sources The values are obtained from the following APIs: transaction_id from SKPaymentTransaction https://developer.apple.com/documentation/storekit/skpaymentqueue receipt_data from the App Store receipt https://developer.apple.com/documentation/foundation/bundle/appstorereceipturl Observed behavior After an In-App Purchase completes, the app receives: a transaction_id from SKPaymentTransaction the corresponding receipt_data for the purchase When inspecting the receipt, the transaction_id inside latest_receipt_info differs from the transaction_id received directly from the purchase transaction. For clarity: A = transaction_id received from the purchase flow (SKPaymentTransaction) A' = transaction_id found in receipt_data.latest_receipt_info The two values are different, but they differ only by 1. Additional observation The original_transaction_id for A and A' is identical, which suggests that both transaction IDs belong to the same subscription purchase chain. Pattern observation on the ID difference We have observed that the difference between A and A' is consistently exactly 1 (i.e., A' = A + 1) across multiple transactions, not just a single case. This appears to be a reproducible pattern rather than a coincidence. This observation raises an additional question (Question 6 below). API verification When calling: GET /inApps/v1/transactions/{transactionId} Both A and A' return what appears to be the same purchase record. The response data is effectively identical except for the transactionId field. However, when calling: GET /inApps/v2/history/{transactionId} A does not appear in the transaction history only A' appears in the history response Questions If A does not appear in transaction history, where does this transaction ID originate from? Why does Get Transaction Info (/inApps/v1/transactions/{transactionId}) return a valid response for A even though it is not present in the transaction history? Why do A and A' both resolve to what appears to be the same purchase? In this situation, which transaction ID should be treated as the canonical transaction ID for server-side validation? Is this difference related to how StoreKit 1 (SKPaymentTransaction) and the App Store Server API represent transactions? Is the consistent off-by-one difference between the transaction_id from SKPaymentTransaction and the one recorded in latest_receipt_info an intentional behavior of StoreKit 1's internal transaction ID assignment? Specifically, we are wondering whether StoreKit 1 applies some form of internal offset when delivering the transaction ID to the client, while the App Store server records a different (adjacent) ID in the receipt. If so, is this documented anywhere? Note We are currently in the process of migrating to StoreKit 2, but this behavior was observed while investigating our existing StoreKit 1 implementation. Any clarification would help us better understand the correct transaction model during the migration.

hello this is my first time putting an app on subscriptions in Storekit, I believe I did everything correctly, from my paywall to everything in Xcode and apple connect, including agreements and sandbox, my sandbox in app purchase worked on all my subscriptions but when I my app was live in store it said purchase could not be made, basically apple wasn't returning what it needs to. my subsections are all approved and say active including my subscription group. bundle ID matches everywhere and so does product id, does anyone know what could possibly be the issue? and how to fix, I would really appreciate any insight.

Hello, I’m trying to understand which Apple subscription offer best fits a coupon-like flow in our app. Our ideal case is a 1-month Pro benefit that users can trigger inside the app: without entering a code manually possibly more than once over time then continue into a normal paid auto-renewable subscription Ideally, this would work for new, existing, and lapsed users, and if possible, even for users who are already actively subscribed (though that part is not required). From the docs, I understand that: Offer Codes require redemption Promotional Offers are for existing or previously subscribed users Introductory Offers are for new eligible users Win-Back Offers are for lapsed subscribers So my questions are: Is there any Apple-supported way to do this without manual code entry? Can the same user receive this kind of 1-month benefit multiple times over time? Which offer type is the closest fit? Is this use case partly incompatible with Apple’s subscription system? Thanks.

I’m working on a Flutter application that implements subscriptions using in-app purchases (IAP). I currently have two apps under the same developer account: One for staging One for production In App A (staging), I successfully created a monthly subscription with the product ID: rc_1299_monthly However, when I try to create a subscription with the same product ID (rc_1299_monthly) in App B (production), I encounter the following error: "The Product ID you entered is already being used by another subscription." My understanding was that product IDs are scoped per app, but this error suggests there may be account-level constraints. Has anyone encountered this before? Is it required to use unique product IDs across all apps under the same account, or is there a recommended approach for handling staging vs production setups? Any clarification or best practices would be appreciated.

I am submitting a new app, so the subscription has to be submitted as part of the overall app review at first, I can't submit it directly on its own. I didn't know this at first, and submitted the subscription directly. It obviously got rejected with the status "developer action needed". Now no matter what I change I cannot seem to get the status to update from "Developer Action Needed" to a more favorable status. This is obviously a problem because until I can get the status to update, I cannot attach it to submit with my app. Any ideas on how to get the status on my subscription to update to "Ready to submit" so that I can attach it with my binary and submit it with my overall app submission?

Currently I have an app which is completely free for all the users, I might have future versions where I will introduce paid version, where I will surely use Apple IAP and Revenue CAT. How should I clarify this to App store? Should I tell only what I am doing today, or also tell what I will do in future and keep Apple IAP in my conversation?

I've published my app with subscriptions (app changed from paid to subscription model). I've have succesfully pass review process and app was published to App Store without subscription store, so no one can buy app (still working as paid, but will expire in few days forcing users to subscribe). I want to attach subscriptions to new build, but I can't - there are no options mentioned in documentation. I'm stuck. There is no any contact point to review team. I've created 3 cases, nobody reads them (oldest 3 weeks). The whole approval process looks broken, Apple team shouldn't approve app with subscriptions without subscriptions added to review. I must immediately publish my app with critical fixes, but I can't. I am devastated, i don't know what to do...