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

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hi, I was wondering about Apple's review queues. I have an app that in waiting for review for almost a week now but review time trackers claim average waiting times less than a day: https://www.runway.team/appreviewtimes My previous experience is also quite inconsistent, can you please shed some light on how things work internally? In this time I have done some improvements on the app that I was considering for the next update, should I cancel and re-submit?

Hello App Review Team, I'm hoping someone can take a manual look or point me in the right direction. The iOS build of my app has been sitting in "Waiting for Review" with no status change, while the macOS and tvOS builds of the exact same version have already been reviewed and released. App: VixioTV - IPTV & M3U Player App ID: 6763137740 Platform: iOS (iPhone/iPad) Current status: Waiting for Review Most recent submission: [June 24, 2026] Time in queue: ~24 days with no status change Related case IDs: [your expedited review / Developer Support case numbers] Context I'd like to share proactively: This is an update to an app that is ALREADY LIVE on the App Store (current iOS version 1.2). It is not a new app. The macOS and tvOS versions of this same update have already passed review and are live — only the iOS build is stuck. VixioTV is a bring-your-own-content player: it provides no broadcasts or content of its own. Users connect their own IPTV subscription (API credentials or an M3U URL). There is no registration, subscription, or content sale inside the app. I have submitted expedited review requests and contacted Developer Support, but I've only received generic/automated replies with no change in status. I would really appreciate it if someone could: Confirm whether there is any issue with the build, metadata, agreements, or account that requires action on my side. Indicate whether this is queue congestion or a submission-specific hold. If possible, escalate or trigger a manual review. Thank you very much for your help. Selcuk Kaymaz

Hi, I added two new auto-renewable subscriptions to an existing subscription group: 50GB Monthly 50GB Yearly The other subscriptions in the same group (200GB and 500GB monthly/yearly) have already been approved. However, these two new subscriptions have remained "In Review" for over 3 days without any updates. Is this normal, or could the review be stuck? Has anyone experienced the same issue? Thanks!

Hello, Our app has been in "Waiting for Review" status for more than a week, and our previous submission also took over a week to be reviewed. This delay is affecting our planned release schedule. App details: App name: Nhật Luân Kiếm App ID: 6777269196 We'd really appreciate any guidance on the current review timeline, or whether there is anything on our side we can do to help move the review forward. We're happy to provide any additional information if needed. Thank you very much for your time and support. Best regards.

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!

I'm building a custom keyboard extension that offers voice dictation. Because keyboard extensions are constrained (memory cap ~30–48 MB, restricted audio session access), I delegate recording to my container app: User in a host app (e.g., Safari) taps the mic in my keyboard extension. The keyboard calls extensionContext.open(URL("myapp://dictation")) to launch the container app. The container app records audio via AVAudioEngine + SFSpeechRecognizer, writes the final transcript to the App Group, and signals completion via a Darwin notification. 4. The user is expected to be returned to the original host app (Safari) automatically so they can keep typing. The problem (step 4): On iOS 26.4 I can no longer identify which app was the host. Every previously-known path returns nil for the keyboard extension's host: parent.value(forKey: "_hostBundleID") → returns the literal string parent.value(forKey: "_hostApplicationBundleIdentifier") → returns NSNull xpc_connection_copy_bundle_id on the underlying XPC connection (via PKService.defaultService.personalities[…]) → returns NULL NSXPCConnection.processBundleIdentifier on extensionContext._extensionHostProxy._connection → returns nil proc_pidpath(hostPID, …) → EPERM from the keyboard sandbox LSApplicationWorkspace.frontmostApplication → selector unavailable from the extension RBSProcessHandle.handleForIdentifier:error: → returns an RBSServiceErrorDomain error Without the host's bundle ID, the container app has no way to call LSApplicationWorkspace.openApplicationWithBundleID: (the technique that worked on iOS 25 and earlier). UIApplication.suspend() correctly sends the container to background, but iOS treats us as a "fresh launch" — it returns the user to the Home Screen instead of Safari, because the container app was launched by an extension, not directly by Safari. KeyboardKit's maintainer reached the same conclusion (issue #1014) and shipped 10.4 without the feature. My questions: Is there a public, App-Store-safe API in iOS 26+ for a custom keyboard extension to identify its host application, or for the container app (launched via the extension's openURL) to identify which app initially hosted the extension that opened it? UIOpenURLContext.options.sourceApplication reports the extension's own container, not the actual host. 2. Is there a public mechanism for "return to source app" when the container app was launched by an extension's openURL? Equivalent to the ← Source affordance iOS shows for normal inter-app openURL, but triggered programmatically by the launched app. 3. Some popular keyboards (e.g., 微信输入法 / WeChat Keyboard) still appear to round-trip through their container app on iOS 26.4 and return the user to the original host — including the iOS ← WeChat back affordance in the host's status bar afterward. What's the recommended approach to achieve this? If it requires a specific scene-activation flow, NSUserActivity pattern, or extension-context configuration, please point at the relevant docs. 4. If there is no public path today, is FB22247647 (or a related radar) the right place to track this? Should developers in this position migrate to in-extension audio capture (which has its own significant constraints in keyboard extensions)? I'd much rather not rely on private APIs. Concrete guidance — or even an acknowledgment of which direction Apple intends — would help thousands of custom-keyboard developers who currently have a degraded voice-input experience on iOS 26.4+. Tested on iPhone 12 Pro Max running iOS 26.4.2 (build 23E261), Xcode 26.x, Swift 5. Thanks!

Details: I'm looking for clarification on how Guideline 1.4.3 is applied to tobacco related apps. My app, The Leaf Cellar, was rejected under 1.4.3 with the reasoning that its "current concept is not appropriate" because it relates to tobacco. The app is a private inventory manager. It has no store, no purchasing, no vendor or affiliate links, no discovery feed, and no content directed at encouraging or using tobacco. its only function is personal record-keeping (logging inventory you already own, aging dates, humidity readings). A 21+ age gate is enforced on launch. What I'm trying to understand is the consistency of the guideline, because functionally identical apps are currently live on the store and receiving updates (which means apple must approve the submitted updates.) Existing Apps (not being enforced by 1.4.3): "My Humidor – Cigar Journal": [https://apps.apple.com/us/app/my-humidor-cigar-journal/id6639582700] "Humidor Journal Pro": [https://apps.apple.com/us/app/humidor-journal-pro/id6751737114] Questions: Is there a specific feature or distinction that separates an approvable cigar-journal app from one rejected under 1.4.3 as a "concept"? If apps in this category are already approved, what's the correct path to have an inconsistent rejection reviewed beyond the standard Resolution Center reply? I have already submitted to the App Review Board.

Hello, my app id 6756081224 Waiting for Review 10 day ago Help me please

Hi all, My first app submission appears to be stalled (16+ days) and I’m completely in the dark as to what is going on. Apple ID: 6776835006 Submission ID: 236039a0-1668-448a-aae6-486d52e6c5b9 Timeline: Ready for Review: Jun 10, 2026 at 3:22 AM Waiting for Review: Jun 10, 2026 at 3:23 AM In Review: Jun 15, 2026 at 5:05 PM Current status: still In Review as of Jun 26, 2026 I have also submitted 2 support cases that are past 48 hour SLA and an expedited review request, but I haven’t received a response yet. Our TestFlight external build has also been stuck in Waiting for Review for 5+ days now. There are no visible unresolved issues, App Review messages, or missing compliance warnings in App Store Connect. Review notes and demo/testing information are provided. Thank you.

Hello Apple App Review Team, I hope you are doing well. I am writing again to respectfully request a priority review for our app. Our submissions have been waiting in review for more than 3 weeks, without receiving a final review decision. During this time, we have continued to submit updates with important bug fixes and improvements, but we have been unable to release them to our users due to the extended review delay. In addition, we have made more than five attempts to contact Apple Support regarding this issue, but unfortunately we have not received any response to our tickets. The requests appear to remain unanswered, with no follow-up or resolution provided so far. This situation is now significantly affecting our users, as critical issues that have already been fixed are still present in the live version. Each additional day of delay continues to impact the user experience. We fully understand and respect the App Review process and workload. However, given that the waiting period has now exceeded three weeks and there has been no response from support despite multiple attempts, we kindly ask if our latest version of our app could be prioritized for review. For reference, our Apple Developer account / Apple ID is: 6475698369 We would greatly appreciate any update or assistance your team can provide regarding the status of our submission.

Hello, I am looking for advice regarding an unusually long App Review delay. Our app, Bien App (ID: 6769135685), has remained in "Waiting for Review" status since June 13, 2026 without any review activity or communication from App Review. Some additional context: The app is a financial services application. We have already submitted updated builds. We have opened support cases with Apple. The app has not entered "In Review" at any point. There have been no requests for additional information. What makes this situation particularly confusing is that our related application, Bien Plus, was submitted under the same developer account during this period and has already completed review and been approved. Because Bien Plus has already been reviewed and approved, we know that our developer account is in good standing and that our financial services business model has already been reviewed by App Review. At this point, Bien App has been sitting in "Waiting for Review" for several weeks. Has anyone experienced a similar situation where an app remained in "Waiting for Review" for an extended period while other apps under the same account continued through review normally? If so: Did Apple eventually review the app? Did you need to escalate through App Review Support? Did withdrawing and resubmitting help? Was there ultimately a queue issue or another explanation? Any advice or similar experiences would be greatly appreciated. Thank you.

Hi App Review, An update to an app that's already live on the App Store has been in "Waiting for Review" for 10 days with no status change, and I wanted to check whether it's proceeding normally or whether anything is required from my side. Submission ID: b4e5d54c-de30-4003-9f3c-232e366d01c4 Version: 1.1.0 (build 7), an update to a live app (1.0.0 currently in production) Submitted: 16 June 2026, 22:10 Current status: Waiting for Review (has not moved to In Review) I've already checked the usual things my end: there's no message in Resolution Center, no "action required" banner on the app or version page, the build shows as valid and is correctly attached to the version, export compliance/encryption is answered, and Agreements, Tax, and Banking are all current. I also contacted Developer Support via the contact form on 23 June [add: case #102923511308 if you have one] but haven't had a reply yet. Could you confirm whether the review is proceeding normally, or let me know if there's anything I need to do? Happy to provide any further detail. Thanks.

Hi all, Our app has been in review since November 1st, and the process has been very slow. We often wait several days between responses, and we keep receiving questions we’ve already answered - even when we point this out in our replies. We’ve contacted Developer Support by email, but the only reply we received was that they’re sorry for the delay and will look into it. We’re unsure whether requesting a phone call might help or if it could pause or reset the review process, and since we’re hoping the next response will finally approve the app, we’ve hesitated to use that option. Has anyone experienced something similar, or does anyone know whether requesting a call has any impact on the current review status? Thanks for any guidance.

Hello everyone, I am facing a severe issue with my app's review process and urgently need some guidance or advice on how to resolve this bottleneck. Current Situation: Our latest version has been stuck in the "Waiting for Review" status for the past 10 days. Yesterday, after reading some community advice, I used "Cancel Submission" and re-submitted the build to try and refresh the queue. Unfortunately, it is still completely stuck in the exact same "Waiting for Review" status with no progress. Past History: This seems to be an ongoing issue with our account. For our previous versions, the App Review team took an incredibly long time—between 1 to 1.5 months for each submission—only to ultimately issue a rejection. We have already tried sending 5-6 standard support requests and even requested an expedited review 3 times, but we have received absolutely zero response or feedback from Apple. It feels like our app or account is stuck in some sort of dead-end queue. Has anyone else experienced such extreme delays just waiting for the review to start? Is there any alternative way to escalate this to a human specialist at Apple who can check if there's an account-level glitch? App Store URL: https://apps.apple.com/uz/app/fonus-kids/id6742020368 Thank you in advance for any insights or help!

Hello App Review Team, I’m writing this as a last resort after 3 weeks of an exhausting and costly review process for our app Hook — Smart Message Assistant (iOS 1.0.0). Full timeline: • May 3: First submission • June 4: Rejected (marketing language) • June 4: Resubmitted with all fixes • June 8: Rejected (Guideline 3.1.2c — subscriptions) • June 9: Resubmitted with every issue fully addressed June 17: Rejected (Guideline 2.1a — app crash + sign-in bug) • June 17: Resubmitted same day with critical fixes • June 23: Resubmitted again with additional bug fixes • Today: Still “Waiting for Review” — no movement, no communication We have submitted 4 expedited review requests — all approved. We have contacted Developer Support multiple times. Every time we are told “it will begin shortly.” It never does. Business impact: We have a contractual launch deadline and active paid marketing campaigns running. Every week of delay costs us thousands of dollars in direct losses. We have already lost over $10,000 in sunk marketing costs and missed revenue. We have addressed every single issue Apple raised — promptly, thoroughly, and without complaint. We are not asking to skip the process. We are asking for someone to actually look at our submission and tell us if something is blocking it. Apple ID: 6766006483 This is not a normal delay. This is 3-4 weeks of a small team’s work being held hostage with no explanation. Thank you.

Hello, I am looking for a better understanding of Guideline 1.4.2, which states that "Drug dosage calculators" must be developed by drug manufacturers, hospitals, universities, or other approved entities. My main question is: What is Apple’s exact definition of a "Drug Dosage Calculator"? - Does the term exclusively refer to apps that calculate dosage (dose, interval, and treatment duration)? - Are apps that do not make clinical decisions, but only display bibliographic references based on user-entered data, also considered Drug Dosage Calculators? - If an app only performs basic mathematical operations on a dose value entered by the user, without suggesting medications or treatments, does it still fall under this restriction? I would like to better understand how Apple differentiates a medical support app (which only presents data) from a dosage calculator (which makes clinical decisions). I appreciate any insights from the community!

1 week and still no answer and response from apple. i have submitted my new application and ” they say ”, we will get back to you in 48 hours. guys ! its more than 48 hours!! i have been waiting for 1 week. how can i get their attention! I raised a case ID and still no one reply to me !!!!!!! i need a solution ! Why they are treating me like this ? instead of raising a ticket and knowing that i will get a solution, i pray to god every night that I don’t want any issue with my application to not deal with this circle all over again!

Hello, My app has been stuck in the review pipeline for nearly one month, which seems very unusual to me App ID: 6767853355
 Bundle ID: com.ttm.photocleaner
 Timeline: Submitted, waiting for review: May 28, 2026
 In Review: since June 9

 I also submitted a support request via the Contact Us form on June 15 but have not received any response. 
Could you please verify if this submission is correctly queued or if there is an internal issue blocking the review ?
 Thank you