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.

I am looking for some guidance regarding a significant delay in the review process for my app update. Platform: iOS Submission Date: February 10, 2026 Current Status: Waiting for Review It has now been 16 days, and the status has not progressed to "In Review." I have checked my App Store Connect "App Review" section, but there are no outstanding requests for information or messages from the review team. I have already attempted to contact the App Review team via the official "Contact Us" form but have only received generic automated responses. Is anyone else experiencing similar delays this month? Are there currently known backlogs, or should I consider canceling this release and re-submitting? Thank you for any insights.

When creating the marketing/promotional material for my app, I reviewed many popular apps to see what was permitted and accepted to the app store. I saw many apps like headlines and image content of text saying "Quit Porn" or similar. Upon submitting my app for review, it was later rejected and one of the reasons was having titles and texts in the marketing saying "Quit Porn". Why is this? (The app is an app to quit porn addiction)

I realize there are already several posts here about the unusually long review times for app submissions. There are some replies from Apple stating that they are looking into it or that specific issues have been resolved, but the problem persists and no one seems to understand what is actually happening or what can be done to improve the situation. I have been experiencing the same issue over the past six weeks. My app (submission ID: 75aed892-ee07-49e1-b62b-fdd54f1b04f8) was rejected because the reviewer stated that it needed “citations, such as links to resources.” I therefore added citations with functional links to online resources directly on the page where the claims were made, yet my app was rejected again with exactly the same copy-and-paste feedback. I then asked for clarification, but my question has remained unanswered for a week. There seems to be a fundamental problem in the App Store review process. For me, it has become a cumbersome issue, as the unexpectedly long response times are causing me to miss deadlines with my customers. We fix and resubmit our app within minutes, literally, but every time we have to wait weeks for the next reply from Apple. Should we pause submissions for a while and focus on other activities, and manage expectations with our customers accordingly? Or is this a temporary situation that is likely to improve soon? Any insights or tips would be much appreciated. Thank you.

Hello, I would like to raise a concern regarding the review status of my apps. Both of my submissions have been in the “Waiting for Review” stage for an extended period of time. Additionally, I have sent multiple support emails and even submitted an expedited review request. Unfortunately, I have not received a single response to any of them. As a long-time Apple developer and someone who genuinely values the Apple ecosystem, I find this prolonged silence concerning. Extended waiting periods without any feedback create uncertainty and negatively impact the overall developer experience. I fully understand that review times can vary. However, the lack of communication is the primary issue here. Even a brief status update would be greatly appreciated. I sincerely hope the review process moves forward soon and that we can resolve the current “Waiting for Review” situation as quickly as possible. Thank you for your time and consideration. Best regards, Berkay

More than 2 week's ago submitted 3 apps, and it's still stuck on "In Review" status with zero updates. No updates in statuses. No updates from email support Apple Team. We create some tickets on support tab, but no updates from Apple Team. Apple’s review process usually isn’t this slow, so I’m starting to wonder if something’s broken on their end… Would appreciate any insights or updates from others who’ve managed to get through this too!!! Can you please help us to resolve this issue?

Hello, I am writing to ask for assistance regarding two of my apps that have been stuck in “Waiting for Review” for an extended period. At the moment: App ID 6497716649 — Waiting for Review since Feb, 19 at 11:45 AM App ID 6743224713 — Waiting for Review since Feb, 15 at 10:26 PM There are no warnings, Resolution Center messages, or visible issues in App Store Connect. All Agreements, Tax, and Banking information are active and up to date. The builds were uploaded successfully, and no further action appears to be required on my side. Could you please help confirm: Whether there is any hidden blocker or account-related issue? Or if this delay is currently due to review queue processing times? If additional details are needed (bundle IDs, app category, sign-in requirements, encryption/export compliance, etc.), I will be happy to provide them immediately. Thank you very much for your time and support. Best regards,

Hello, I have a policy-related question regarding App Store Review for dating apps. As a development agency, we build apps based on client requirements. Recently, we received feedback from App Review stating that the dating app category is saturated and that the app should demonstrate unique features to avoid being considered spam or a duplicate of existing apps. In such cases, what is the recommended approach for developers working on client projects? If a client requests a standard dating app with common features (profiles, matching, chat, etc.), is it likely to be rejected under the spam/duplicate guideline (4.3)? Should developers proactively advise clients to include clearly differentiated features before submission, even if the app is functionally complete and complies with technical guidelines? Any clarification on how App Review evaluates dating apps for uniqueness under Guideline 4.3 would be very helpful. Thank you.

After nearly ten years in Android development, I finally built a native iOS app, sharing the journey publicly while learning Swift and SwiftUI, using AI selectively, and finding the platform familiar yet different in tooling, concurrency, and culture. I reached production without initially buying a developer account and faced a stricter, iterative App Store review process than the Play Store, with several rejections that ultimately clarified Apple’s quality standards and expectations.

I’ve been building iOS apps since 2011, took a 4-year break, returned with two new apps, and it feels like organic visibility and indexing have changed drastically compared to earlier releases. Has anyone else noticed slower indexing, fewer automatic mentions, and almost zero organic traction—has discovery changed, or is it just saturation?

When creating a new App Store version to update ASO keywords and metadata, I notice that elements like the app icon and other details are missing and I am looking for a way to copy the existing metadata from the previous version. Also, is it possible to submit a new App Store version solely for ASO improvements without uploading a new build and still have the changes applied successfully.

I take a lot of screenshots such as tickets, ideas, chats, and receipts, but I often forget about them later, so I am considering building an iOS app that asks the purpose of a screenshot as soon as it is taken, lets you assign it to a category, and reminds you after a set number of days to turn screenshots into actions instead of clutter. Before starting development, I would love to know if this feels genuinely useful, whether you would consider paying around $2 per month for it, and what features you would like to see, as I truly appreciate any honest feedback.

One of my apps has been stuck in “Waiting for Review” for the past 21 days. App ID: 6758734829. I have contacted other support channels over the past few weeks but have not received any response. I also have three additional apps, App IDs 6758755469, 6759047311, and 6759095185, that have been in review for the last 14 days. All of these apps have already been live on the Google Play Store for months. I am trying to launch them on the App Store so I can move forward with my marketing plans. I kindly request Apple to review these submissions and help resolve whatever is causing the delay.

Hello Apple Review Team, I am writing to inquire about the review status of my two apps, which are still in the “Waiting for Review” stage: Healthoria: Health Diary – Submitted on Feb 5 at 7:01 PM OrbitGoals – Submitted on Feb 17 at 4:11 PM Could you please provide an update on the expected review timeline? I want to ensure there are no issues or missing information delaying the process. Thank you for your assistance. Best regards, Berkay

I'm not sure where to go from here, I've filled in the "appeal" form but had no response. My app has somehow been interpreted to 'only work with specific hardware' - this is not the case it works wither either specific hardware OR a third party piece of software (which is freely available) The third party software provides a TCP server and my app connects to it as a client. I have been rejected four times now because I haven't provided a 'video to show the paring process with the dedicated hardware' There isn't a 'pairing process' any more than there is a pairing process between Safari and a website or Mail and an IMAP server, it literally connects to the specified IP and Port. I've provided a video of this (showing a screen capture of the software in question, and a screen capture from an actual iOS device - my iPhone - showing me connecting to the other application in the app, and demonstrating the functionality of the app - but keep being told I need to provide a video with hardware. I don't own the hardware version, I use the software version. It's exactly the same process and software whether it is running on hardware or software.

Hello everyone, I am facing a very frustrating situation and wondering if anyone else has experienced this or if an Apple engineer can help. My app (App ID: 6756897429) has been stuck in "Waiting for Review" for 13 days (since Feb 12). I had a previous rejection for a Guideline 5.2.1 (Trademark) issue. I completely fixed it, uploaded a new build, and submitted it for review. Since then, total silence. I have tried: Opening a ticket (Case ID: 102820782519) -> No response. Sending follow-up messages via Contact Us -> No response. Uploading a new build to "wake up" the system -> Still stuck in Waiting for Review. I am not asking to skip the line; I just want to know if my app is stuck in a system glitch because 13 days of silence is not normal. Can any Apple representative here please check my App ID or escalate this? I am totally blocked.

Hello everyone, My app (ID: 6758039899) was submitted on Feb 17, 2026, and has been stuck in "Waiting for Review" status for over 8 days. I contacted Developer Support (case #20000108234172) and received confirmation that it's proceeding normally, but no update since. On average, Apple reviews 90 percent of apps within 24 hours. However, there might be cases that need more review time, but mine exceeds a week. Any recent experiences with long queues? Thanks!

New version of our App was uploaded 2 days before. Still it is in waiting for review, not yet available for testing. It is just a minor version that is being updating to. No major changes have been included as part of the new release, still it is taking high time even for getting the build available for testing. Please expedite the process.

Has anyone else experienced extremely long wait times for app review or know what I can do to help expedite this process? I am waiting 22 days currently I have done everything I have seen to do both sending an email and calling Apple support for help to have nothing changed or even a confirmation email of my call sent. Does anyone have any advice?

Hi, it's been almost 3 days since I submitted an app update for review. Is anyone else also experiencing such a long waiting for review time ? It's the first time in years this has happened

Has anyone experienced all review delays? We usually get reviewed very fast or within 24 hours. Our last version was stuck in "waiting for review" for 6 days. We resubmitted a newer version yesterday and it's been stuck in the same status. I know apple has introduced a new app submission UX, maybe that's the issue? Anyone is having same delays?