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, 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.

I use AES encryption on my app (it's a game), I encrypt the user data (JSON file) (levels / scores / etc...) This is how I answered the App Store Connect questions, not sure if it's correct:-Does your app use encryption? Select Yes even if your app only uses the standard encryption within Apple’s operating system. YES-Does your app qualify for any of the exemptions provided in Category 5 You can select Yes for this question if the encryption of your app is: (a) Specially designed for medical end-use (b) Limited to intellectual property and copyright protection (c) Limited to authentication, digital signature, or the decryption of data or files (d) Specially designed and limited for banking use or “money transactions”; or (e) Limited to “fixed” data compression or coding techniques NO-Does your app implement any encryption algorithms that are proprietary or not accepted as standards by international standard bodies (IEEE, IETF, ITU, etc.)? NO-Does your app implement any standard encryption algorithms instead of, or in addition to, using or accessing the encryption within Apple’s operating system? YESIs your app going to be available on the App Store in France? YESNow it's sending me to Encryption page - Add Export Compliance Documentation for ITC.apps.universal.platformName.iosIs your app designed to use cryptography or does it contain or incorporate cryptography? (Select Yes even if your app is only utilizing the encryption available within Apple’s operating system.) YESDoes your app meet any of the following: (a) Qualifies for one or more exemptions provided under Category 5 Part 2 (b) Use of encryption is limited to encryption within Apple’s operating system (c) Only makes calls over HTTPS (d) App is made available only in the U.S. and/or Canada NODoes your app implement any encryption algorithms that are proprietary or not accepted as standards by international standard bodies (IEEE, IETF, ITU, etc.)? NODoes your app implement any standard encryption algorithms instead of, or in addition to, using or accessing the encryption within Apple’s operating system? YES (it asks me to submit a copy of your French encryption declaration approval form- not sure what it is so I changed it to NO meanwhileClicked OK and then nothing happens. I'm not sure how to continue from here, In order to submit my app to test flight I need to provide export compliance information, which asks my the questions above, and then sends me to Add Export Compliance Documentation, but nothing was added ...

Hello, My app "Zen Mahjong!" has been stuck in the App Review process for an unusually long time and I’m trying to understand if something might be wrong with the submission. Timeline: First submission entered “In Review” and stayed there for 6 days without a decision. I rejected that build, uploaded a new build and resubmitted on February 17. Since then the app has been in “Waiting for Review” for more than 3 weeks. Additional context: App size ~40 MB Only IAP is a “Remove Ads” purchase I already contacted Developer Support and opened an expedited review request. Support also mentioned that this delay seems unusual. Has anyone experienced something similar or could this indicate that the submission is stuck in the review pipeline? Any guidance would be greatly appreciated. Thank you.

Hi everyone, I’m encountering a persistent issue with a visionOS app distributed through TestFlight for internal testing. The Problem: I have successfully archived and distributed the build as an Internal Test. The testers (including myself) received the invitation, accepted it, and the app is visible in the TestFlight app on Apple Vision Pro. However, the moment we click the "Install" button, an alert pops up saying: "The requested app is not available or doesn't exist." Context: Platform: visionOS (Targeting Vision Pro). App History: This is an ongoing project where the last distribution was about 5 months ago. The app has never been submitted for formal App Review or public release; it has only been used for TestFlight. Account Status: All agreements (including the Paid Applications Agreement) are active and in effect. What I have tried (but did not work): Re-uploading builds: Increased both version and build numbers and re-archived. Resetting Test Groups: Deleted the existing internal testing group, waited, and created a new group to re-invite testers. Tester Association: Removed all testers and re-added them to force a new invitation email. Device-side: Signed out and back into "Media & Purchases" on the Vision Pro. Key Observation: To determine if it was a project-level configuration error, I created a completely new App Identifier (Bundle ID) for the same project code and uploaded it as a new app record. In this case, TestFlight worked perfectly, and I could install the app without any issues. This leads me to believe that the original Bundle ID is stuck in some kind of "detached" or "stale" state on the App Store Connect backend. Has anyone experienced a specific Bundle ID being "corrupted" in the TestFlight system after a period of inactivity? Is there a way to force a full reset of the TestFlight status for an existing app record, or is this a backend bug that only Apple Support can resolve? Any insights or workarounds would be greatly appreciated.

Hi everyone, I’m encountering a persistent issue with a visionOS app distributed through TestFlight for internal testing. The Problem: I have successfully archived and distributed the build as an Internal Test. The testers (including myself) received the invitation, accepted it, and the app is visible in the TestFlight app on Apple Vision Pro. However, the moment we click the "Install" button, an alert pops up saying: "The requested app is not available or doesn't exist." Context: Platform: visionOS (Targeting Vision Pro). App History: This is an ongoing project where the last distribution was about 5 months ago. The app has never been submitted for formal App Review or public release; it has only been used for TestFlight. Account Status: All agreements (including the Paid Applications Agreement) are active and in effect. What I have tried (but did not work): Re-uploading builds: Increased both version and build numbers and re-archived. Resetting Test Groups: Deleted the existing internal testing group, waited, and created a new group to re-invite testers. Tester Association: Removed all testers and re-added them to force a new invitation email. Device-side: Signed out and back into "Media & Purchases" on the Vision Pro. Key Observation: To determine if it was a project-level configuration error, I created a completely new App Identifier (Bundle ID) for the same project code and uploaded it as a new app record. In this case, TestFlight worked perfectly, and I could install the app without any issues. This leads me to believe that the original Bundle ID is stuck in some kind of "detached" or "stale" state on the App Store Connect backend. Has anyone experienced a specific Bundle ID being "corrupted" in the TestFlight system after a period of inactivity? Is there a way to force a full reset of the TestFlight status for an existing app record, or is this a backend bug that only Apple Support can resolve? Any insights or workarounds would be greatly appreciated.

I'm trying to understand why App Preview uploads are stuck in this state even after 24 hours without any errors thrown My current video has the following specs which follows Apple requirements for Video Specifications for App previews. Video codec: H.264 High Profile Level 4.0 — meets requirement Resolution: 886×1920 — correct for 6.9" Frame rate: ~28.9 fps (under 30) — meets requirement Format: MP4 — meets requirement Duration: 28.08s (under 30s) — meets requirement Audio codec: AAC — meets requirement Audio bitrate: 256kbps — meets requirement Audio sample rate: 44.1kHz — meets requirement Audio channels: stereo — meets requirement

I removed TestFlight app from old device (email is no where exists in AppStore connect in Testers) which has different email than my AppStoreConnect email. Now I am trying to get invitation to the device which has same email as my AppStoreConnect, but keep getting -> Couldn't Load App The apple Account you're currently signed in with, , doesn't match the one assiciated to this invitation. You can sign in to TestFlight with original Apple Account, , or request a ne…. Where as all other apps in the AppStore connect shows up fine in the TestFlight using appstore connect email. Followed all the reset & settings mentioned but no luck so far.

Hello everyone, I’m facing an issue with my app submission being stuck in “Waiting for Review.” I initially submitted my app on 21 February and waited until 27 February, but the review process did not start and there were no updates. On 27 February, I contacted Apple Support regarding this issue, but I did not receive any response. Since there was still no progress, on 4 March I removed the app from review and resubmitted it again, but it is still showing “Waiting for Review.” This delay is affecting my operations, so I would really appreciate any guidance or help if someone has experienced a similar situation. App ID: 6741708449 Thank you.

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, I’m experiencing a delay with the App Store review process and wanted to check if this is normal. My app was initially approved very quickly (within a few hours after submission). However, shortly after that I noticed a few minor UI bugs, so I fixed them and submitted a new build. The new version has now been waiting for review for about 5 days, and there has been no update since submission. I also want to mention that I have already contacted Apple Developer Support twice about this issue but have not yet received any response. Previously the review happened very quickly, so I’m wondering if something might be wrong with the submission or if this delay is expected.

Hello, I am facing a validation error when uploading a macOS app with a Network Extension. The Error: Invalid system extension. The system extension at “[T] TEXT.app/Contents/Library/SystemExtensions/company_name.network-extension.systemextension” resides in an unexpected location. The Problem: Validation fails only when the app's Product Name contains square brackets: [T] TEXT. If I remove the brackets from the Product Name, validation passes. What I've tried: Setting Product Name to TEXT (without brackets) and CFBundleDisplayName to [T] TEXT. Cleaning Derived Data and rebuilding the archive. Verified that the extension is physically located at Contents/Library/SystemExtensions/. It seems the Apple validation tool fails to parse the bundle path correctly when it contains characters like [ or ]. Question: How can I keep the app name with brackets for the user (in System Settings and Menu Bar) while ensuring the Network Extension passes validation? Is there a way to escape these characters or a specific Info.plist configuration to satisfy the validator?"

I submitted a software update for one iOS app several days ago. It was approved two days ago. I received a message about distribution that said The status of your app has changed to Ready for Distribution I happened at the iTunes Connect website at that very moment in order to submit a totally new iOS app to the App Store. Its status said 'Removed from App Store.' I thought it was a rare mistake. Unfortunately, it's not. The one that I was submitting was approved some 15 minutes ago. I received the 'Ready for Distribution' message by email. Yet, it's been removed from the store as you see in the screenshot below. As you see in the 2nd screenshot below, it says that it's Ready for Distribution. But it's not? So is this a new norm? And we have to go back the iTunes Connect website to change the app status every time we submit a software title and then get it approved?

Hello. Despite making my membership payment (and accidentally twice!), my membership is still not activated even after 62 hours. I contacted their support system but received no response. Does anyone have any suggestions?

Hello, I have multiple iOS app updates (for already live apps) that have remained in “Waiting for Review” status since early February (approximately 4–5 weeks). These are standard updates (minor improvements / maintenance). All builds are properly attached, agreements are active, and there are no compliance or metadata warnings in App Store Connect. The apps were moved to “Waiting for Review” on February 6–11 and have not progressed to “In Review” since. Has anyone else experienced unusually long review times for updates recently? Could this indicate a queue issue at the account level? I have already contacted App Review Support and one of the submissions was marked for expedited review approximately one week ago, but the status remains unchanged in “Waiting for Review.” Thank you in advance.

Hello everyone, I am an iOS developer and both my apps are experiencing an unusual App Store review delay that I have not been able to resolve through the normal support channels. These are existing apps on app store with simple updates. It has not moved to “In Review”, and I have not received any rejection message or request for additional information from the App Review team. AppleID: 6756242440 and 6746870245 Please help us resolve the issue. Thanks in advance

Hi, my app has been stuck in Waiting for Review for 18 days. I contacted you via your contact us link a week ago, and haven't heard back. Overall I'm very disappointed by your inability to communicate The app ID is 6758786767

Hello, I am facing a validation error when uploading a macOS app with a Network Extension. The Error: Invalid system extension. The system extension at “[T] TEXT.app/Contents/Library/SystemExtensions/company_name.network-extension.systemextension” resides in an unexpected location. The Problem: Validation fails only when the app's Product Name contains square brackets: [T] TEXT. If I remove the brackets from the Product Name, validation passes. What I've tried: Setting Product Name to TEXT (without brackets) and CFBundleDisplayName to [T] TEXT. Cleaning Derived Data and rebuilding the archive. Verified that the extension is physically located at Contents/Library/SystemExtensions/. It seems the Apple validation tool fails to parse the bundle path correctly when it contains characters like [ or ]. Question: How can I keep the app name with brackets for the user (in System Settings and Menu Bar) while ensuring the Network Extension passes validation? Is there a way to escape these characters or a specific Info.plist configuration to satisfy the validator?"

Hello everyone, I am an iOS developer based in South Korea, and I’m currently experiencing an unusual App Store review delay that I have not been able to resolve through the normal support channels. My app has been stuck in “Waiting for Review” for more than two weeks, and there has been no progress at all during this time. It has not moved to “In Review”, and I have not received any rejection message or request for additional information from the App Review team. App Information Platform: iOS App Name: WOOTA Apple ID: 6759412826 Status: Waiting for Review Submission Date: February 20, 2026 Developer Account Region: South Korea What I Have Already Tried: I have already attempted the following steps: Submitted an inquiry via App Store Connect → Contact Us → App Review Received a response from Developer Support saying they understand my concern and that they contacted the review team However, since then there have been no updates at all. The app status remains “Waiting for Review”, and there are no messages in the Resolution Center. Questions I would appreciate any insight into the following: Is it normal for an app to remain in “Waiting for Review” for more than two weeks without any status change? Are there any recent delays in the App Review queue that could cause this kind of situation? Is there any other support channel I should try in order to get more information (for example phone support or another ticket)? Is it possible that some hidden issue with my account or metadata could cause the submission to remain stuck in “Waiting for Review”? What I Verified I double-checked the following: All required metadata fields are completed Screenshots and app information are properly filled The status shows “Waiting for Review”, not Metadata Rejected or Missing Information There are no messages in the Resolution Center Previous versions of the app were approved without issues Concern I am worried that the submission might be stuck somewhere in the review queue or blocked for an unknown reason. This update contains important improvements and fixes for existing users, so the long delay is quite concerning. If anyone has experienced a similar situation recently, I would really appreciate your advice. If any Apple staff member happens to see this post, I would be extremely grateful if you could help check whether there is any issue with this submission. Thank you very much for your time and assistance. Best regards, Lee Yuchang

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. Apple ID: 6758804549 Thank you.

Dear App Review Team, I hope you are well. I am writing to respectfully follow up on my recent submission (Dev ID: 1770951123), which has now been in “Waiting for Review” status for approximately 12+ days. Currently, four of my applications are in a similar state, including one update for an app that was previously approved without issue. Given my past experience, reviews have generally been completed within a reasonable timeframe. While I fully understand that review times may vary depending on workload, the extended duration in this case has raised some concern. I previously submitted an expedited review request and opened a support case (Case ID: 102832785901). However, I have not yet received any response regarding the status of the review or the case. To better understand the situation, I would sincerely appreciate clarification on the following points: Whether there are any issues or flags currently preventing the review process from proceeding Whether any additional information or documentation is required from my side Or whether the submission is simply pending assignment to a reviewer I completely understand that the App Review team may be experiencing a high volume of submissions. Nevertheless, given the duration and the number of affected apps, I would be very grateful if someone could kindly review my case and advise on the current status. Thank you very much for your time and assistance. I look forward to your response. Kind regards, Lovesoft