An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

App Store Connect displays the In-App Purchases and Subscriptions section on your app's version page when your app has an In-App Purchase or subscription with a Ready to Submit status. To locate the In-App Purchases and Subscriptions section: In Apps, select the app you want to view. In the sidebar, select the app version. On the version page, scroll down to the In-App Purchases and Subscriptions section. For more information, see Submit an In-App Purchase.

I'm the sole Director, Shareholder, and PSC of a UK-registered limited company (Companies House verified, D-U-N-S number obtained), enrolling in the Apple Developer Program as an Organization. Apple requested additional verification documents to confirm my identity and association with the entity. On 17/08/2026, I submitted a complete package: Government-issued passport Certificate of Incorporation (UK Companies House) Official Companies House officer record showing my role as Active Director, with "Verification requirements complete" A signed declaration confirming my authority as sole Director/Shareholder/PSC, and explaining that as a newly incorporated company with no employees other than myself, no separate employment reference is available Apple confirmed receipt of these documents by email. Since then: I followed up via support ticket on 27/08/2026 — Case ID: 20000149144709 No response as of today, several business days later Enrollment ID: 6HDSQCQU98 Could someone from the Apple Developer Relations team please advise on the status of this case, or point me to the correct escalation path? Happy to provide any further information needed to resolve this.

Hi, I am seeing "Waiting for Review" for the past 10 hours, and I do not know why it is taking so long, some of my versions get approved quickly some versions taking a long time. General Information Bundle ID: com.salesforce.pronto.fooddelivery.ProntoFoodDeliveryApp SKU: com.salesforce.pronto.fooddelivery.ProntoFoodDeliveryApp Apple ID: 6756443629 App Name: ProntoFoodDeliveryApp Bundle Short Version String: 1.0.6 Bundle Version String: 2 Please let me know if you need any additional information. My testers are waiting to test the new features. Thank you

Hi everyone, I am preparing to publish my React Native mobile application called ScoreVerse to the App Store and would like clarification regarding developer account requirements (Individual vs. Organization). App Overview & Core Features: Sports Turf & Ground Booking: Users can browse local turf grounds, check available time slots, and book turf sessions for physical sports activities (football, cricket, etc.). Tournament Management & Live Scoring: Organizing local matches/tournaments, tracking live scores, team management, and schedules. Payments: Payments are processed via a third-party gateway (Razorpay) strictly for real-world physical turf bookings and local tournament entry fees (physical services / events, in compliance with Guideline 3.1.3(e) / 3.1.5). User & Admin Roles: Ground owners/managers manage their own turf availability and slots, while players/users book slots and view tournament stats. My Questions: Individual vs. Organization Account: Does Apple App Store Review require an Organization Account (D-U-N-S registered legal entity) for this type of sports turf booking and tournament platform, or is an Individual Developer Account sufficient for initial release? Third-Party Payment Gateway Usage: Since payments are exclusively for physical services/turf rentals in the real world (and not for digital consumable goods or in-app unlocks), will having an Individual Account cause any review rejections under Guideline 5.1.1 / 3.1.3(e)? Account Migration: If we launch initially under an Individual Account, how seamless is the process to convert/transfer the app and account to an Organization Account later once company registration is complete? Any insights from developers with similar booking/sports platforms or App Review moderators would be greatly appreciated! Thank you!

hi all Hi all, ClubDraw (App ID: 6761770554) has been in review for 4+ months across 6 submission cycles. Resubmitted 18th August with a formal App Review Board appeal the same day - 16 days with no response. The core issue: Apple are applying Guideline 5.3.4 (gambling licence) to a B2B SaaS platform. ClubDraw enables UK grassroots sports clubs to run their own weekly lotto draws. The clubs are the licensed operators under the Gambling Act 2005. We charge a flat subscription fee only - all draw revenue goes directly to the club. We are not a lottery operator. ClubZap (App Store ID: 1004097048) operates an identical model and is live on the App Store. We've cited this in every response. ClubDraw is also live on Google Play UK without any licence requirement. Guideline 3.1.1 has also been raised - Apple say our club admin subscription must use IAP. It's a B2B SaaS fee charged to club administrators, not a consumer purchase. All other guidelines (2.1, 5.2.1) are fully resolved. The problem: App Review Board appeal not acknowledged. Message thread locked in App Store Connect. Direct emails bounce. Has anyone successfully escalated past the App Review Board? Any advice welcome. Thanks in advance.

We have 5 consumable in-app purchase products (Product IDs: localshadows_support_099, _499, _999, _2499, _4999) currently in "Prepare for Submission" status. Our app's first version (1.0) has also not yet been submitted for App Review. Question: Does sandbox testing of these consumable IAPs require the app to be fully approved through App Review first, or is it sufficient for the products to be attached to a version that has been submitted (even if still pending review)? What we've tried: We're using react-native-iap v16.4.1 for a real native StoreKit 2 purchase flow (not RevenueCat, which was masking this issue via its Test Store simulation mode). Calling fetchProducts() for these SKUs returns an empty array, and calling requestPurchase() for them results in an indefinite hang with no error. We want to complete sandbox testing before deciding on our actual App Review submission timeline.

Hello, My app has now been stuck in “Waiting for Review” for more than 66 hours after resubmission, with no status change. This is the first public release of the app. I have also experienced unusually long review delays on several previous submissions. In one previous case, the submission remained stuck for nearly a week, and a Contact Us support request also went unanswered for about a week. Once the app actually enters “In Review”, the review itself is usually completed very quickly, which makes me concerned that the repeated delay may be related to queueing or routing rather than the review itself. I replied to App Review and resubmitted the app three days ago, but there has been no further response or progress since then. A priority / expedited review had previously been approved, so I am also concerned that the current resubmission may have lost its priority or may not be correctly routed in the review queue. Could an Apple Staff member please help confirm whether this submission is correctly queued for review, and whether there may be a routing or processing issue affecting it? Submission ID: cb8ae2c6-94ab-463d-b9a6-e218179ecefc Thank you very much for any assistance.

Hi everyone, I'm hoping someone here has run into this and found a way through it, because Apple Support hasn't been much help so far. Background: We manage an Apple Developer Program Organization account for a healthcare startup. The membership itself is active and has existed for a while — we're simply trying to renew it. The issue: Every renewal payment attempt gets redirected to a "payment review," and every single review has since failed — 5 times in a row now, over more than a week. We've tried: A locally-issued card, paid from within the country of registration A different card issued in a different country, paid from that country Both cards, both regions — same result every time. No explanation is given for why the review fails, and no alternative payment method is offered. What we've already done: Contacted Apple Developer Support multiple times through the normal request form Explained the repeated failures and asked for the specific reason Asked for escalation beyond the standard review queue So far, we've gotten generic responses without any diagnostic detail on why the payment keeps getting flagged, and no indication of timeline. Why I think this isn't a card issue: Five consecutive failures across two completely different cards, banks, and countries strongly suggests the problem is on the review/account side, not the payment method itself. But without any feedback from Apple explaining what's actually being flagged, we're stuck guessing. This is currently blocking a completed, ready-to-submit app from being released, so the urgency is real on our side. Has anyone dealt with a payment review that kept failing repeatedly like this? Did you find out what actually triggers repeated review failures (billing address mismatch, name mismatch, something account-level)? Is there a way to reach a specialized billing/renewal team rather than the standard support queue? Did a specific action on your end (changing payment method type, updating account info, waiting a certain amount of time) actually resolve it? Any insight — even "this happened to us and here's roughly how long it took" — would genuinely help. Thanks in advance.

We are testing two auto-renewable subscriptions for a new iOS app. In Apple Sandbox, StoreKit 2 Product.products(for:) always returns an empty array. Legacy SKProductsRequest independently reports both identifiers as invalid. Environment: Physical iPhone, iOS 26.5 Xcode development build with automatic signing Storefront.current = USA (143441) canMakePayments = true No StoreKit Configuration file in the Run scheme Direct native StoreKit 2 diagnostics, without a third-party purchase SDK TN3186 checks completed: Explicit Bundle ID matches the App Store Connect app, installed app, and provisioning profile In-App Purchase is enabled for the App ID Developer membership, Paid Apps Agreement, banking, and tax are active One subscription group with monthly and yearly subscriptions is visible Pricing, localizations, and availability are configured Neither subscription is Rejected or Developer Action Needed The scheme is using real Sandbox data, not local StoreKit testing Results: StoreKit 2 batch query: rawCount = 0 SKProductsRequest: valid = []; both identifiers are invalid StoreKit 2 individual monthly query: 0 StoreKit 2 individual yearly query: 0 No exception; failure occurs during product discovery Related reports: https://developer.apple.com/forums/thread/839313 — TN3186 verified and USA storefront valid, but still 0 products; no replies https://developer.apple.com/forums/thread/841722 — Apple Commerce mentioned Rejected or Developer Action Needed states; ours have neither https://developer.apple.com/forums/thread/820656 — Apple DTS confirmed first subscriptions do not require review before Sandbox testing Apple Developer Support referred us to TN3186, and we verified every applicable item. The individual subscription detail route in App Store Connect also intermittently remains on a loading indicator although the group and both records are visible. Could an App Store Commerce or StoreKit engineer check whether the app-to-IAP catalog association is populated correctly on Apple's side, or advise an official escalation path to have the Sandbox catalog reprocessed? Exact account, app, product, device, email, and support-case identifiers are omitted from this public post and can be supplied privately through Apple Support or Feedback Assistant.

Hello, I’m posting here to ask for guidance and to see if anyone has experienced a similar situation. More than 30 days ago, I submitted an appeal to the App Review Board after receiving a Pending Termination Notice for my Apple Developer Program account. However, I have not received any response or update since submitting the appeal. In the notice, Apple mentioned that my account was associated with “dishonest or fraudulent activity” related to app submissions. I want to clarify that I did not intentionally attempt to bypass the App Review process. The only change I made around that time was editing some app metadata (subtitle keywords) while trying to optimize my Apple Search Ads campaign. Looking back, I now understand that some of those keywords may have been interpreted as referencing content that Apple considers inappropriate for the App Store. After realizing this might have caused an issue, I immediately: Canceled the latest app submission that contained those metadata changes Explained the situation clearly in my appeal to the App Review Board Confirmed that I would avoid using similar metadata in the future Despite providing this explanation in my appeal, I have not received any reply or update for over a month, so I’m unsure about the current status of the appeal. If anyone here has gone through a similar process, could you share: How long it took to receive a response from the App Review Board? Whether it’s normal for appeals to take this long? Also, if any Apple staff happens to see this post, I would sincerely appreciate any guidance on whether my appeal is still under review or if there is anything further I should provide. Thank you very much for your time and help.

While validating Xcode Cloud with a self-managed GitLab instance, I found what appears to be an OAuth scope issue affecting private repositories. Apple’s documentation says to configure the GitLab OAuth application with: api, read_repository, read_user However, the actual /oauth/authorize URL generated by Xcode Cloud requests only: scope=api+read_user With a private GitLab repository, OAuth completes successfully and Xcode Cloud can call: GET /api/v4/user → 200 GET /api/v4/projects/:project → 200 But repository setup fails with: Repository was not found. Either the repository does not exist or you do not have permission to access it. The GitLab user had Maintainer-or-higher access. I reproduced this from a clean Xcode Cloud setup. As a control test, I repeated the exact same flow but manually changed the OAuth authorization request to: scope=api+read_user+read_repository GitLab then explicitly requested read-only access to private repositories over Git HTTP. After authorization, the same private repository connected successfully to Xcode Cloud, and a build could be queued normally. A public repository works without read_repository, which can hide the issue. So the reproducible difference was: Private repo + Apple-generated api read_user → fails Private repo + api read_user read_repository → succeeds This also appears inconsistent with Apple’s own self-managed GitLab setup documentation, which instructs users to enable read_repository. I’m sharing this mainly for others who may run into the same issue with private repositories.

I'm stuck on what should be a routine resubmission and can't find documented steps that match what I'm actually seeing in App Store Connect. Situation: My app's only existing submission (from an earlier rejected review round) is now in "Unresolved Issues" status. Per Apple's own docs, items can't be added to a submission in this state. I have a new build ready and uploaded (via eas submit / App Store Connect API), showing "Ready for Review" on the version page. I also have two subscriptions in the same subscription group, both fully configured and showing "Ready for Review" status. The subscriptions' own "Add for Review" button creates a separate Draft Submission, but that draft has no way to attach an app version to it. It just shows "To submit your items for review, add an app version for the selected platform," with no visible control to do so from that panel. The app version page itself has no "+" button next to Build and no "In-App Purchases and Subscriptions" section (some help docs describe this section; it doesn't appear on my version page at all). What I'm trying to do: submit the new build together with both subscriptions as one review submission, since it's a first-time auto-renewable subscription and Apple requires it be submitted alongside an app version. Has anyone run into this specific dead end: an app version with nowhere to attach IAPs, and a subscription draft with nowhere to attach a build? What's the actual current path to combine them? Screenshots of the exact UI I'm seeing available on request.

Hello, I made my app icon with Icon Composer and added the .icon file directly to my Xcode project. I noticed that the icon preview in Icon Composer looks one way, while the icon shown on the App Store looks different. Details: I am using the .icon file directly in the project I am not using an exported PNG for the app icon I did not add a separate background image The background was set with fill in Icon Composer The preview in Icon Composer looks as expected The App Store version has a different appearance I would like to ask whether this difference may come from: App Store processing caching or a recommended Icon Composer setup for background fill If anyone has seen something similar, I would appreciate any guidance. I can also share screenshots of the Icon Composer preview and the App Store result.

Hi all, My app has been stuck in the "Waiting for Review" status since August 13 (US Time), and today is August 23. It has been 10 days without any status updates or messages from the App Review team. App ID: 6800282515 Submission Date: Aug 13, 2026 Developer Support Request Submitted: Aug 19 (No response yet) Expedited Review Requested: Aug 20 (No response yet) Current Status: Waiting for Review Since both support inquiries and expedited requests haven't received a reply after several days, I am concerned there might be an internal system hold or communication breakdown regarding this submission. Could someone from Apple please look into this or advise if any additional documentation/action is needed from my side? Thanks for your help!

Hi! I've successfully uploaded my web extension using the Web Extension Packager. However, there was a build error. When I review the list of cloud builds and click "view issues" for the failed build, I get the message: "Exporting for App Store Distribution failed. Please download the logs artifact for more information." However, I can't find any link in the app store connect web UI for viewing the logs artifact for Web Extension Packager builds.

When trying to log in to App Store Connect, I receive the following message: Your Apple Account is not enabled for App Store Connect. (https://appstoreconnect.apple.com/m/INVALIDITCUSER) I have already paid the annual fee and can access my Apple account normally.

Hello, I forgot to renew my Paid Apps Agreement when the previous one expired. As a result, all of my In-App Purchases and subscriptions became unavailable. I have now signed the new agreement, and it appears as active in App Store Connect. However, my In-App Purchases are still unavailable and purchases cannot be completed in my apps. Is there a propagation delay after signing the agreement before In-App Purchases become available again? Does Apple need to perform any manual action on their side after the agreement is renewed? If there is a delay, how long did it take in your experience? My products are still marked as "Ready for Sale" and everything else appears to be configured correctly. This issue is currently affecting live apps and preventing customers from making purchases, so I'm trying to understand whether I should simply wait or contact Apple Support. Thanks for any insights.

Hello, I am posting here because I no longer have access to the communication channels that were previously available to discuss my developer account with Apple. My appeal was denied, but Apple informed me that I could submit a reinstatement request after addressing the concerns that had been identified. Following that communication, I spent considerable time reviewing my applications, metadata, screenshots, codebase, user flows, and business practices. Although I do not believe my account was involved in dishonest or fraudulent activity, I nevertheless made extensive changes in an effort to address any potential concerns Apple may have had. The main difficulty is that the specific conduct that led to the termination decision was never clearly explained to me. Apple cited Section 3.2(f) and provided examples of prohibited behavior, but did not identify which specific action or activity was associated with my account. As a result, I was left attempting to correct every possible issue without understanding what the actual concern was. In addition, throughout my participation in the Apple Developer Program, I had never previously encountered a notice, suspension, or similar action of this nature. This made it even more difficult for me to understand what specific issue Apple believed had occurred and how best to address it. While I was still implementing changes and preparing what I believed would be a reinstatement submission, I received a termination notice. Since the termination, I have lost access to the Contact Us page and the communication channels that were previously available to me. I would therefore appreciate guidance from Apple or from developers who may have experienced a similar situation: How is a developer expected to submit a reinstatement request after termination if the Contact Us page is no longer accessible? Is there an alternative channel through which reinstatement requests can be submitted? Has anyone successfully submitted a reinstatement request after account termination and received a review? I am not asking Apple to reverse its decision through this forum. I am simply trying to understand how a developer is expected to submit a reinstatement request after termination when the previously available communication channels are no longer accessible. Thank you for your time.