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 everyone, My app has been in “Waiting for Review” status since February 4, 2026, and there has been no progress or update since then. Normally, my previous submissions were reviewed within a few days, but this time it has been significantly delayed. There are no messages in the Resolution Center, and I have not received any communication from the App Review team. Has anyone else experienced similar delays recently? Is there anything I can do to follow up or escalate this review? Any guidance would be greatly appreciated. Thank you.

Hi, My app VITTRA has been approved and is live on the App Store. also i have already pushed even another update …However, I submitted two in-app purchases along with the app: 1. VITTRA Pro (Non-Consumable) — Status: “In Review” 2. AI Scan Pack (Consumable) — Status: “Waiting for Review” The app binary was approved and distributed, but the IAPs are still under review. My app’s core functionality depends on these purchases being available to users. A few questions: 1. Is it normal for IAPs to remain in review after the app itself has been approved and distributed? 2. Is there an expected timeline for IAP reviews when submitted alongside a new app? 3. Is there anything I can do to expedite the process, or should I just wait? Any guidance would be appreciated. Its a real frustrating situation and there is not a single response from the support. Thanks!

Dear Apple Review Team, I am writing to urgently follow up regarding our pending account termination and appeal, as we have not received any response despite multiple attempts to contact your team. For reference, our timeline is as follows: January 31, 2026: Received Pending Termination Notice January 31, 2026: Submitted appeal and corrective update February 7, 2026: Responded to DPLA compliance notice February 12, 2026: Submitted follow-up via Review Board February 23, 2026: Submitted additional summary follow-up via Review Board and Contact Us February 23, 2026: Contacted Apple Support by phone for status inquiry We have fully addressed all identified compliance issues and submitted all requested verification documentation, including government-issued identification, proof of address, and relevant licensing documentation. As of today, our corrective update remains marked as “In Review,” and we have not received any acknowledgment or update from your team. With the February 28 deadline imminent, the lack of communication is extremely concerning. We respectfully request: Confirmation that our appeal and corrective submission are actively under review Clarification on whether any additional information is required from us An estimated timeframe for a decision We are fully committed to complying with Apple’s policies and guidelines and have made every effort to respond promptly and thoroughly. We would greatly appreciate your urgent attention to this matter. Thank you for your time and assistance. We look forward to your prompt response. Sincerely, Tien Nguyen

I just had an app approved and pending developer release. As part of my release checks, I always download the app using a promo code (even for free apps). This time, on both iOS and macOS, redeeming a promo code for the respective builds gives this error: Unable to Redeem. This content is incompatible with the current software on this device. Update your device to the latest software version and try again. The app targets iOS 26.0 and macOS 26.0, and my devices are on the latest releases. Has anything changed with promo code redemption for approved apps? I typically use promo codes for updates, but have not released a new app in a while.

Hi everyone, I am trying to submit the first version of my app with auto-renewable subscriptions, but I am stuck in a loop. Both of my subscriptions (Yearly and Monthly) are stuck with the status "Developer Action Needed". Because of this status, they do not appear in the list of available In-App Purchases when I try to attach them to my app binary on the App Store Connect submission page. Here is what I have already done/checked: All metadata is filled out (Display Name, Description, Pricing). Review Information is complete (Screenshot and Review Notes are provided). My "Paid Applications" agreement in the Agreements, Tax, and Banking section is Active. I contacted Apple Developer Support by phone, but they were unable to resolve the issue and suggested I post here for help. Has anyone experienced this "limbo" before? How can I trigger the status to change to "Ready to Submit" so I can finally attach them to my build and send the app for review? (I have attached screenshots of my App Store Connect dashboard showing the issue). Thanks in advance for any help!

I'm experiencing a contradictory validation issue with DeviceActivityReportExtension that creates an impossible situation: The Problem: Without NSExtensionPrincipalClass in Info.plist → App Store Connect rejects upload with: "Missing Info.plist values. No values for NSExtensionMainStoryboard or NSExtensionPrincipalClass found" With NSExtensionPrincipalClass → Local install fails with: "defines either an NSExtensionMainStoryboard or NSExtensionPrincipalClass key, which is not allowed for the extension point com.apple.deviceactivityui.report-extension" Setup: Extension point: com.apple.deviceactivityui.report-extension Using SwiftUI with @main attribute and DeviceActivityReportExtension protocol Xcode 16.2, iOS 17.6 deployment target Code structure: @main struct SpoolReport: DeviceActivityReportExtension { var body: some DeviceActivityReportScene { // Report scenes here } } The extension builds and runs perfectly without NSExtensionPrincipalClass, but cannot be uploaded to App Store Connect. Adding the key allows upload but breaks local installation. Is this a known issue? Is there a workaround or correct Info.plist configuration for DeviceActivityReportExtension? Thank you!

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

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

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

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

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

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

I am aware of the following in the App Review Guidelines; 3.1.1 If you want to unlock features or functionality within your app, (by way of example: subscriptions, in-game currencies, game levels, access to premium content, or unlocking a full version), you must use in-app purchase. Apps may not use their own mechanisms to unlock content or functionality, such as license keys, augmented reality markers, QR codes, cryptocurrencies and cryptocurrency wallets, etc. The app itself operates normally, but imposes limits after a limited time of use. Purchasing the full version removes these limits. This is a one-time IAP, not a subscription. My app is aimed at professionals within the entertainment industry, and will only ever be used within a theatre or other similar venue. I do not intend to provide any other paid route to the full version than via the App Store. However, what I would like to do is provide free use at certain events and to students in their educational venues (e.g. college theatres etc)- is it acceptable to use an external mechanism (e.g. a server based API) to temporarily remove the limitations whilst in that venue? Or, likewise, provide an extension to the free trial period for specific uses. Note this is not a purchase, as there is no payment. Therefore there is no revenue outside of the App Store (which surely is the point of the mandate to use IAP for this purpose) Also, it's not fully 'unlocking' the app (the user doesn't get the full version, they just aren't bound by the trial limit timer when within that venue or for a limited time) I'm aware that another route would be to put a different version of the app in the store that requires a username and password for use (for example) and then provide those credentials to log in - as there's lots of apps that follow that model, but it seems clunky to require the user to download a different app.

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

Hi everyone, I’m opening a new thread because I previously posted about this issue and received a reply from App Review saying it was being investigated, but unfortunately I have not received any follow-up and still see no progress in App Store Connect. At the moment, all 3 of my apps are still stuck in “Waiting for Review” with no visible update: App ID 6759178103 — Waiting for Review since Feb 14, 2026 App ID 6758885884 — Waiting for Review since Feb 8, 2026 App ID 6758135741 — Waiting for Review since Feb 6, 2026 I do not see any warnings, Resolution Center messages, or visible account issues. Agreements/Tax/Banking are active, and the builds were uploaded successfully. Could someone please help check whether there might be a hidden blocker on my account or these submissions, or confirm if this is currently only a review queue delay? If needed, I can provide additional details immediately (bundle IDs, app category, sign-in requirements, encryption/export compliance, etc.). If anyone else is currently experiencing the same delay, please feel free to share your status here as well (date submitted / current status), so we can understand whether this is a broader review queue issue. Thank you in advance for your help.

Dear Apple Review Team, I am writing to request a status update regarding our pending account termination and the appeal currently under review. For reference, please see the timeline below: January 31, 2026: Received Pending Termination Notice January 31, 2026: Submitted appeal and corrective update February 7, 2026: Responded to DPLA compliance notice February 12, 2026: Submitted follow-up via Review Board February 23, 2026: Submitted additional summary follow-up via Review Board and Contact Us In addition to addressing all identified compliance issues, we have submitted all requested verification documentation, including personal identification documents (government-issued ID), proof of address and relevant licensing documentation. At this time, our corrective update remains marked as “In Review,” and we have not yet received further feedback. With the February 28 deadline approaching, we are concerned about the current status of our appeal. We have carefully addressed all identified issues and are fully committed to maintaining compliance with Apple’s policies and guidelines. We respectfully request confirmation that our appeal and corrective submission are actively under review, and we would greatly appreciate any available update regarding next steps. Thank you for your time and consideration. We look forward to your response. Sincerely, Tien Nguyen

A short overview on how ASO tools calculate keyword difficulty differently and why no platform can claim an official score. The real evaluation lies in comparing competitive apps, understanding relevance, and reviewing metadata quality for each keyword.

With agentic coding and AI rapidly improving at solving development problems, I’m starting to question what the next three to five years will look like for iOS developers and whether manual coding will gradually disappear. I’ve been building iOS apps full time since 2013 and while I appreciate AI for speeding up workflows like unit testing, I worry that over reliance could weaken our core skills, reduce our understanding of evolving APIs, and ultimately impact our long term value and demand in the industry, does anyone else feel the same?

We recently changed the development team for our app and are getting ready for the first update since the change. We store a small amount of data in an sqlite database. From what I understand that data should be retained for users when updating the app version since the Bundle ID has remained the same. When I update the app from the currently released App Store build, which was from the old development team, to the latest build in TestFlight the data is not being retained. Is there something else that needs to be done to retain the data? Is it possible that the data is only being lost when updating from TestFlight but will be retained when updating the app from the App Store?

Hello everyone, I am hoping someone here can share some advice or has experienced a similar situation. I am an individual developer and two of my apps have been stuck in 'Waiting for Review' status for over 10 to 12 days now. Prior to this, the review process was moving normally and I was receiving feedback from Apple on both apps. Then suddenly everything stopped and both apps have been sitting in the queue with no movement and no communication from the review team. To make things worse, I am also unable to delete these apps or make any changes because their In-App Purchases are simultaneously under review, which is locking me out of managing my own apps entirely. I already created a support case specifically for App Review (Case ID: 20000111755276) over a week ago, but unfortunately I have not heard back anything from Apple at all — no acknowledgment, no update, nothing. I am based in Pakistan and the phone callback option is not available for my region, so email and this forum are essentially my only options to get any help. Has anyone else experienced such a long delay recently? Is there anything else I can do to get this moving or at least get a response from the review team? Any advice or shared experience would be greatly appreciated. Thank you.