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, My new app has remained in the "Waiting for Review" status for an extended period. I initially submitted it on January 23, 2026. After several days without any progress, I submitted an inquiry on January 27 but have not yet received a response. On February 1, I canceled and resubmitted the app, wondering if there might have been an issue with the review queue, but it still remains in the "Waiting for Review" state. I had scheduled my marketing activities based on the typical review timeframe, but since the review has not started and there is no indication of how much longer the wait will be, it has been difficult to adjust my plans accordingly. If anyone has experienced a similar issue and managed to resolve it, I would greatly appreciate any insights you could share. Thank you for your time, and I hope you have a great day.

I am trying to submit my app for review but when I click on the 'add to review' button, I am getting the message: Unable to Add for Review The items below are required to start the review process: There are still screenshot uploads in progress. However, there is nothing I am uploading... I tried removing all screenshots, nothing works. It has been 4 days, I cant update my app on the app store... impossible to get any response from Apple... Any inputs will be greatly appreciated.

Hello Apple Staff and Community, An important update for my app has been unexpectedly stuck in "Waiting for Review" for 9 days (submitted on February 9th). This is not a new app, but an update to an existing one. • App ID: 6756239914 We have an active marketing campaign tied to this specific update. Deadlines are failing, leading to daily financial losses. I already submitted an Expedited Review request through the Contact Us form but have received absolutely no response or movement. Could an Apple representative please help investigate if this update is stuck due to a system glitch and escalate it to the review team? Thank you.

I’m sharing my situation in case others have experienced something similar. I initially submitted my app for review on February 4, and it remained in “Waiting for Review” for over 12 days without any feedback or request for additional information. I also sent a message through App Store Connect on February 11, but did not receive a response. To help move things forward, I’ve now resubmitted an updated build with clearer onboarding, improved permission explanations, and some minor UI improvements. I included detailed notes for the reviewer explaining the changes. I’m staying patient and cooperative, but I wanted to ask if others have encountered similar delays recently, and whether resubmitting helped unblock the review. Thanks in advance for any insights 🙂

Hello everyone, I submitted my app USDT Miner – Rig Manager to App Store Connect on February 2, and it has been in “Waiting for Review” status since then. I understand that review times can vary, but it has now been several days without any status change or feedback. This is my first submission for this app, and there are no resolution center messages or rejection notices so far. I wanted to ask: Is this delay normal at the moment? Are there any known review backlogs or factors that could cause an extended “Waiting for Review” status? Is there anything recommended to do from the developer side, or should I simply continue waiting? Any insights from Apple staff or fellow developers who’ve experienced similar delays would be appreciated. Thank you.

Hello everyone, I submitted my app USDT Miner – Rig Manager to App Store Connect on February 2, and it has been in “Waiting for Review” status since then. I understand that review times can vary, but it has now been several days without any status change or feedback. This is my first submission for this app, and there are no resolution center messages or rejection notices so far. I wanted to ask: Is this delay normal at the moment? Are there any known review backlogs or factors that could cause an extended “Waiting for Review” status? Is there anything recommended to do from the developer side, or should I simply continue waiting? Any insights from Apple staff or fellow developers who’ve experienced similar delays would be appreciated. Thank you.

I had to create a new version (26.01.1) for my app in order to provide updates to the age ratings prior to the end of January, 2026. The problem is that this version wasn't production/release ready, but nonetheless I created this version to answer the updated age ratings. I now have a production ready version (26.02.1), but I do not see any way to cancel/delete this current version in order to create a new version with the 26.02.1 build I've uploaded. What are my options? Must I submit 26.01.1 for review and distribute it and then I will see the + icon to be able to create a new release?

Hello, I’m looking for guidance regarding a new app submission that has been in “Waiting for Review” status for 6 days now, with no change or additional communication. This is a brand-new app submission (not an update). There have been no metadata changes or rejections — it has remained in the waiting state since submission. I completely understand that review times can vary depending on workload and complexity. I just wanted to check whether this timeframe is currently normal, or if there may be something specific I should verify on my end. The app is an educational medical application, and all content is original. There are no unusual entitlements, external payment systems, or restricted APIs involved. If anyone from Apple or fellow developers has insight into whether extended “Waiting for Review” times are currently common, I would appreciate your input. Thank you in advance.

I needed to change the bundleid in my app, so I created a new app and used the build I created with the same source code and deleted my old app completely, but my app is rejected for spam

Hello everyone, I wanted to check if anyone else has experienced longer App Review delays recently. Our recent app submission has been in the “In Review” status for more than 7 days (since Jan 15, 10:44 PM). In our previous submissions, reviews usually started or completed within a few days, so this delay feels unusual. Current situation: No messages or rejection notes from Apple No metadata or compliance issues flagged Status remains “In Review” without updates I’d appreciate guidance from the community: • Is this type of delay normal these days? • Could this indicate a manual or extended review? • At what point should we contact App Review directly? • What is the best way to contact App Store / App Review support regarding a stuck review? If anyone has faced a similar delay and can share their experience or advice, it would be very helpful. Thank you in advance for your help.

Good day, I've uploaded a build to TestFlight, but received an automated response with the following error: ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. Our project started in Objective-C and have mixed swift class and pods. The last uploaded build without any automated response was Nov 8, 2023. I'm using XCode Version 26.0.1 (17A400). I've tried every way i found in internet and i'm not able to find any solution for this. ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES = YES use_frameworks! :linkage => :dynamic (in pods) We would appreciate any assistance in clarifying why this issue is occurring and how we should proceed to address it. Your guidance would mean a lot. Thank you.

Hello!! I wasn't able to find a feedback form anywhere so I'm hoping this could reach the team that made the submission form for the challenge. I was really hoping the form could save our progress. Working on the longer response questions does take time, and it's incredibly frustrating when the site tends to reload, losing all progress and causing me to copy everything over again.

I understand that private APIs are not permitted under Apple’s App Review Guidelines. However, our application requires I²C communication, and we are currently using the following APIs: IOAVServiceReadI2C IOAVServiceWriteI2C IOI2CSendRequest.These api's are not permitted by apple. I didnt found any alternative public api to achieve I²C communication. please suggest any public api's for the same or any chance to use this private api.

We submitted a build to testflight and received a confirmation email it was successfully uploaded. When we open testflight on our iPhone's (X, 6s) we get a message of "Could not install appname" "The requested app is not available or does not exist" Where appname is the name of the app. Its very confusing because I can see the build listed in testflight on my mobile device and can view it in iTunes connect. I also can't install prior builds that had worked successfully when I try.

Dear App Review Team, Our app – Apple ID 6756967338, has been stuck in the “In Review” status for over 10 days (Jan, 19 at 1:33 PM). Normally, reviews begin within a few days, but in our case, it seems unusually delayed. Could you please clarify: • Is there a specific reason for this hold? • Is any action required from our side? • When can we expect the review to finish? Thank you very much for your time and assistance.

90809: Deprecated API Usage. New apps that use UIWebView are no longer accepted. Instead, use WKWebView for improved security and reliability. Learn more (https://developer.apple.com/documentation/uikit/uiwebview). I did not actively use UIWebView in my app, but this error occurred during the build upload process. This version has an additional integration of the iOS Ayla SDK and Public-9.0.7 SDK compared to the previous version. If there is indeed a call in a third-party SDK, how can I determine where the call exists? Thank you

Hi everyone, Just wanted to ask if anyone else has noticed longer-than-normal review times recently. Our latest app has been sitting in “In Review” for more than a week now. Normally our apps get reviewed much faster, so we’re unsure if this is just a backlog or something else. Currently: No communication from Apple No visible issues in metadata Review status hasn’t changed Curious to know: • Are others seeing similar delays? • Does this usually mean a deeper/manual review? • When should we reach out to Apple? • How do you usually contact App Review for status checks? Would love to hear your experiences. Thanks!

I received this message "Your app provides a limited user experience as it is not sufficiently different from a web browsing experience." It needs to be more robust and native. When submitting this the app had: Push Notifications Core Location Phone Contact access So now I am adding: Haptic feedback Quick touch actions A more robust add to calendar function. (the app does scheduling) But is this enough for resubmission? I am not really sure what is considered "robust" and "more native".... that is vague.