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.

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, 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.

I need Apple to update a legacy App ID prefix to match my Team ID, and my support case has gone unanswered. Posting here in hopes a code-signing engineer can advise or nudge it along. My app VHDLRef (bundle ID com.squishLogic.VHDLRef, Apple ID 418473744) dates back to my original individual developer account. The App ID's prefix is still the legacy value CN7ZHAEHF4, while my current team (squishLogic LLC) has Team ID R55F2X4J69. Certificates, Identifiers & Profiles confirms the prefix mismatch. The iOS app builds, uploads, and was just approved (v3.2), since iOS accepts an App ID prefix that differs from the Team ID. The macOS build of the same target is rejected at upload by App Store Connect: Error 91130: "Invalid Provisioning Profile ... Invalid 'com.apple.application-identifier' entitlement value." Error 90286: "the 'CN7ZHAEHF4.com.squishLogic.VHDLRef' value for the com.apple.application-identifier key ... isn't supported. This value should be a string that starts with your Team ID, followed by a dot, followed by the bundle ID." My understanding is that the Mac App Store requires application-identifier to be TeamID.bundleID, there is no self-service way to change an App ID prefix, and the fix is for Apple to update the prefix to R55F2X4J69. The app has no keychain items or keychain sharing (entitlements are empty), so no user data depends on the old prefix. Questions: (1) Is a prefix update the correct and available fix here? (2) Is there any developer-side workaround short of shipping the Mac app under a new bundle ID and losing universal purchase? (3) Any way to escalate the support case, given phone support is currently unavailable? Case number: 20000152117550

Hello, Our app has been in "Waiting for Review" since August 18, 2026 at 6:51 PM, and has never entered "In Review." It has now been 10 days. Apple ID: 6768989011 Version: 1.0 Platform: iOS Submitted: August 18, 2026 Current Status: Waiting for Review I have already confirmed the following on our side: No messages or requests for additional information in Resolution Center Agreements, Tax, and Banking are all Active Age Rating questionnaire and Export Compliance are complete App Review Information includes demo credentials and detailed review notes No in-app purchases pending review I understand review times can vary, and I can see from recent posts in this forum that other developers are experiencing similar delays with first submissions. Could someone from the App Review team please check whether this submission is progressing normally, or escalate it if necessary? Thank you for your time.

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.

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.

Hello, I am seeking guidance regarding a Pending Termination Notice received on March 18, 2026 for the developer account of Kaagapay Platform Inc. Background: Our app, CreditKaagapay: Score & Report (App ID: 6744999391), is a credit report and loan matching platform operating in the Philippines in partnership with the Credit Information Corporation (CIC). The app maintained a 4.8-star rating with over 4,000 reviews. No prior warnings were issued before the notice. Notice Details: The notice cited Guideline 5.6 and Section 3.2(f), alleging dishonest or fraudulent activity related to account information. Timeline: • March 18: Received the Pending Termination Notice. Submitted two appeals (App Removal + Pending Account Termination) on the same day. Both received on-screen confirmation. • March 25: Submitted a follow-up through the App Review Status contact form. • March 26: Developer Support confirmed the appeal was forwarded to the App Review Board (Case ID: 30000003321343). • April 1 (today, Day 14): No response received from the App Review Board. Questions: Is there a way to confirm that our appeals are currently under review by the App Review Board? Are there any additional steps we should take to bring this to the Board's attention? Is there any mechanism to submit supplementary documentation, as the appeal form did not support attachments? We remain fully committed to compliance and ready to provide any additional information requested. Thank you for any guidance. Yifu Zhang, Account Holder Case ID: 30000003321343

Hi! I currently have a web extension sucessfully published to Firefox. And now I'm trying to make the same web extension available for Safari. But I am having some trouble. Steps to reproduce this issue: Through appstoreconnect I create a new app. Within the app I select the tab Xcode Cloud, and scroll down to the Safari Web Extension Packager. When I try to upload a .zip file of my extension I get the error message: "NetworkError when attempting to fetch resource." According to the docs this upload feature should be compatible with any browser. I'm using Firefox version 154 running on Linux Mint 22.3. Note to forum admins: I originally tried to post this under subtopic Web Extensions but for some reason I kept getting an error when hitting "Post". That's why I'm posting this issue under the sub-topic General.

Hello, I am new for apple developer. I see the problem and I think apple show me very few error message and I do not know to start with it. I was created my app by python and build to .app then package it to pkg by the pkgbuild. I have problem to upload the pkg file to app store connect by transporter both CLI and GUI. when I try to upload it by GUI, I see this message. Cannot find the ITMSP file: (null). (11)` and when I upload my pkg by the CLI, I found more message but still cannot start with it as well. [2026-08-23 09:57:58 ICT] <main> DEBUG: Registered file for monitoring: /Users/xxxxxxxxx/.itmstransporter/temp/tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp with action CANCEL_ALL [2026-08-23 09:57:58 ICT] <main> DEBUG: Started file monitor for 1 file(s) [2026-08-23 09:57:58 ICT] <main> INFO: Starting upload for package b7ac46de-45fe-4fa6-b0f6-6fea35038d8f-tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp. [2026-08-23 09:57:58 ICT] <main> INFO: Computing total size of files to upload ... [2026-08-23 09:57:58 ICT] <main> DBG-X: adding file for % complete logging: tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp , size: 7704460 [2026-08-23 09:57:58 ICT] <main> DEBUG: Setting total size of files for upload to: 7704460 [2026-08-23 09:57:58 ICT] <main> INFO: Done computing total size of files to upload. [2026-08-23 09:57:58 ICT] <main> INFO: Starting checksum calculations for 1 file(s) using up to 1 thread(s)... [2026-08-23 09:57:58 ICT] <main> INFO: Checksum calculations are complete, elapsed time: 0 d 0h 0m 0s. [2026-08-23 09:57:58 ICT] <main> INFO: Creating reservations for build upload: b7ac46de-45fe-4fa6-b0f6-6fea35038d8f [2026-08-23 09:57:58 ICT] <main> DEBUG: creating upload file... [2026-08-23 09:57:58 ICT] <main> DEBUG: SMART-CLIENT: getCurrent(); using pinned data center = contentdelivery01.itunes.apple.com [2026-08-23 09:57:58 ICT] <main> INFO: Package upload progress: 0.00% completed [2026-08-23 09:57:58 ICT] <main> INFO: Transfer Metrics Summary: [2026-08-23 09:57:58 ICT] <main> INFO: bytes transmitted: 0 [2026-08-23 09:57:58 ICT] <main> INFO: tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp transfer metrics: [2026-08-23 09:57:58 ICT] <main> INFO: bytes transmitted: 0 [2026-08-23 09:57:58 ICT] <main> INFO: Starting checksum calculations for 1 file(s) using up to 1 thread(s)... [2026-08-23 09:57:58 ICT] <main> INFO: Checksum calculations are complete, elapsed time: 0 d 0h 0m 0s. [2026-08-23 09:57:58 ICT] <main> INFO: Creating reservations for build upload: b7ac46de-45fe-4fa6-b0f6-6fea35038d8f [2026-08-23 09:57:58 ICT] <main> DEBUG: creating upload file... [2026-08-23 09:57:58 ICT] <main> DEBUG: SMART-CLIENT: getCurrent(); using pinned data center = contentdelivery01.itunes.apple.com [2026-08-23 09:57:59 ICT] <main> DEBUG: Stopped file monitor [2026-08-23 09:57:59 ICT] <main> DEBUG: Transport HTTP failed after 0 bytes, trying next transport. Error: could not upload file: tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp [2026-08-23 09:57:59 ICT] <main> DEBUG: Upload phase transition: CLOSED -> INITIAL [2026-08-23 09:57:59 ICT] <main> ERROR: All transport types failed for file: tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp Package Summary: 1 package(s) were not uploaded because they had problems: /Users/xxxxxxxxx/xxxxxxxxx/../xxxxxxxxx_Image/xxxxxxxxx.pkg - Error Messages: All transport types failed for file: tx-xxxxxxxxx.pkg-swinfo.plist16166255377348903097.tmp [2026-08-23 09:57:59 ICT] <main> DBG-X: Returning 1 Not too sure if anyone ever see my issue and how you solved it?

Hi everyone, I submitted my identity verification documents (Passport) on August 6th for my Apple Developer Program enrolment (Case Number: 20000127168095). It has been over 25 days and I haven't received any response or update on my enrolment status. Can an Apple Moderator or staff member please help review or escalate this case? Thank you!

Our developer account was deactivated, and our app has now been unavailable for more than a week. We submitted our appeal and contacted Apple regarding Case ID 20000149095871, but we still have not received a substantive response. We have worked with Apple for approximately three years and have always had great respect for the App Review team and Apple’s rules. Whenever App Review raised concerns in the past, we communicated openly with the team, understood the issue, and made the requested changes. That is why we were genuinely shocked and deeply concerned by what happened. We are not asking Apple to make an exception for us. We are simply asking for the opportunity to understand what went wrong and fix it. Our team is ready to provide any information, make any necessary corrections, or speak directly with Apple by phone. After three years of cooperation and respect for Apple’s team, it is very difficult for us to understand why our app has been unavailable for more than a week while we are still waiting for an answer. We sincerely hope someone from Apple can review our situation and escalate Case ID 20000149095871 to the appropriate team. We just want the opportunity to understand the issue, cooperate with Apple, and resolve this properly. Thank you for your attention and help.

Hello! I have a new organization-level Apple Developer account and I'm stuck on the Tax Forms step in App Store Connect (https://appstoreconnect.apple.com/business). The system is showing me U.S. Form W-9 as the only option, but in my case filling out a W-9 would be incorrect — and I'd appreciate guidance from anyone who has resolved this. My setup: I am a non-US individual (not a US citizen, not a US resident, never lived in the US). I am the sole owner of a single-member LLC registered in the US (set up via Firstbase specifically to distribute a mobile app). For US federal tax purposes, this LLC is a disregarded entity — it's not treated as a separate taxpayer from its owner. Why W-9 is not the correct form in my case: The IRS instructions for Form W-9 explicitly state: "If the owner of the disregarded entity is a foreign person, the owner must complete an appropriate Form W-8 instead of a Form W-9. This is the case even if the foreign person has a U.S. TIN." Form W-9 also requires me to certify, under penalty of perjury, that I am a US person — which I am not. The LLC itself doesn't certify anything on a W-9 because it's disregarded; the IRS looks through to the beneficial owner, who in my case is a foreign individual. The correct form for me should be W-8BEN (Certificate of Foreign Status of Beneficial Owner — Individuals). What I've already tried: I opened two support cases 4 days ago and have not received a substantive response yet: Apple Developer Support — Case ID: 20000112974233 Ack Tax / Tax category settings — Team ID: 7YYWN3MYCY, Case ID: 19944616 My questions: Has anyone in the same situation (non-US individual, sole owner of a US single-member LLC) successfully switched the tax form from W-9 to W-8BEN inside App Store Connect? If so, how? Is there a specific path in the Business / Tax Forms section to declare the beneficial owner as a foreign individual that I might be missing? Is there an escalation channel beyond the standard support cases for tax-form issues that are blocking onboarding? Thanks in advance for any pointers.

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.

Hello, I enrolled as an individual and paid the annual Apple Developer Program membership fee. My membership is active, my role is Account Holder, and I can access Certificates, Identifiers & Profiles. However, every attempt to open App Store Connect redirects to: https://appstoreconnect.apple.com/m/INVALIDITCUSER?errorKey=ITC.signin.error.invalidUser.asc The message says that my Apple Account is not intended for use with App Store Connect or that I must be a member of the Apple Developer Program. This contradicts the active membership shown in my Developer Account. I have contacted Apple Developer Support and requested escalation, but access is still not provisioned. This appears to be a missing or desynchronized App Store Connect (ITC) provisioning record: my Developer Program account is active, but my Apple Account is not linked correctly in App Store Connect. Has anyone experienced this exact issue? Did Apple have to manually restore or create the App Store Connect provider/user record, and which support team resolved it? Thank you.

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 App Review, I have an update to a live app that has now spent roughly 10 weeks unable to get through review, across two separate submissions, and I'd appreciate someone checking whether it's genuinely queued or whether something is holding it. Timeline: 16 June 2026 — v1.1.0 submitted. Sat in "Waiting for Review" for 5+ weeks, never moved to In Review. No Resolution Center message, nothing action-required. 23 July 2026 — after that submission showed no movement, I removed it and submitted a fresh build of the same version. It has now been in "Waiting for Review" for 38 days, again with no reviewer pickup and no Resolution Center message. v1.0.0 reviewed and approved normally on 8 June 2026, so the app and account have a clean prior review. The resubmission has been left completely untouched — no edits, no cancellations — so this is not a case of repeated changes resetting the queue. Two clean submissions of the same update have now stalled identically. What I've already checked on my side: no Resolution Center messages, no action-required banners, build shows valid and correctly attached to the version, export compliance answered, and Agreements/Tax/Banking all current. I've also raised support case 102923511308 and submitted an expedited review request, neither of which has changed the status. Could someone confirm whether this submission is proceeding normally, or flag if anything is required from me or if it needs to be looked at manually? Happy to provide the submission ID or any other detail. @Apple

Hello App Review Team, I’m seeking confirmation that my first iOS app submission is correctly queued for review. DriveAvionn 1.0 was originally submitted as a new app and remained in Waiting for Review for an extended period. App Review subsequently requested additional information under Guideline 2.1, including a physical-device screen recording and details regarding the app’s functionality, target audience, testing environment, external services, regional operation, and access instructions. We provided the requested information in full, including a continuous physical-device recording demonstrating account creation and verification, both vehicle-search workflows, messaging, billing, account settings, and account deletion. The separate App Review test account remains active and available. The submission was then successfully resubmitted and is currently again showing Waiting for Review. There are no outstanding messages or compliance items visible in App Store Connect, and no purchase is required to review the app. Given the unusually long review times currently being reported for first submissions, could someone from App Review please confirm that this submission is properly queued and that no additional action is required on our side? Thank you for your assistance.

Hello, I’m having a recurring TestFlight issue. This is already the third time it has happened. All of my TestFlight builds are automatically marked as Expired, and I’m unable to submit a new processed build for External Testing. App Store Connect returns: HTTP 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Beta Contract is missing. My Developer Program membership and agreements are active, with no pending agreements. The issue happens directly in the App Store Connect website, with no third-party service involved. Has anyone else experienced this? It seems like a TestFlight backend / Beta Contract provisioning issue. I’ve already contacted Apple Support multiple times, but the problem keeps returning. Thanks.

Hoping someone from App Review can take a look at a first submission that has been sitting in "In Review" since 22 July. App: NextUp (Apple ID 6758259427), iOS 1.2, build 30141 Submission ID: 5ea082d9-58b1-4430-b897-5111bc78225a Submitted: 22 July 2026 Status: In Review. All 11 items show In Review (app version, subscription group, 4 auto-renewable subscriptions, 5 consumables). What has happened so far: 22 July: automated metadata return for a missing Terms of Use link. Fixed it the same morning and resubmitted. The submission moved to In Review and has not changed since. 9 August: requested an expedited review. Accepted on screen, no follow-up. 19 August: opened case 20000141656520 asking for status. Reply on 24 August confirmed the expedite had been accepted and the app is In Review. No ETA, nothing asked of me. 30 August: followed up on the same case. Auto-acknowledged. There are no messages in Resolution Center after the resubmission and nothing waiting on me. The build is valid, the demo account in App Review Information works, all metadata links resolve, and the Paid Applications agreement, banking and tax are active. I understand the queue is long at the moment, but 39 days without a single reviewer note is well outside anything I have seen. Could someone check whether this submission is actually assigned, or whether something is holding it that I can't see from my side? Happy to provide anything that would help.