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

Hi all, I hope someone from App Review can take a look My situation: QuidProQuote: Memory Keeper (app ID: 6791349683) is a simple cross-platform app where a single purchase unlocks both the macOS and iOS versions. Both versions were submitted from the same build/codebase. The problem is that while my macOS version has been approved and is now pending my release, the iOS version (submission ID: 9fba8d59-d9a7-4a09-bbbe-1d23035adbe1) has been "Waiting for Review" for 12 days now. 2026-07-30, ~4:30pm ET: Both macOS and iOS submissions entered "Waiting for Review" 2026-08-06, ~10am ET: macOS version approved, now Pending Developer Release 2026-08-11 (Today): iOS version still showing "Waiting for Review," 12 days with no status change This ends up being more than a normal wait because the purchase is shared across platforms... releasing the macOS version now would put it in front of customers without the iOS half of what they're paying for. I can't release the approved macOS build until the iOS version clears review, so the delay on one platform is effectively holding both hostage. I did file an expedited review request today (2026-08-11), received confirmation ("we'll expedite this review"). But I read advice that additionally it would be wise to register the problem here. Thanks for any visibility into this!

Hi all, Like others my app submission has been stuck in “waiting for review” for weeks. I know initial app reviews take longer than updates, but this has been delayed far too long and makes me concerned about repeating the process in the future. I submitted this app for review back on Feb 10. It was initially rejected for a minor issue, which I resolved and resubmitted the same day. After that, the build remained in “Waiting for Review” for about two weeks with no further communication. At that point I canceled the submission and resubmitted the build, thinking it may have been stuck in the queue (I now know not to do this next time). Unfortunately the new submission has also been waiting for review for another 9 days now with no messages or updates. I’ve contacted app review support as well (case ID- 102826632729). I understand review times can vary, but delays like this make it difficult for developers to plan launches or push updates when the review process is the only path to distributing apps. As paying members of the Apple Developer Program, we rely heavily on this pipeline functioning reliably. Hoping this post will reach someone from Apple who can help move the process along. If any other devs have suggestions/tips that have worked for them, please share so others in this position can become unblocked. Thanks in advance.

Hello, Our app was submitted on August 7 and has remained in “Waiting for Review” with no status change. This is now a launch-blocking issue for a scheduled enterprise customer rollout on August 13. Hundreds of participants are already scheduled for mobile user testing and are unable to proceed without the iOS app. We have submitted an expedited review request and contacted Developer Support, but have not received a response or any update from either channel. At this point, the App Review delay is directly blocking a committed enterprise launch and participant testing schedule. We would greatly appreciate any urgent assistance in getting this case reviewed or escalated to the appropriate App Review team. App Name: Satellica App Apple ID: 6797731123 Submission ID: b7105850-5a17-489d-907d-550febe3895a Thank you.

Hi Apple Developer Community, Our first iOS release (Version 1.0) has been stuck in “Waiting for Review” since August 7 with no status change. We have already submitted an expedited review request due to a critical, time-sensitive business need this week. We have also tried contacting Apple Developer Support through multiple channels. We requested a phone callback but have been waiting for over six hours without being connected, and we have not yet been able to reach the support team. Could someone from Apple please advise whether there may be an issue with the submission, or whether there is any additional action we should take to help move the review forward? Any guidance or assistance would be greatly appreciated. Thank you.

Our app — a screen-time / focus app — has had no App Review activity for two weeks, and we believe the trigger was an automated Guideline 2.5.1 check that froze an otherwise actively progressing review. (This forum account is linked to the developer account in question; we can provide the App ID, bundle IDs, submission IDs, and support case numbers through any private channel on request.) Context: Jul 2–5: Our first submission (Version 1.0.0) was under active review. We went through several ordinary metadata / paywall-related iterations, and the reviewer responded within roughly 24 hours each time. Nothing related to Screen Time was raised in these human reviews of builds 9 and 10. Jul 8: After we submitted build 11 — which addressed the remaining human-review feedback — we received an automated Guideline 2.5.1 (Performance: Software Requirements) message stating that the app uses the Screen Time API but has not been submitted with the Family Controls entitlement, and that review of the submission cannot proceed. All reviewer activity stopped at that point, and there has been none since. What we verified: The Family Controls (Distribution) entitlement is granted to our account and assigned to all four bundle IDs (the main app plus its DeviceActivityMonitor, ShieldAction, and ShieldConfiguration extensions). We verified with codesign that com.apple.developer.family-controls = true is present in the code signature and embedded provisioning profile of every one of the four executables in the submitted IPA — so the entitlement named in the automated message is present in the flagged build. For context: builds 9 and 10, with an identical Screen Time API surface and identical entitlements (verified at the binary level with nm against the submitted artifacts), had been human-reviewed on Jul 2–5 with no Screen Time-related objection. We recognize those builds may simply not have reached the automated analysis stage before being superseded, so we do not draw firm conclusions from that. What we did anyway (build 12, submitted Jul 9): In case the automated check actually concerns the separate com.apple.developer.family-controls.app-and-website-usage entitlement (which we do not request and do not need), we removed every reference from our main app to the APIs associated with it: AuthorizationStatus.approvedWithDataAccess, ManagedSettings.Application.bundleIdentifier, ManagedSettings.Application.localizedDisplayName, ManagedSettings.ActivityCategory.localizedDisplayName, and ManagedSettings.WebDomain.domain. We verified with nm that none of the four executables in the build 12 IPA reference these APIs. The app does not use FamilyActivityData, DeviceActivityReport, app usage events, web usage events, or App and Website Usage data access. No automated message has appeared for build 12. What has happened since: Jul 9–14: No reviewer activity on build 12. We filed an expedited review request and opened two Developer Support cases (Jul 8 and Jul 14). No response to any of them. Around Jul 15: Hoping to clear the frozen state, we cancelled and resubmitted the same Version 1.0.0 / build 12. Around Jul 17: Filed a second expedited review request for the new submission. Jul 22 (today): The new submission has been in "Waiting for Review" since Jul 15, with no reviewer activity and no reply to either support case or either expedite request. What we are asking: Could someone check whether the Jul 8 automated flag is still attached to the app record and blocking reviewer assignment, and help get the current submission assigned to a reviewer? If the automated check flags build 12 again, could the message specify which entitlement and which binary / API references triggered it, so we can address it precisely? We can provide codesign output, entitlement plists, provisioning profile dumps, and nm symbol listings on request. Thank you.

Hello, our team is currently in the process of adapting our app for UIScene lifecycle and Liquid Glass. When building with Xcode 26 and iOS 27 Simulator, we see the following message in the console: "UIScene life cycle is now required when building with the latest SDKs. Apps that don't adopt will fail to launch." If we build the app with Xcode 27 without scenes implemented, it crashes on launch as expected. To plan our development roadmap, we would like to clarify the following: 1. Behavior of Xcode 26 builds: Can builds created with Xcode 26 (without UIScene support) still be submitted to the App Store, and will they continue to launch without crashing for users updating to future iOS versions? 2. Xcode 26 submission deadline: Until what exact date will Apple continue accepting App Store submissions built with Xcode 26? Thank you for your guidance!

Hello, My app Air Finder - My Device Tracker (Apple ID: 1490211589) seems to be stuck in the App Review process and I'd like to check if something might be wrong with my submission. Timeline: Submission for review: Jul 30, 2026 Current status: Waiting for Review Waiting time: 7 days as of Aug 6, 2026 My app reviews are typically approved within 1-2 business days, so I suppose this delay seems to be unusual. Please help review this submission as soon as possible! I have a timeline for publishing app version that cannot be delayed for this long. Any guidance would be very appreciated. Thank you in advance!

Hello, Our game is scheduled for official release tomorrow, Wednesday, August 5, and we would like to request an expedited review. This build was first submitted on July 23 and has been in the review process for about two weeks; our latest submission is currently in "Waiting for Review" status. All marketing and promotional campaigns have already been rolled out based on the August 5 launch date. This date is especially important because the new theatrical film of the original animation 'Catch! Teenieping' premieres on the same day, and the game is planned to launch alongside the film. The previous film drew over 1 million moviegoers, becoming the first Korean animation to do so in 12 years. Many children and family fans have long been looking forward to this day. This is the first official match-3 puzzle game based on the Teenieping IP, and we have put great care into making it a game families can enjoy together. After launch, we are fully committed to operating the game responsibly in compliance with the App Store guidelines. We apologize for the urgent request and would sincerely appreciate it if the review could be completed in time. App Name: Teeniping Magic Match App Apple ID: 6786589102 App Bundle ID: com.plaium.tmm

Hello, My iOS app, Chef Library, version 1.2.0, has remained in “Waiting for Review” for several days. App Store Connect shows no unresolved issues, missing information, or messages from App Review. I contacted Apple Developer Support on July 28 and followed up again on July 30. Both messages appear under support case 20000121706395, but I have not received a response and the review has not started. The submission details are: App: Chef Library Platform: iOS Version: 1.2.0 Current status: Waiting for Review Support case: 20000121706395 Could an Apple representative please check whether this submission is progressing normally or whether it has become stuck in the review queue? If anything is required from me, I am ready to provide it immediately. Thank you, Bart

Hello everyone, I’m writing this post in the hope of hearing from other developers who may have experienced a similar situation, and to better understand whether this level of action without transparency is common. Our company, VISION VENTURES TEKNOLOJİ TASARIM VE PAZARLAMA A.Ş., is the developer of Watchlabb, an app that has been available on the App Store for approximately six months. Watchlabb is not an online watch retailer. We do not own watches, buy watches, or sell watches. Our platform simply connects independent buyers and sellers of authentic watches, allowing them to publish listings, create auctions, and communicate directly with each other. From the very beginning, our goal has been to build one of Turkey’s safest marketplaces for authentic watches. To achieve this, we have invested significant effort into protecting users by: Reviewing listings before publication. Rejecting counterfeit and replica watches. Verifying user identities. Moderating marketplace activity. Building a transparent and trustworthy environment for collectors and buyers. In other words, our platform exists to prevent fraud, not enable it. Despite this, Apple terminated our entire corporate Developer Program membership under Section 3.2(f) of the Apple Developer Program License Agreement. The notice states that Apple has “documented indications of fraudulent conduct associated with your account.” However, it does not explain: What specific conduct allegedly violated the agreement. Which feature, transaction, listing, or activity is involved. Whether the concern relates to a specific user. What evidence led Apple to this conclusion. Before the termination: We never received a warning. We were never informed that our account was under investigation. We were never asked to provide additional information. We were never given an opportunity to explain or correct anything. Even more confusing, our latest app update was approved through App Review just three days before our developer account was terminated. This decision affects much more than our company. We currently have approximately: 2,800 registered users, hundreds of active listings, ongoing auctions, professional stores operating on our platform. Many businesses rely on our application to reach customers, and many users depend on it to buy and sell authentic watches safely. As a registered company, we have contractual obligations, commercial partnerships, and responsibilities toward both our sellers and our users. Having our entire developer account terminated without knowing what specific conduct Apple believes occurred has placed both our business and our community in an extremely difficult position. We fully support Apple’s efforts to protect users and maintain the integrity of the App Store. Those are values we share. What we struggle to understand is how such a severe action can be taken without identifying the specific facts behind the allegation or giving a company the opportunity to respond before permanently terminating its developer account. Has anyone else experienced a similar situation? Were you able to obtain more detailed information from Apple or successfully resolve the issue? Any advice or shared experience would be greatly appreciated. Thank you.

App update stuck in “Waiting for Review” after replacing an approved build (possible queue issue?) Hello, I would like to know whether other developers are experiencing a similar issue with App Review this weeks. App: Spherag IOT Platform: iOS Current build: 1.2.34 (234) Status: Waiting for Review Timeline Friday, July 24: build 1.2.30 was reviewed and approved successfully. We decided not to release that approved build. Monday, July 27: we removed it from release and submitted 1.2.31 (231). Build 1.2.31 remained in Waiting for Review for about 3 days and never moved to In Review. We then submitted 1.2.34 (234), Today, August 04: after waiting several days with no progress, we removed the submission and re-submitted the same build, 1.2.34 (234), which is currently still in Waiting for Review. I have already opened two Developer Support cases regarding this issue, but I have not yet received a resolution. What concerns me most is that, after submitting build 1.2.34, the version history in App Store Connect appears inconsistent and previous entries are displayed as 1.2.34 (234). This makes me wonder whether there could be a display issue or a problem with the review queue state. All Agreements, Tax and Banking information are active, and all required metadata, privacy details, export compliance and age rating information are complete. This delay is becoming difficult to manage operationally: one release is already blocked, a second release is now waiting, and a third release will likely be ready before the current submission is reviewed. Has anyone experienced a new submission remaining in “Waiting for Review” for several days after withdrawing a previously approved build and submitting a newer build? If so, did it eventually move to review automatically, or was any action from Apple required? Thank you.

Hi everyone, I'm wondering if anyone else is experiencing unusually long App Review delays. My app has been in "Waiting for Review" since July 22 at 11:04 PM, and it still hasn't entered the review process. As of today, it's been nearly two weeks with no review activity. I understand that review times can vary depending on workload, app category, and other factors, but this is significantly longer than what I've experienced before. Has anyone else recently faced similar delays? How long did your app remain in "Waiting for Review"? Did it eventually get reviewed without taking any action? Did contacting Apple Developer Support help in your case? I'm mainly trying to understand whether this is a broader issue affecting other developers or if I should reach out to Apple Support. Thanks in advance for sharing your experience.

I paid the $99 annual Apple Developer Program membership fee and submitted my first iOS game, Pippin Plaza, for App Store review on July 21, 2026 at 9:54 PM. Apple publicly states that most app submissions are reviewed within approximately 24 to 48 hours. It has now been nearly 12 days, and my submission is still sitting in “Waiting for Review.” It has never entered “In Review.” There has been no request for additional information, no message from App Review, no explanation for the delay, and no indication that anyone has looked at the submission. I understand that review times can vary and that a first release may sometimes require additional time. However, nearly 12 days without even entering review is far beyond Apple’s publicly stated review timeframe and does not appear to be a normal delay. I contacted Apple Developer Support on July 29, 2026 through the App Review Status support category. Case ID: 20000122288868 Despite contacting support, I have still received no reply, no explanation, and no update regarding the submission. Developers are required to pay Apple $99 annually before they are allowed to distribute apps through the App Store. It is therefore reasonable to expect that a completed submission will at least enter the review process within a reasonable period, or that Apple will communicate when there is a significant delay. Is this currently considered normal for first-time app submissions? At what point should a developer conclude that a submission is stuck rather than merely delayed? Why has there been no response from Apple Developer Support since July 29, despite the submission already being delayed far beyond the stated review timeframe? I am not asking for special treatment, guaranteed approval, or an expedited review. I am asking for my completed submission to enter the review process, or for Apple to explain why it has remained untouched for nearly 12 days.

Hello, All of my submissions across my account have been stuck in review for many weeks, which is well outside my normal turnaround. These are apps that have historically been approved within 24 hours or 2-3 days. Those updates are time critical. Singapore MRT just updated on 12 July. We are losing installs and impressions largely because of this, especially no reason is given. App: Singapore MRT Map Route Apple ID: 536957287 / Version: 3.0.1 App: Singapore MRT Map Route(Pro) Apple ID: 475976737 / Version: 3.0.0 App: Epic Cards Battle Apple ID: 1003611640/ Version: 2.6.3 On my side everything appears complete: metadata, build, review notes, demo account credentials, and all agreements in Agreements, Tax, and Banking are accepted. There are no messages in Resolution Center and App Store Connect shows no action required from me. I have contacted Developer Support but have not received a actual response. Could someone please confirm whether these submissions are correctly queued, or whether something is blocking them that requires action on my side? Thank you.

Hello, I'm experiencing a serious issue with my Apple Developer account. Every app I submit stays in "Waiting for Review" for more than a month. This is not happening with just one app—it affects every app I submit. Here are the details: Every submission remains in Waiting for Review for over a month. The status never changes to In Review. I have already contacted Apple Developer Support. I also submitted an Expedited Review request, but the apps are still waiting. The apps fully comply with the App Store Review Guidelines and are complete and functional. At this point, I'm trying to understand whether there could be an issue with my developer account or if there is another reason causing all of my submissions to remain stuck in the queue. Has anyone experienced the same issue recently? If an Apple engineer sees this post, I would greatly appreciate any guidance or if my account could be checked. Thank you.

I'm looking for advice because I've been facing the same issue with every app submission on my Apple Developer account. Every app I submit remains in "Waiting for Review" for more than one month. The status never changes to "In Review", regardless of the app. Here's what I've already done: Contacted Apple Developer Support. Submitted an Expedited Review request. Waited well beyond the normal review timeframe. Verified that my apps are complete, functional, and comply with the App Store Review Guidelines. The problem is not limited to a single app. It affects every new submission and every app update I send for review. At this point, I'm wondering if there could be an issue with my developer account that is preventing my submissions from entering the review process. Has anyone experienced a similar situation? If so, how was it resolved? If an Apple engineer or App Review team member sees this post, I would be very grateful if someone could check whether there is an issue with my developer account or advise me on what I should do next. Thank you very much for your time and any assistance.

An unexpected error was encountered when submitting for review. If the issue persists please contact us I can no longer submit iOS app for review. Always show this error. I am using Safari latest version - 16.4 MacOS Version - Ventura 13.3.1 Xcode - 14.2 Appreciate any leads. Thank You!

Team ID: 63XFUNLKTY App: TabUp Build: 1.0.0(10) Submission ID: 43c1231c-7b80-44c6-91af-f45aff050530 -- It has now been more than 56 working business hours since I submitted my build for review, and the submission is still showing "Waiting for Review." My Agreements, Tax, and Banking information are all active, and all required metadata, privacy details, age rating, and export compliance information have been completed. I've also spent over two hours on hold with Developer Support without being able to speak to anyone or get an update on the status of my submission. I invested a significant amount of time building this app, and the lack of any progress, feedback, or estimated review timeframe has been extremely frustrating. As an independent developer, delays like this directly affect my ability to launch, gather user feedback, and begin generating revenue. I understand that review times can vary, but this delay seems unusually long compared with Apple's published expectations. Is there anything that could be causing a submission to remain stuck for this long? Any guidance from Apple or other developers who have experienced this would be appreciated. Thank you :)

Hi everyone, We're experiencing an unusually long App Review delay for our tvOS application and wanted to check if anyone else is seeing the same behaviour or has any suggestions. App Details Platform: tvOS Xcode Version: 26.4.1 Submission Type: App Update Distribution: App Store Status: In Review Issue We submitted an app update last week, and it remained in the "In Review" state for approximately one week with no updates. Since there was no progress, we rejected that submission, uploaded a new build, and submitted it again. The new build has now also been "In Review" for the last 5 days. Apple has not rejected the app or provided any review notes or requests for additional information. The status simply remains "In Review". What we've tried Submitted an Expedited Review Request. Contacted Apple using the App Review "Contact Us" option. We have not received any response to either request. Since there is no rejection or feedback, we don't have any indication that there is an issue with the app itself. Questions Is anyone else currently experiencing unusually long review times for tvOS apps? Is this likely to be an App Review backlog or a known issue on Apple's side? Has anyone had success getting a response through App Review support or Developer Support in a similar situation? Is there anything else we can do besides waiting? Any insights or recent experiences would be greatly appreciated. Thank you!

Hello Apple Developer Community, My app, Apple ID: 6794291305, has been stuck in the “Awaiting Review” status for 5 days now, which seems unusually long compared with the review times I normally expect. I understand that review times can vary and that some submissions may require additional time. However, I’m becoming concerned because we are approaching our marketed release date, and the prolonged review could affect our planned launch. There have been no requests for additional information or other updates regarding the submission so far. Has anyone experienced an app remaining In Awaiting Review for this long recently? Is there anything I should do at this stage, or is it best to continue waiting for the review team to complete the process? Any insight would be greatly appreciated. Thank you.