Hi, I am planning to show the StoreKitError as alerts, I have corresponding custom Error so that I can show meaningful error messages. Reason I wanted to display error alert messages that describe the underlying error so that when in production and user faces this error I would be able to reason about the error and try to resolve the error in a app update or Appstore Connect change. If I display a generic error I wouldn't know the cause of the error, but is there is a security risk in display the following kind of messages? Proposed UI error messages: | Error | UI alert message | | ------------------------------------ | ----------------------------------------------- | | StoreKitError.notEntitled | App is not entitled to make this request. | | PurchaseError.invalidOfferSignature | Invalid offer signature. | Questions From a security / user perspective is it risky / wrong to show an error message like the ones pasted above? Or are there some errors I shouldn't explicitly state? Or is there a better / preferred approach?

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.

I am testing a StoreKit 2 non-consumable IAP through TestFlight. Product ID: com.metabolla.plus.lifetime Type: Non-Consumable Environment: TestFlight / Sandbox Transaction.currentEntitlements keeps returning an active entitlement for this product even after: configuring a Sandbox Apple Account clearing Sandbox Purchase History reinstalling the app rebooting the device Important detail: the first TestFlight purchase was completed before configuring the Sandbox Apple Account on the device. If I temporarily change the Product ID in code, the entitlement disappears, so the issue seems tied to the original Product ID/account/receipt. Question: Can a non-consumable TestFlight purchase made before Sandbox Apple Account configuration remain associated with the original TestFlight/Apple ID identity? Is there any supported way to clear this entitlement for testing?

I recently released an iOS app that includes banner ads through Google AdMob, and an in-app purchase to remove those ads. I created 500 offer codes in App Store Connect to be able to give out to people to get the in-app purchase for free. And I of course tried using one myself. However, it didn't work. At first, clicking on the offer code link failed to redeem anything. Eventually I was able to enter an offer code manually by going to App Store > My Photo > Redeem Code. But even after doing so, the ads weren't actually removed from my app. Now when I click the "Restore Purchases" link in my app, it says, "No Purchases Found. No previous ad removal purchase was found." But when I click the button to remove ads it says "Purchase Failed. The purchase could not be completed. Please try again." And if I try and redeem another code, it says, "Your code limit has been reached. You have already redeemed the maximum number of these codes per Apple Account." As the developer of this app, is there any way for me to make a in-app purchase (either with money or with an offer code) of my own app? Claude Code told me this: Apple prevents the developer Apple ID (the one that owns the app in App Store Connect) from purchasing or redeeming in-app purchases and offer codes for their own apps. But that response is AI and I always take its responses with a grain of salt. I asked it to cite its source, and it couldn't. Can anyone else who's developed iOS confirm or deny that this is true?

General: Forums topic: StoreKit Forums tag: In-App Purchase App Store Pathway Simple and safe In-App Purchases Auto-renewable subscriptions In-App Purchase documentation Getting started with In-App Purchase using StoreKit views documentation Supporting business model changes by using the app transaction documentation Testing at all stages of development with Xcode and the sandbox documentation App Store Server Notifications documentation App Store Server API documentation Simplifying your implementation by using the App Store Server Library documentation TN3185: Troubleshooting In-App Purchases availability in Xcode technote TN3186: Troubleshooting In-App Purchases availability in the sandbox technote TN3188: Troubleshooting In-App Purchases availability in the App Store technote Understanding StoreKit workflows sample code Implementing a store in your app using the StoreKit API sample code What’s new in StoreKit and In-App Purchase video

I'm testing IPhone and iPad Apps on Apple Silicon Macs. When I purchase In-app product in the app on Apple Silicon Mac, the payment receipt is not created, so the purchase fails. In console log, it says it doesn't have permission to write to the file. storekitagent [6913DE38_SK1] Error writing receipt (5095 bytes) to file:///Users/XXXX/Library/Containers/90FE2A60-9FDF-4ECF-848F-CE3D396322CA/Data/StoreKit/sandboxReceipt: Error Domain=NSCocoaErrorDomain Code=513 "You don’t have permission to save the file “sandboxReceipt” in the folder “StoreKit”" UserInfo={NSFilePath=/Users/XXXX/Library/Containers/90FE2A60-9FDF-4ECF-848F-CE3D396322CA/Data/StoreKit/sandboxReceipt, NSUnderlyingError=0x14202c920 {Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"}} The App is using Original API for In-App Purchase written in Objective-C. When I purchase in-app product, the app calls SKPaymentQueue::addPayment. And then it gets paymentQueue:updatedTransactions callback with SKPaymentTransactionStatePurchased. This means that the payment was successful. But the receipt is not created so I can't continue the after process. I'm testing with sandbox in-app purchase. I have tested several times and confirmed that on macOS Monterey 12.2 the receipt is created successfully, but on macOS Ventura 13.2 the receipt isn't created. I think there is something to do with macOS version. Does anyone have any solutions? Here is a very similar thread on apple developer forum. (And there too has no anwsers)  https://developer.apple.com/forums/thread/719505

Hello App Review team, I'm hoping you can help with what looks like an inconsistent product state on an auto-renewable subscription, rather than a normal review delay. Details: App ID: 6459996442 Subscription products: 6762844313, 6762844514, 6762844429, 6762844600 Submitted: April 21, 2026 (~1 month ago) Support case ID: 102899130307 The issue: the subscription product has shown "In Review" for over 31 days, while the product's own localization (the display name) shows "Waiting for Review" for that same product. The two statuses have diverged and neither has moved since. On top of that, the product is locked — I'm unable to edit or delete it while it's in this state. — It is currently attached to version 1.19.0 of the app, which is ready to release and has been approved by App Review. — It no longer appears in the In-App Purchases section of my current version submission, so I'm unable to re-attach or resubmit it. This matches a pattern other developers have described, where a subscription falls into a stuck state that can only be cleared from Apple's side. I'd prefer not to remove and resubmit, since I understand that can reset the queue without fixing the underlying state. Could you please: Confirm whether the products are genuinely in the review queue or in an inconsistent state, and If it is stuck, reset the products back to "Ready to Submit" or "Approved" so I can resubmit and release cleanly. I'm happy to provide any additional information you need. Thank you very much for your time and help. @App Review

Hi everyone, We develop the Ice Scream series and are introducing consumable IAPs (coin packs) for the first time in Ice Scream 1 and Ice Scream 2. The products are straightforward: coin packs that users can spend on boosters and additional content within the game. No expiration, clear value description, standard StoreKit implementation. Here's where things stand: Ice Scream 3: consumable IAPs submitted under the same model were approved without issues. Ice Scream 1: IAPs have been rejected multiple times with no specific feedback indicating what needs to be fixed. Ice Scream 2: after multiple rejections, the IAPs have been sitting in "In Review" status for over a week with no update. With each rejection we have provided detailed review notes including step-by-step instructions to reach the Shop (which requires completing a short onboarding tutorial as a new user) and video walkthroughs showing the full purchase flow for both new and returning users. Despite this, we keep getting rejections or no response at all. We have also submitted an appeal form requesting specific clarification, but have not received any reply. A few questions: Has anyone experienced a similar situation with consumable IAPs being repeatedly rejected without actionable feedback? Is there anything specific Apple checks for consumable IAPs beyond what is covered in Guideline 3.1.1 that we might be missing? Is there any other escalation path beyond the appeal form when a review appears to be stalled? Any help or insight would be greatly appreciated. Thanks!

To the App Review and Developer Support Teams, I am writing this post to bring an ongoing issue to your attention, as standard support channels have failed to provide any resolution or clear communication. Issue Summary: We are introducing consumable IAPs (coin packs) for the first time in Ice Scream 1 and Ice Scream 2. Both apps have been reviewed and approved, however their associated IAPs remain blocked. Despite multiple resubmissions with detailed review notes and video walkthroughs, the IAPs have been repeatedly rejected without specific or actionable feedback. The equivalent IAPs submitted for Ice Scream 3, using the exact same implementation and business model, have already been approved by the App Review team. Current status per app: Ice Scream 1: App approved. IAPs have been repeatedly rejected with no specific feedback indicating what needs to be corrected. Ice Scream 2: App approved. After multiple rejections, the IAPs have been stuck in "In Review" status for over a week with no update or response. Lack of Communication: We have opened support cases for both titles and have received no response or actionable feedback. The lack of synchronization between the App Review and Support teams is causing significant operational disruptions and is directly impacting our business. Impact: Not having the monetization features active in both titles is causing direct financial loss and preventing our users from accessing content they need. Request: We request an immediate update on the status of these IAPs and clarification on why the support cases remain unanswered. We are looking for a direct escalation or a response from an Apple representative who can resolve this situation. Related apps and support cases: Ice Scream 1: Scary Horror — App ID: 1480827449 — Case ID: 102902530872 Ice Scream 2: Scary Horror — App ID: 1488473484 — Case ID: 102902529670 I look forward to a prompt resolution. Sincerely, Maria Laskurain Keplerians Horror Mobile Games

I'm trying to submit a first-time In-App Purchase together with a new version of my macOS app, but App Store Connect doesn't seem to provide a way to do this. Setup: macOS app (Bundle ID: de.andreasmaser.Screenshots) Marketing version: 1.2, Build 1 (uploaded, processed, attached to version) IAP "Screenshots Pro" (Product ID: de.andreasmaser.Screenshots.pro) is fully configured: status "Waiting for Review", App Review screenshot present, both English + German localizations, pricing set Previous 1.1 submission was rejected under Guideline 2.1(b) because "the associated In-App Purchase products have not been submitted for review" Per Apple's documentation (https://developer.apple.com/help/app-store-connect/manage-submissions-to-app-review/submit-an-in-app-purchase), step 3 says: "On the right, scroll down to the In-App Purchases and Subscriptions section." The problem: This section does not exist on the macOS app version page. I scrolled through the entire page; the sections are: App Previews & Screenshots → Promotional Text → Description → Keywords → URLs/Version/Copyright → Build → Added Content → Game Center → App Review Information → App Sandbox Information → Version Release. There is no "In-App Purchases and Subscriptions" section anywhere. What I've tried: Both Version 1.1 and a fresh Version 1.2 with a freshly-uploaded build Cancelling/withdrawing the previous submission and starting a new draft Editing the IAP and re-saving (no status change) The IAP's "Submit for Review" button stays greyed out on the IAP page The submission draft panel only shows the app version, with no "+" button to add IAPs The "Submission Drafts" floating button on the IAP detail page just opens the same panel with only the app Questions: Does the "In-App Purchases and Subscriptions" section appear for macOS apps under specific conditions I'm missing? Is there a different workflow for attaching first-time IAPs on macOS apps vs. iOS apps? Is this a known App Store Connect bug, and what's the recommended workaround? Any guidance is greatly appreciated — I've been blocked on this re-submission since yesterday.

The app idea is pretty simple, we manage small physical events through ticketing and QRs for entry. However the app reviewer insists that they are “digital” invitations and therefore mist use Apple IAP. To my understanding, digital products, services and consumables inside the app are what require Apple IAP. please correct me or guide me on what is the correct understanding. my reply to the review: Multiline requesting reconsideration under >Guideline 3.1.3(a). Xxx is a service for organizing physical events >(weddings, birthdays, corporate >gatherings) held at real venues in >xxx. The per-guest fee charged >through the app covers: Sending physical-event invitations >via xxx (the standard communication channel for event >organizers in xxx) RSVP tracking for physical attendance planning (Premium tier) >Per-guest QR codes used by gate staff to admit guests to the physical >venue The end deliverable is >admission to and management of a >real-world, in-person event. This is >materially identical to ticketing apps >(Eventbrite, Ticketmaster, ...), >reservation deposits (OpenTable, >...), and on-demand service apps >(Uber, DoorDash, ...) - all of which >use external payment processing >for physical services consumed >outside the app, per 3.1.3(a). The app does not sell digital >content or services consumed >within the app itself. No streaming >media, no in-app credit, no >subscription to in-app functionality. >The user pays only to enable real->world event logistics. BlockQuote Their reply is: Multiline Guideline 3.1.1 - Business - >Payments - In-App Purchase Issue Description We noticed that the app includes or >accesses paid digital content, >services, or functionality by means >other than In-App Purchase, which >is not appropriate for the App Store. >Specifically: The digital invitation can be >purchased in the app using >payment mechanisms other than >In-App Purchase. Apps on the United States >storefront may link out to the >default browser, using buttons, >external links, or other calls to >action, for payment mechanisms >other than in-app purchase. … BlockQuote

To the App Review and Developer Support Teams, I am writing this post to bring an ongoing and critical issue to your attention, as standard support channels have failed to provide any resolution or clear communication. Issue Summary: My application’s last two versions have been successfully reviewed and approved. However, three In-App Purchases remain stuck in the review process. Lack of Communication: I have opened several support cases regarding this delay, yet I have received no response or actionable feedback. The lack of synchronization between the App Review and Support teams is causing significant operational disruptions. The current communication gap and the slow response times are directly impacting my business and user experience. Impact: It is unacceptable to have a live application with "Pending" monetization features for such an extended period. This delay is causing financial loss and preventing my users from accessing the services they need. Request: I request an immediate update on the status of these IAPs and a clarification on why the support cases remain unanswered. I am looking for a direct escalation or a response from an Apple representative who can resolve this bottleneck. App ID: 6744109858 Related Case IDs: 102900240277 102896872200 102896192600 I look forward to a prompt resolution. Sincerely

To the App Store Review and Developer Support Teams, I am reaching out via this forum as a last resort because my communication through standard support channels has been entirely ignored, causing significant disruption to my business. The Timeline of the Issue: May 16: I submitted 5 In-App Purchases (IAPs) with version 2.0. While 2 were approved, 3 were rejected. I immediately resubmitted them for review on the same day. May 21: Version 2.0.1 was approved, but the 3 IAPs remained "Under Review." May 25: Version 2.0.2 was approved. I specifically included a Note to the Reviewer explaining that the IAPs were stuck, but this was completely disregarded. The Bottleneck: It has been 12 days since the resubmission. I have opened multiple support cases to resolve this, yet I have received no response or actionable feedback from the support team. This lack of communication and the extreme delay in IAP synchronization is creating a broken experience for my users and causing financial loss. Reference Information: App ID: 6744109858 Current App Version: 2.0.2 Related Case IDs: 102900240277, 102896872200, 102896192600 I request an immediate investigation into why these IAPs are stuck and why my support cases are being ignored. I am looking for a direct resolution from an Apple representative. Regards,

My Non-Consumable IAP was rejected with Guideline 3.1.1 and now has status ‘Developer Action Required’. The problem: On the version page in App Store Connect, the ‘In-App Purchases and Subscriptions’ section does not appear at the bottom. I cannot link the IAP to a new version submission. Every time I submit a new binary, Apple approves the app version but rejects the IAP afterward — even though I have no way to attach it to the version in the first place. This seems to be a circular issue: the IAP doesn’t appear on the version page because of its current status, but the only way to fix the status is to submit it with a new version. Has anyone experienced this and found a solution? Any help appreciated!​​​​​​​​​​​​​​​​

Hello everyone, I'm facing a very frustrating situation with App Review for my indie app, CoffeePomodoro, and I'm hoping someone here or an Apple engineer can help shed some light on how to escalate and resolve this. My recent update (Version 1.3.1, Submission ID: 59763b52-7c14-4b27-a2cf-2799d2bafe35) was rejected under Guideline 3.1.1 - In-App Purchase. The rejection message states: "We found that the app includes a feature to restore previously purchased In-App Purchase products by entering the user's Apple Account and password. However, In-App Purchases cannot be restored in this manner." The Reality: There is absolutely zero custom UI, form, or TextField in my app that asks for an Apple ID or password. When a user taps "Restore Purchases", the app simply calls Purchases.shared.restorePurchases() via the RevenueCat SDK, which directly wraps Apple's native SKPaymentQueue.restoreCompletedTransactions(). The credential prompt the reviewer saw is the native iOS system-level authentication dialog that appears automatically in the sandbox/TestFlight environment. This usually happens if the device or simulator being used for the review doesn't have an active Sandbox Apple ID already logged in. I have explained this in the App Store Connect Resolution Center. I provided screen recordings showing it's the system dialog, and I attached code snippets proving the app only calls native APIs. Unfortunately, my explanations seem to be ignored, and I keep facing the same roadblock. It feels like the reviewers are mistaking their own OS's native prompt for a custom credential-harvesting screen. Meanwhile, my users are waiting for this update to resolve their subscription issues, and I am stuck in a rejection loop for using Apple's own native API exactly as intended. Has anyone else experienced this specific misunderstanding by the review team? How can I escalate this so someone actually reviews the screen recording and code snippets I provided? Thank you for your time.

Hello, My Paid Apps Agreement has been stuck in "In Process" status since May 16, 2026 — now 9 days with no resolution. I have received no emails from Apple regarding this The agreement has not been rejected The system does not allow me to make any edits I have contacted Apple Developer Support twice with no real response

Hello, I am experiencing an App Store Connect issue where my In-App Purchases are not attaching to the app review submission. Current situation: The IAP products are fully configured. Status is currently "Waiting for Review". Product IDs match the app code correctly. Sandbox testing works correctly. However, the app version page does not display the "In-App Purchases and Subscriptions" section at all. App Review repeatedly responds that they cannot locate the IAPs during review. It appears the IAP submission linkage between the binary and App Store Connect may be corrupted or missing. App: Phantom Spy I would appreciate any guidance or escalation assistance. Thank you.

To the Apple Review and Developer Support Teams, I am writing to request guidance and assistance regarding a persistent rejection my React Native application is facing under Guideline 2.1 - Performance (In-App Purchases). My app has been rejected multiple times with the following specific note: "The In-App Purchase products in the app still exhibited one or more bugs which create a poor user experience. Specifically, the subscription screen failed to load any subscription plans. Review the details and resources below to troubleshoot this issue." The screenshot provided by the review team shows a completely black screen where our paywall options are intended to populate, indicating that the product array is returning completely empty during the review process. The Dilemma: We are completely unable to reproduce this behavior on our end. Everything functions flawlessly within our TestFlight builds across multiple physical test devices and various sandbox tester accounts. On TestFlight, the paywall renders instantly, local pricing fetches immediately via SKProductsRequest, and test transactions process without a single error. Our Current Implementation & Verification: Product Status: All subscription products are explicitly marked as "Waiting for Review" in App Store Connect with one In-App product Rejected for not being attached with a bin but I've since submitted the app once again. All the subscriptions and the in-app product have been actively attached to this specific app submission version. Agreements: The Paid Apps Agreement is active, signed, and fully up to date within our Agreements, Tax, and Banking configurations. Identifiers: We have strictly verified that the hardcoded product identifiers in our React Native codebase match the App Store Connect product IDs exactly. Because this error only occurs within the App Review environment and never in TestFlight or local sandboxes, we are at a loss for how to debug or resolve this issue. Could the App Review team or the Developer Support technical team please clarify if there is a known environment mismatch, storefront routing discrepancy, or specific network configuration (such as IPv6 handling in the review sandbox) that would cause production-ready StoreKit products to return an empty array exclusively to the reviewer? Any direct guidance, logs, or steps on how we can successfully surface our plans to your review team would be deeply appreciated. Review Environment Submission ID: 5a35279c-1621-4972-b6c6-7c1fb202b2f0 Review date: May 20, 2026 Review Device: iPad Air 11-inch (M3) Version reviewed: 1.0.2 (8) Thank you for your time and assistance.

I'm hoping someone from the App Review team can help. My App ID: 6743341470 is Ready for Distribution, but both auto-renewable subscriptions have been stuck in "In Review" since May 10 with no update. Subscriptions: Subscription Group ID: 22039292 Account status: Paid Apps Agreement: Active Banking and tax: Complete Localization: Approved (Since 11 May) Resolution Center: No outstanding items What I've tried: Apple Developer Support case 20000114086909 — escalated thrice, support confirmed nothing is concerning but no movement. All they said was wait with no definite timeline. This is my first app and these subscriptions are blocking my launch. Any help from the App Review team would be greatly appreciated.

Hello, I am trying to ship the first auto-renewable subscription for my iOS app and I am facing what seems to be a workflow / availability issue involving App Store Connect and TestFlight. Product ID: seka_premium_yearly_ Current situation: The subscription exists in App Store Connect. Its status remains “Waiting for Review”. The subscription page says that the first subscription must be submitted with a new app version and attached through the “In-App Purchases and Subscriptions” section on the app version page. 4. However, this section does not appear on my iOS app version page in App Store Connect. 5. In TestFlight, when tapping “Subscribe”, the app shows: “The offer is not available yet. Please try again in a moment.” Additional context: Paid Apps Agreement is active The app uses expo-iap The product ID configured in the app is seka_premium_yearly_ We are not restricting access by storefront, region, or device configuration Sandbox testing has been attempted, but the issue remains reproducible in TestFlight Question: Is it expected that the subscription is unavailable in TestFlight while the first subscription is still in “Waiting for Review”? Does the missing “In-App Purchases and Subscriptions” section on the app version page indicate an App Store Connect issue? Has anyone encountered this specific first-subscription workflow problem? Any guidance would be appreciated.