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

Hello Apple Developer Support, My app has been stuck in “Waiting for Review” since February 7, and I have submitted multiple inquiries without receiving any response. This delay has now become extremely concerning. Missing a planned launch due to an indefinite review timeline is very difficult for independent developers. If there is an issue with the submission, I would appreciate clear communication. If there are review delays, transparency would help us plan accordingly. I respect the review process, but the lack of updates after this amount of time is frustrating. I would sincerely appreciate clarification on the status. I kindly ask for a specific and personalized response regarding my case, as my previous inquiries received only general or automated replies without addressing the actual issue. Thank you.

Hello App Review Team, We respectfully ask for your assistance regarding our app review status. Our submission was re-submitted on April 29, 2026, and it has now been waiting for review for more than 12 days without any update or response. In addition, we have already been working through the review process for this app on this developer account for almost 4 months. We carefully addressed all previous review feedback and submitted the required fixes, but the review process continues to experience very long delays. This situation is now seriously impacting our planned product launch, business operations, and partner commitments. We sincerely ask if the App Review Team could please help: Review the current submission status Escalate the case internally if possible Help move the review process forward Reference Information: Case Number: 102877213113 Submission ID: 68850cef-1651-40c8-b717-7916b679a467 We would greatly appreciate any assistance or update regarding this matter. Thank you very much.

Hello, I'm hoping someone from the App Review team can look into this situation, which has specific context that I believe makes it worth a careful look. Thank you in advance for your time. I'm hoping someone from the App Review team can look into this situation, which I believe has specific context that makes it worth a careful look. My app YADA: You've Already Met (App ID: 6759586097) has been in "Waiting for Review" since Wednesday May 6 at 7:44 PM ET - now over 96 hours. I have an open support case (20000112508151) filed Friday with no response yet. I'm not writing simply to flag the wait - I want to explain why this submission deserves a thoughtful second look on the merits. When YADA was submitted for TestFlight beta review, it was flagged under Guideline 4.3(b) for the same reason as the App Store rejection. I appealed, explained the differentiating mechanic, and an Apple reviewer evaluated the argument and approved the app for external testing. That approval is on record. I'm asking for consistency with that prior decision. YADA's core mechanic is genuinely unlike any dating app currently on the App Store. A user privately adds someone they already know to a list. That person receives no information about who added them. A match is only revealed when both people have independently and privately added each other. If the feeling isn't mutual, nothing is ever disclosed. There is no browsing of strangers, no algorithmic recommendations, no swiping, and no rejection possible because neither party knows they've been added until both have added each other simultaneously. Critically, YADA does not ask users to declare their gender or sexual preferences - because the mechanic doesn't require it. This makes YADA the only interest-discovery platform on the App Store that works entirely without those declarations, which creates a uniquely safe experience for LGBTQ+ users and young people who are not ready to publicly disclose their orientation. No equivalent experience exists on the App Store. The App Store rejection also included 5.1.1 and 2.1 issues, both of which I fully resolved - redesigning the contacts permission flow with a proper in-app explanation screen and directly answering Apple's question about data handling - with a new build submitted alongside my Resolution Center reply. I'm not asking for special treatment. I'm asking for the opportunity to have the full argument evaluated by a reviewer with the time to consider it, consistent with how the TestFlight review was handled. Support case: 20000112508151. App ID: 6759586097. Submission ID: abdf8b5b-5ea0-46a4-8a0b-fb58320fa701. Thank You

Hello, I'm reaching out regarding my app AUREX (App ID: 6761672161), which has been in "Waiting for Review" status for 17 days with no movement or communication from App Review. Submission details: App: AUREX AI — Investment Portfolio & Crypto Tracker Version: 1.0 (Build 17) Status: Waiting for Review since April 24, 2026 Category: Finance Support Case: 20000111960192 (opened 13 days ago, no response received) Context: All agreements, tax, and banking information are active. There are no messages in the Resolution Center, no warnings, and no visible issues in App Store Connect. The build was uploaded successfully and no further action appears to be required on my side. I understand that review times can vary and that the queue may currently be experiencing higher-than-usual volume. I'm not trying to escalate — I simply want to confirm whether: There is any specific issue or blocker with this submission Any additional information or documentation is required from my side Or whether the app is simply still pending reviewer assignment I would sincerely appreciate it if someone from the App Review team could take a look. Thank you very much for your time.

My app has been released, and there is an "App Clip" link available in the advanced experience. Could someone please tell me if there is a way for me to modify or delete this link? (I'm not looking to deactivate the link; I just want to remove it so that other apps can use it.) If I remove the already published APP, can I also delete this link?

I'm hitting a persistent build/upload failure when trying to submit my first app for review. Hoping someone has seen this specific issue. Setup App: ShiftSelf (an AI-guided self-coaching app) Bundle ID: app.shiftself.mobile Apple Developer account: active, paid, fully verified (Switzerland) App Store Connect: app created, Version 1.0 in "Prepare for Submission" Build pipeline: Expo-based (using a hosted Expo build service for the IPA upload) The error Every upload attempt fails with: exportArchive Error: Downloading App Information This has now occurred 14 times over the past 5 days, with no configuration changes between attempts. What is already configured correctly Two auto-renewable subscriptions (Monthly $9.99, Annual $59.99) — both in "Ready to Submit" state Subscription Group with English localization ("ShiftSelf Pro") created Both subscriptions attached to Version 1.0 under In-App Purchases and Subscriptions Privacy Policy URL, Terms URL, and Account Deletion URL all live and reachable DSA verified, Banking and Tax information active App icon, screenshots, and metadata all uploaded Age rating questionnaire completed (4+) App Privacy answers fully submitted No pending agreements in Account → Agreements, Tax, and Banking What I have already tried Recreated the subscription group localization Detached and reattached subscriptions to the version Multiple rebuild attempts at different times of day and across multiple days Verified all metadata fields are filled Apple Support engagement Currently working with Apple Developer Support (Case #102880953484). Guidance so far: Subscriptions must be "Ready to Submit" → done Subscriptions must be attached to the version → done Both confirmed. Builds still fail with the same error. Questions for the community Has anyone else seen "exportArchive Error: Downloading App Information" specifically during the metadata fetch step of an automated upload? Is there a known App Store Connect API issue that causes the metadata download to fail silently for first submissions? Would uploading the IPA manually via Apple Transporter bypass this step entirely, or does Transporter rely on the same metadata fetch? Is there any way to get more verbose logs on what specific "App Information" the export step is attempting to download? Any pointers from anyone who has hit this would be hugely appreciated. Happy to share more details if useful. Thanks 🙏

Hi to you all, I have a problem with setting up a subscription for an app for the first time. I keep getting a rejection with the message under Guideline 2.1(b) that “one or more of the In-App Purchase products have not been submitted for review.” I don’t know what to add anymore. I only have two monthly subscriptions. I set them up and selected them in the version description and submitted the package. There‘a not more information what exactly is missing. The only other information is the following: “Note you must provide an App Review screenshot in App Store Connect in order to submit In-App Purchases for review.” I’d be glad to get some advice.. Thank you in advance for your help!!

Hi I uploaded the zenweb mac app for review in TestFlight and it was rejected - after that I uploaded a new version - which was reviewed and approved. Since then all version I upload (TestFlight or App Store) are displayed in TestFlight but the Distribution - App Review is displaying only the link to the first app that was rejected. I have no way of submitting to app to review before publishing. Opened a cse with apple - 102876729124 - received a response from SB - to which I answered on 30 April 2026 since then - nothing - we re keen to deploy, Safari is lagging after Chrome and Edge solution now.

My app has been rejected two times. The latest reply from Apple is provided below. "Issue Description The app provides loan services but the domains listed on the app's Product Pages are not clearly under your control or ownership. Since users may use these domains to contact you to request support, the domains used on the Product Page for loan apps must be under your control or ownership. Next Steps Update the Product Page metadata in App Store Connect to only include domains that you both own and are used as email domains for Apple Accounts registered to your developer account. You can review the email domains and Apple Accounts registered to your developer account in the Users and Access section of App Store Connect. Account Holder and Admin users should use emails with domains that identify the company providing loan services. Please note that apps used for financial trading, investing, or money management should be submitted by the financial institution performing such services, as required by App Review Guideline 3.2.1(viii)." Any suggestion?

Hello everyone, my initial app release (Version 1.0) has been stuck in the 'Waiting for Review' status for 6 days now. It is a comprehensive app that includes localization for 14 different languages. I understand that initial submissions and extensive localizations can take longer to review, but 6 days seems unusually long. Is anyone else experiencing similar extended delays with App Review recently? Any insights would be appreciated. Thank you.

Hello, I am seeking advice or assistance regarding a significant delay in the review process for my app, Preppy (App ID: 6443527187). The app has been on the App Store for over 4 years and has been featured as "App of the Day" on three separate occasions. We have always maintained a good standing, but we are currently facing an unprecedented bottleneck that is negatively impacting our users. The Timeline: Version 2.6: Approved successfully ~3 weeks ago. Version 2.6.1: Submitted shortly after to address a critical bug. It was rejected due to the screenshots (which were the same as in 2.6), but I changed them according to the feedback. It remained in review for another 7 days. Even after requesting an expedited review, there was no movement anymore. Action taken: I rejected the build and resubmitted with a new build and updated screenshots again, hoping it would help. It sat for another 5 days with no status change again. Phone Support: I spoke with support via phone and was advised to increment the build/version number and resubmit and was told the app is in the expedited queue, so it will be reviewed shortly, which did not happen. Version 2.7: Uploaded 4 days ago with a new version number, updated screenshots yet again, and an improved description. It has been stuck in "Waiting for Review" since then. I have sent multiple emails to the App Review team explaining that this update contains a critical bugfix. Because of this delay, we are now receiving a wave of negative 1-star reviews from users who are experiencing the bug that is already fixed in the pending build. I have had no response to my follow-up emails, and the "Contact Us" forms haven't resulted in any updates. Has anyone else experienced this recently with a long-standing app? Is there any other way to escalate this beyond the standard expedited review form (which has already been used)? Thank you for any help or guidance.

Hi everyone, I’m looking for some guidance regarding my app review status. About a week ago, I submitted my app for review on the App Store. The review team responded asking for some declarations and a few changes in the app. I addressed all the requested changes and resubmitted the app promptly. However, it has now been more than a week since the resubmission, and I haven’t received any further updates or feedback from the review team. The status still appears unchanged, and there has been no communication. I understand that review times can vary, but I wanted to check: Is this delay normal after a resubmission? Is there anything I should do from my side (e.g., follow-up, resubmit again, contact support)? Has anyone else experienced similar delays recently? my app name is Darenite Any insights or suggestions would be really helpful. Thanks in advance!

The In-App Purchases and Subscriptions section is missing from my version page despite having a build attached and subscriptions in Waiting for Review status. This is the same bug reported in Developer Forums thread 820936. I need this escalated so my version 1.0.5 build 6 can be submitted with my subscriptions.

I have a submission that has been stuck in “Waiting for Review” significantly longer than expected, while other apps submitted from the same developer account during the same period were reviewed and approved quickly (under 2 days). Current pending submission App Store Connect ID: 6760300948 Waiting for Review - Mar 9, 2026 at 4:50 PM Related history (previous record for the same app functionality) App Store Connect ID: 6759011698 Status history: Waiting for Review - Feb 11, 2026 at 1:22 AM Developer Rejected - Feb 28, 2026 at 10:18 AM Ready for Review - Feb 28, 2026 at 11:31 AM Waiting for Review - Feb 28, 2026 at 11:31 AM Developer Rejected - Mar 9, 2026 at 3:13 PM I withdrew that earlier submission out of frustration after attempting to reduce review friction (first by changing metadata/review notes, then by withdrawing it altogether). The current pending submission (ID 6760300948) uses very conservative metadata and includes demo mode to allow straightforward testing. Can the App Review team check why submission ID 6760300948 is not progressing from “Waiting for Review”, and advise what the problem is or what information is needed to move it forward? Related similar thread: https://developer.apple.com/forums/thread/782319

I have a new dosing App, and I am currently facing submission issues and need help navigating it. My app helps with calculating a specific drug (Vancomycin) dosing. I am not affiliated with any organization, so I listed it under "Education", with the disclaimer "For Educational use only". I got the following message regarding issues with my submission: "Guideline 3.2 - Business Issue Description We found in our review that the app is intended to be used by a specific business or organization, including partners, clients, or employees, but you've selected public distribution on the App Store in App Store Connect. Since the App Store is intended for apps with a public audience, we recommend reviewing the other distribution options available to you through your Apple Developer Program Account. If you believe our assessment is incorrect and the app is intended for a general, public audience, clarify why in your response to the questions provided below. Next Steps If the app is intended for use by a specific business or organization, review the other distribution options available for apps designed for specific businesses or organizations and choose a distribution option that works for the app and users. You can review these app distribution options on Apple Developer. If you believe the app is intended for a general public audience, review the following questions and provide as much detailed information as you can for each question: Is the app restricted to users who are part of a single company or organization? This may include users of the company's partners, employees, and contractors. Is the app designed for use by a limited or specific group of companies or organizations? If yes, which companies or organizations use this app? If not, can any company or organization become a client and utilize this app? What features in the app, if any, are intended for use by the general public? The general public refers to a wide range of users who can discover, download, and use an app without invitation, pre-approved registration, or affiliation with a specific organization. How do users obtain an account? Is there any paid content in the app and if so who pays for it? For example, do users pay for opening an account or using certain features in the app?" Does anyone have an experience with building such an app? How do I navigate this issue? Thanks. Joy

Our app PrepAiro: Crack UPSC IAS 2026 (Account: 6741750813) has been caught in a rejection/resubmission loop since April 12, now over 10 days. Timeline: April 12: First rejection received Cycles 1–6: Each rejection addressed per reviewer feedback, resubmitted promptly April 18: Status moved to "Waiting for Review" , no movement since We submitted an expedited review request through Apple Support due to the urgency. This release contains critical bug fixes actively impacting users, but there has been no response or update. We understand review timelines can vary, but 6 full cycles over 10 days with no resolution, and a 6-day stall after the last submission, is unusual. Each resubmission addressed the specific feedback provided, yet the cycle continues. Has anyone experienced similar extended holds recently? And is there any additional channel or escalation path beyond the expedited review request to get clarity on what's causing this? Any guidance from Apple or fellow developers would be appreciated.

App Review stuck/stalled — Khalas (App ID 6757966927 Version 1.0.5 - ESCALATION) My app has been blocked in review far longer than usual, and previous channels have not resolved it. My app has an error and I need to roll back and release a fix and I can't because of this review problem. App Name: Khalas Apple ID (App Store Connect): 6757966927 Bundle ID: com.khalas.mobile.khalasapp2 Platform: iOS Team ID: AW8RAKXM5P Submission / review Version submitted for review: [1.0.5] Build number: 19 Current status in App Store Connect: In Review and previously stuck in “Waiting for Review” for over a week Total time in review pipeline: Over 7 days What I’ve already tried Requested Expedited App Reviewl Contacted Developer / App Review support Confirmed there are no unanswered messages in Resolution Center and no missing metadata on my side that I can see. Ask Please look up this submission by App ID 6757966927 and tell me whether: The review is actually active or blocked internally (queue, metadata sync, IAP attachment, etc.), There is a silent hold, duplicate submission, or binary processing issue, Anything specific you need from me (I’ve included identifiers above to avoid back-and-forth). I rely on this CRITICAL release and I’m doing everything I can on my side. I’m asking for a concrete status and, if possible, forward progress on this submission. Thank you

Hi everyone, I am writing this post with the hope that someone from Apple's App Review team, Developer Relations, or the wider developer community can shed some light on what I am experiencing. I have exhausted every official support channel available to me, and I am at a complete loss. ━━━━━━━━━━━━━━━━━━━━━━━ THE SITUATION ━━━━━━━━━━━━━━━━━━━━━━━ I have a v1.0 iOS app that has been stuck in 'Waiting for Review' for 57 days. It has never progressed beyond this status. No rejection. No feedback. No communication. Just silence. I am not here to complain. I am here because I genuinely do not understand what is happening, and I need guidance. ━━━━━━━━━━━━━━━━━━━━━━━ TIMELINE ━━━━━━━━━━━━━━━━━━━━━━━ • Day 1 — App submitted for review. Status: 'Waiting for Review.' • Day 22 — No movement. No feedback. Out of frustration, I made the mistake of doing a Developer Reject and resubmitting. I now understand this was the wrong decision, as it likely reset my position in the queue. • Day 27 — Contacted Apple Developer Support. A Senior Advisor confirmed the app was still in review and said they would reach out to the internal review team. • Day 42 — Still no change. Sent a formal follow-up and escalation request. • Day 44 — A second Senior Advisor responded, confirming they had also forwarded the case to the review team. • Day 57 (today) — The app is still in 'Waiting for Review.' Nothing has changed. Two separate Senior Advisors have each told me they contacted the internal review team. After both of those interactions, nothing changed. ━━━━━━━━━━━━━━━━━━━━━━━ WHAT MAKES THIS UNUSUAL ━━━━━━━━━━━━━━━━━━━━━━━ I want to be clear about something: the app has NEVER entered 'In Review.' It has been in 'Waiting for Review' the entire time. This is not a case of a slow review — it appears the app has never been picked up for review at all. I have checked Apple's System Status page multiple times throughout these 57 days. All services have consistently shown as fully operational. I have not resubmitted again after Day 22. I have been patiently waiting, following the advice given to me. ━━━━━━━━━━━━━━━━━━━━━━━ MY HONEST QUESTIONS ━━━━━━━━━━━━━━━━━━━━━━━ Is it technically possible for a v1.0 app to be permanently stuck in 'Waiting for Review' without any notification or rejection? Could this be a system or queue issue on Apple's end? Is 'Waiting for Review' for 57 days — with no status change and no communication — within the range of what other developers have experienced? I want to understand if this is abnormal. When a Senior Advisor says they have 'forwarded the case to the review team,' what does that actually mean in practice? Is there a way to verify this happened or to escalate further? Is there a formal escalation path beyond Developer Support — for example, Developer Relations or the App Review Board — for situations where standard support channels have not produced any result after nearly two months? Could the app category (social / matching) be the reason for an extended manual review? If Apple requires additional information, documentation, or content moderation policies from developers in certain categories, why is there no notification or communication mechanism to request this? ━━━━━━━━━━━━━━━━━━━━━━━ WHAT I AM NOT ASKING FOR ━━━━━━━━━━━━━━━━━━━━━━━ I am not asking for my app to bypass the review process. I am not asking to skip the queue. I am not asking for guaranteed approval. I understand Apple's review process exists to protect users, and I fully respect that. I am simply asking for ONE of two things: — Either: review the app and give me a decision — approval or rejection, both are acceptable. — Or: tell me if there is a problem, a hold, or something you need from me, so I can act on it. Fifty-seven days of silence, with no path forward, is the one outcome I cannot work with. ━━━━━━━━━━━━━━━━━━━━━━━ A NOTE TO APPLE DEVELOPER RELATIONS ━━━━━━━━━━━━━━━━━━━━━━━ If anyone from Apple is reading this — I am not writing out of anger. I am writing because I am a solo developer who has poured everything into this product, and I am genuinely stuck. I have done everything I was asked to do. I have been patient. I have followed the process. All I am asking for is a resolution — in any direction. If there is anything I can provide — demo account credentials, additional documentation, a content moderation policy, privacy details, anything at all — I will provide it within hours of being asked. Thank you sincerely to anyone who takes the time to read this and share their experience or advice. — Akif Solo Developer

Our app update for Underground Arena (a padel sports community platform) has been pending review for over (65 days), since the first submission on February 11, 2026. At no point has the submission transitioned to "In Review" or received any feedback. The previously approved version (v1.1.2) was reviewed and approved within one day. This update includes security improvements, privacy policy alignment, and metadata updates. No changes to monetization or permissions. We have submitted two expedited review requests and opened support case 102840575585 — none have resulted in movement. We have a padel tournament on April 22, 2026 that requires the updated app for participant registration. Our Android version is already live on Google Play, and iOS users are currently unable to access the latest features. Could someone from the review team please confirm whether this submission is in extended review, or advise on any information needed to proceed? Thank you.

Hi, we have an app which used DeviceID to track users. We had implemented ATT and setup our privacy declaration in ASC accordingly. Now in our new version we decided to not track users anymore. We removed NSUserTrackingUsageDescription, removed ATT permission code and submitted the new version. Now, reviewer has complained that our privacy declaration in ASC still says we are tracking users and refused app acceptance. They told us to update the privacy declaration in ASC. We tried to do so, but ASC does not allow us to remove device ID tracking. It is showing a warning that our app still uses NSUserTrackingUsageDescription and in fact that is true for the production version. We are now in a chicken egg problem. We can't change our privacy declaration in ASC because the production version still uses the feature AND we do not get the new version accepted as long as our privacy declaration is not changed. How can we fix that ? Pls advise !