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

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.

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

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 !

Hello, I have a perplexing issue with apple reviewers not having the same experience as myself regarding the paywall. This is an Expo app and uses RevenueCat and SuperWall integrations. This app is going through its first review - it is not published yet. So the app and its subscriptions are being reviewed for the first time. I should also mention that this is my first time as an app developer, so please pardon my ignorance. When I install the app from TestFlight and launch it, I see the paywall with the product prices shown and I can complete a test purchase. Same for my friends who I've asked to test for me. But the apple reviewer does not see the product prices when the paywall is shown to them. Without being able to replicate the problem I am flying blind. I don't want to re-submit the app for review only to find the same problem exists. I also need to understand what is different between my testing environment and the apple testers. If anyone can point me in the right direction here I would really appreciate the help!

My current app is a smoking cessation app and it is desgined to help people quit smoking for good. Currently users of the app are expected to set a quit date and then remain quit from cigarettes for 12 weeks. The app helps with this by using badges, notifications and even live chats to stop smoking professionals (depending on your area). The app "frequently" mentions smoking and tobacco, but it never promotes it. It does the opposite. By mentioning the harms of smoking and the benefits of stopping. The app also mentions (and can provide, depending on your area, medical history and a professionals final opinion) about nicotine replacement therapy, which users who are quitting smoking may be interested in. Currently the app is rated 18+ as I have to tick "frequent" mention of drugs/tobacco/alcohol in the age rating questionnaire. Though it does not mention recreational drugs or alcohol. We will soon be adding a large update to the app to add vaping support. The app will change largely in the fact smoking content and vaping content will be siloed from each other. So a user can either be on a smoking support journey (and see stop smoking content), or a vape support journey (and only see vaping content). We need the app to be 13+ on the store and we will enforce age restrictions using the declared age range API as part of the account creation process. If the user is aged 13 - 17, they will only see vape related content, if they are 18+ they can see vaping OR smoking. How negotiable is the age rating certificate, can we change it to 13+ if we implement age restrictions in the app and protect stop smoking related content behind it?

ID 6758008521, Dear App Review Team, I submitted my app review and it got rejected for inaccurate screenshot. I have revised the app screenshot and also resubmitted. But it has been 8 days and no response. We look forward to completing the review, thank you.

My support case has stalled despite being escalated to a Senior Advisor over a week ago with no follow-up or resolution. My application is being rejected from the App Store due to what appears to be a synchronization issue between apple.developer.com and App Store Connect. Full Timeline March 24, 2026 — My account migration from Individual to Organization was completed and approved by Apple. March 27, 2026 — My app (Version 1.0, Submission ID: 72b19231-8010-4844-b873-f2853d02092e) was rejected under Guideline 3.1.5 on an iPad Air 11-inch (M3). The rejection stated my app was submitted under an Individual account, which is not permitted for fintech applications. March 28, 2026 — I submitted a support request explaining the situation. April 6th, 2026 — I received a response from Developer Support, who acknowledged the issue and escalated it to a Senior Advisor. April 7, 2026 — I followed up via email as no Senior Advisor had contacted me. Today, April 13, 2026 — Still no contact from the Senior Advisor. App Store Connect still shows my account as Individual. Core Issue: When I go to apple.developer.com my account membership type is organization, with all relevant company details. However, my membership type in AppStore Connect still reflects an individual account. Such is demonstrated by an App Store review response: "Your wallet app facilitates the transmission and/or storage of a virtual currency but was submitted by an Apple Developer Program account registered to an individual, which is not appropriate for the App Store. Your app must be submitted through an Apple Developer Program account enrolled as an organization." What I Need A manual update of my Appstore Connect membership type such that it correctly reflects my Organization account status; allowing me to resubmit my app. Relevant details: Case Number: 102854501693 (screenshots of issue provided in case details) If any Apple staff can help escalate this internally or advise on next steps, I would be incredibly grateful.

We recently ran into an issue where our submission was rejected due to references to an API that we are not using but that was present in the code. Guideline 2.5.1 - Performance - Software Requirements Issue Description The app uses the Clinical Health Records API but the app does not appear to include any primary features that require the Clinical Health Records API. Next Steps To resolve this issue, please remove the Clinical Health Records API from the app, as well as any references to this app’s interactivity with Clinical Health Records from the app or its metadata. And as it turns out, we actually did have references to that API that we had missed and did have to remove them. Usually, I would recommend to just resubmit the new build and see if it gets accepted, then hold it until the powers that be approve it for publication. For this client, though, their QA team forces us into more of a waterfall-ish approach, where we are not allowed to submit production builds ahead of time (i.e. until after all manual testing has concluded, test evidence has been filed and the required documents have been updated and approved). And if after resubmission we find something else that needs to be fixed, we get to restart the process all over again. That's ... slower. We do have a workaround in place where we submit a development build for review and check whether that would get accepted, then retract that version and submit the production build once we are allowed to. But that means more work for Apple (the App has to be reviewed twice) and more risk for us (if the submission team accidentally publishes a development build, the consequences would be severe). Is there a tool that allows us to check for guideline violations without having to submit a build to the App Store Connect? I'm not looking for a "yes, this will get approved" kind of guarantee, just a "well, the review team may find something else to question / reject, but as far as automated checks go, this looks ready for submission".

When I sign into App Store Connect, I am taken to this URL: https://appstoreconnect.apple.com/review_agree The page shows a gray activity spinner for a few seconds, then is blank. I have tried on multiple computers and multiple browsers, over the past few weeks, with the same result. I have lodged a developer support request, but it hasn’t been resolved yet. It’s been holding up our App Store submission for a couple of weeks now. Any ideas of things I could try, or has anyone else had this issue and had it resolved ?

Hi everyone, I’m dealing with a strange App Review delay and would appreciate any advice from people who faced something similar. My app was released on January 20. A small update was approved quickly on January 28, and another one on January 29. So far everything looked normal. Then I submitted another update on February 6. This submission stayed in “Waiting for Review” for 3 weeks with no progress. During that time, I contacted Apple Support to ask if something was wrong with my submission or the review queue. The response took quite a while, and since nothing was changing, I assumed the queue got stuck. So I decided to remove the update and resubmit it. Later Support replied and told me that I removed my own update, and that the queue was working normally and there was nothing I needed to do. However, even after resubmitting, the new build stayed in the same “Waiting for Review” status all the way until March 19 — with no signs of movement. At this point I started to think maybe the review team found some critical issues that would block the app from going live. I rechecked the entire app, didn’t find anything serious, but fixed a couple of small bugs and submitted another update. Unfortunately, this update is now also stuck in “Waiting for Review.” Additionally, I requested an expedited review on April 6, but haven’t received any response or changes in status. So at this point I’m not sure what else I can do. Has anyone experienced something similar? Is there anything that helped you unblock a submission stuck in this state? Any advice or shared experiences would be greatly appreciated.

Hello, My app has been approved on March 14, 2023 and has the status "Ready for sale" ever since. But the app is still not available on App Store, and whenever i use the link in App Connect to view on App Store it says "App Not available. This app is currently not available in your country or region". Initially I made the app only available in my country, after few days of getting that error, I made it available worldwide but still can't seem to find my app being available. I've sent a support ticket to apple a few days ago but got no reply. In the approval email it said it may take up to 24 hours for the app to be available on App Store, but few days have passed and still not available on app store. The app is free, and i checked all the countries and regions for availability. What can be the problem, how long does it take? Thank you

We are planning to distribute our app outside of TestFlight because our testing period exceeds the 90-day limit. Since we have an Apple Developer account, we are considering using Unlisted App Distribution for long-term testing. I have a few questions regarding this approach: After completing testing via Unlisted Distribution, is it possible to switch the same app to a public App Store release, or would we need to create and submit a separate app for public distribution? If a separate app is required, are there any restrictions from Apple on releasing essentially the same app under a different bundle identifier through another distribution channel? (Additionally, once testing is finalised, we plan to discontinue the Unlisted App version.) Are there any potential complications or limitations we should anticipate (e.g., app review concerns, versioning, or policy compliance) related to this matter? Any guidance or best practices in this matter would be greatly appreciated.

Hi folks, I had a similar issue I was able to replicate without fail: Public beta submission fails with: "Beta app contract is missing" POST /iris/v1/betaAppReviewSubmissions returns 422 Error: TF_BETA_APP_REVIEW_RESPONSE Internal TestFlight installs fail with: "The requested app is not available or doesn't exist" Adding apps to beta review also fails I was unable to: Add builds to public testing groups Submit builds for TestFlight review Reliably update TestFlight metadata ("What to Test", etc.) The fix: filed via Feedback Assistant (not Developer Support email). Included a HAR capture of the failing request and response headers, also provided all affected App IDs (even though this was account-wide). Got traction within a couple days after filing, much faster than waiting on Developer Support. Note: In my case this affected every app on the account. From what I’ve seen, this may be triggered by changes to tester groups (adding/removing testers), but this is not confirmed. Seems to be a backend contract/entitlement desync Apple-side. Hope this helps someone.

Hello Apple App Review Team, and everyone, I am in a gap. I cant solve it. 2 days ago I received a copyright claim ref# APP264502-A As a 5 years experienced ASO professional, I choose and position keywords based on volume and relevancy. I didnt know that the keywords was copyrighted. After I received the App Store Notices email, I have took immediate action to prepare a new build to update the app title. I want to remove the copyrighted keyword. Now, because of this copyright claim, Apple put my account under "Pending Termination" status. Don't get me wrong, I can send the app to the review. But this status is blocking the app from going into App Review. Submission ID: 49f886fb-7d5e-4493-b7e8-5e5db2ab1e18 This is where I am stuck. The gap. the loop. I received copyright claim. Okay, of course I will remove your keyword. I need review to change app title. I cant get my app a review. I have created tickets, I replied all of the emails. I need help. This situation makes me stress a lot. I understand that companies or people can get copyrights. I respect that. And I move forward accordingly. I am willing to co-operate. Help needed. Thank you. Best regards,

I have a macOS App Store app with a lifetime non-consumable IAP. I can’t do a normal App Store app transfer, so the app will be re-released as a new app under a different Apple Developer Team. That means users’ old purchases won’t automatically carry over. I want to let existing customers keep their lifetime access in the new app, but I want to do it in an Apple-approved way and avoid anything that would look like a custom license-key unlock flow. A few questions: Is there any Apple-supported way for the new app to recognize a user’s purchase from the old app? If not, is the safest App Review-compliant option to make the new app’s equivalent IAP temporarily free or discounted? Would a custom migration/recovery flow for prior customers be allowed, or would that likely violate 3.1.1? Has anyone handled this kind of migration before? Thanks.

Hi everyone, I am experiencing an issue with App Store Connect and subscriptions. My app (Couple Organizer, App ID: 6748842796) already has an approved subscription group (Premium Plans) with Monthly and Yearly Premium options. Version 1.0.0 is live in the App Store, subscriptions are working. But - When preparing version 1.1.0 for submission the “In-App Purchases and Subscriptions” section is not visible on the submission page so I am unable to attach them to the new version of the app. I tried removing the build from review and re-adding another one but the section still does not appear. Subscriptions show status approved and ready for sale . My questions: Are subscriptions automatically carried forward to new app versions once approved in the first release? Or is there a step I’m missing to explicitly attach them again in every new version? Is this the expected behavior, or is it a bug in App Store Connect UI? Screenshots available if needed. Any advice would be appreciated!

I am unable to submit my app EggZap for review. When I navigate to my iOS App Version 1.0 submission page, I can make all edits and save successfully — screenshots, description, keywords, contact info all save without issue. However, as soon as I add a build to the submission and click Save, the button turns red with a ! error indicator and will not save. Removing the build allows the page to save normally again. The build (Build 51) is fully validated and shows as Complete in TestFlight. It is fully playable via TestFlight on my device. I have tried multiple browsers on multiple devices with the same result. Browser console shows a 409 Conflict error from the PATCH endpoint when saving with a build attached. I have already contacted Apple Developer Support (Case ID: 102858642503) but wanted to reach out to the community as well. I have seen other posts about this same issue but no real answer on how it was fixed. Has anyone experienced this? Any suggestions appreciated.

Hello, I would really appreciate if someone from Apple could take a look at this, as I believe there may be an issue with my submission or account. I submitted my app for review for the first time over a month ago, and it has been stuck in “Waiting for Review” ever since, with absolutely no updates. This delay is far beyond the typical review timeframes (which are usually just a few days). I have not received any rejection, feedback, or request for additional information. So far, I have already: Resubmitted the build Sent multiple support requests through App Store Connect Requested an expedited review (which was approved) Despite all of this, there has been no progress at all. I have also sent several support messages and emails, but unfortunately I have not received any response so far. It feels like my case is not being reviewed at all, which makes it very difficult to understand what is going wrong. The app is quite standard and does not contain anything that should require extended review. At this point, I am concerned that there might be: An issue with my developer account A submission stuck in the review queue Or some kind of internal flag that I am not aware of Has anyone experienced a similar situation where an app remained in “Waiting for Review” for over a month? And if anyone from Apple is reading this, could you please check if there is any issue with my submission? Any help or guidance would be greatly appreciated. Thank you.