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

I submitted an updated version of my app for review on May 18, 2026, and its status has remained "Waiting for Review" ever since. It has now been more than two weeks without any progress or communication from Apple. To resolve the issue, I have: Submitted multiple support tickets through Apple Developer Support. Received the standard message that I would receive a response within 48 hours. Waited more than 15 days, but have not received any reply to any of my tickets. Attempted to contact Developer Support by phone during U.S. business hours, but after waiting on hold for more than two hours, I was unable to reach anyone. This delay is affecting my ability to release important updates to my users, and I am running out of options. Has anyone experienced a similar situation recently? Is there any other channel or escalation process that I can use to get assistance or have my submission reviewed? Any guidance would be greatly appreciated. Thank you.

It doesn't seem to be able to launch. It says "This version of Xcode is not compatible with this version of macOS." So, does that mean that users who have updated to macOS 27 cannot submit apps to the App Store? Do I have to wait until Xcode 27 starts accepting submissions? Environment: macOS 27.0 / Xcode 26.6 RC

Hi App Review team, I'm posting here as a last resort after7 weeks with no movement and 4 unanswered support requests. I'm about to lose my launch window next week and I need someone at Apple to look at this. The situation: App: BMH Themes — App ID 6763770421 — Bundle ID com.bringmedinahome.bmhthemes Version 1.0 (Build 24): reviewed and APPROVED, currently "Ready for Distribution". In-app purchases: 904 are APPROVED, but 1,134 have been stuck in "Waiting for Review" for 7 weeks. The 1,134 stuck items are the exact same type as the 904 already approved — so this is clearly not a content issue. None of the 1,134 show any rejection or "Developer Action Needed" message. Nothing is pending on my side. I have submitted 4 support requests over the past weeks. None received a substantive response. Why this is urgent: My company is now legally registered, my VAT number is being issued, my business bank account is active, and my full marketing campaign is finalized for a launch next week. I cannot launch with 1,134 of my products frozen — releasing a half-empty catalog would waste the entire launch. These stuck in-app purchases are the ONLY remaining blocker. My request: Could someone please check whether these 1,134 in-app purchases are correctly queued, confirm whether there is an internal processing issue, and escalate to the App Review / in-app purchase team? The app is already approved — only these items are stuck. Thank you very much for any help.

Over the last 24 hours, App Store Connect has been performing very slowly, sometimes showing Bad Gateway and sometimes only loading tab views without any content. I use the word "flakiness" because it's happening intermittently. It took over an hour for Xcode Cloud builds to be triggered yesterday, and during that time it was not possible to start builds manually because the github refs weren't refreshing. Today I was unable to load the Users & Access > Integrations > Webhooks page. Since, I've logged out and back in, and now I cannot load any of my apps even though my development team correctly shows with my account info in the top right. Is anyone else experiencing these symptoms? I see nothing on the System Status page other than an outage with Apple Podcasts Connect.

Hello Apple Support Team, My app's new In-App Purchase appears to be stuck in the review process, and I'd like to check whether there might be an issue with the submission. App Information App Name: Foxify AI - Make Your Own Song Apple ID: 6761515837 Item for Review: New Consumable In-App Purchase Timeline Submitted: July 3, 2026, at 6:28 PM As of today (July 8), the In-App Purchase has remained in "Waiting for Review" for 6 days. Context: We submitted a new app build together with this new In-App Purchase so the Apple Review team could test the updated purchase flow and the new consumable IAP. The app build has already been approved and is currently Pending Developer Release, but the new In-App Purchase is still showing Waiting for Review. Since the IAP has not been approved yet, we are unable to release the new version as planned, and our launch date is approaching. Normally, our In-App Purchases are reviewed within 1–2 days, so this delay seems unusual. Could you please help check whether there is any issue with this submission and, if possible, assist with reviewing it as soon as possible? Any guidance or assistance would be greatly appreciated. Thank you for your support.

Hello, My app Jewel Coloring+ Sort Beads IQ+ (App ID: 6785241915) appears to be stuck in the App Review process, and I would like to check whether there may be an issue with this submission. The current version was originally planned for release on June 30, 2026. However, today is July 7, 2026, and the app is still in "Waiting for Review." Current status: Waiting for Review No messages in Resolution Center No requests for additional information We have also submitted multiple Support inquiries but have not received any response so far. This version is particularly important to our team, as it is tied to a planned release schedule and user acquisition activities that had already been prepared in advance. Given the unusually long delay, we are unsure whether the submission is proceeding normally or if there may be an issue requiring attention. If an Apple staff member could help check the status of this submission, it would be greatly appreciated. Thank you for your time and assistance.

Hello, Our GAKO Business update has been repeatedly delayed in “Waiting for Review,” despite multiple contacts with Apple Developer Support and an approved expedited review request. App: GAKO Business Version: 1.3.1 Current submission date: July 3, 2026 Current status: Waiting for Review Expedited review: Approved This issue has been ongoing across multiple submissions for approximately one month. We have contacted Apple Developer Support several times and followed up repeatedly under the same support case. However, the current submission has still not entered review. The update contains critical production fixes affecting existing App Store users. GAKO Business is used by real businesses to manage appointments, employees, schedules, services, and customer records. The currently published version contains issues affecting essential business workflows, while the corrected version remains unavailable. Apple has confirmed that the application was placed in the expedited review queue. However, it remains in “Waiting for Review.” We are not asking Apple to bypass the App Review Guidelines. We would like Apple to verify whether the submission is affected by an internal routing issue, technical hold, or another submission-level problem. Has anyone experienced the same situation where expedited review was approved, but the application remained in “Waiting for Review”? If Apple staff sees this post, we would greatly appreciate assistance in checking the submission. Thank you.

Does the annually updated requirement that apps uploaded to App Store Connect must be built with the latest SDK (i.e. Xcode version) only apply to the main executable or to embedded binaries (e.g. frameworks) also?

Guideline 1.4.3 rejection for a cigar journal app — multiple apps with identical functionality are live on the App Store Hi all, My first submission (a cigar humidor/tasting journal app) was just rejected under Guideline 1.4.3 (Safety – Physical Harm) for "content or features related to the use of tobacco... products." The rejection states the app's concept is "not appropriate because it is focused on these products or activities." The issue: my app doesn't sell tobacco, doesn't facilitate purchasing it, and doesn't encourage consumption any more than a whiskey-tasting log encourages drinking. It's a personal tracking/journal tool — users log cigars they already own, rate them, track humidor inventory, etc. There is no e-commerce, no social sharing of consumption, no promotional content. There are currently multiple apps live on the App Store with functionally identical (in some cases nearly indistinguishable) feature sets: My Humidor – Cigar Journal — https://apps.apple.com/us/app/my-humidor-cigar-journal/id6639582700 Humidor Journal Pro — https://apps.apple.com/us/app/humidor-journal-pro/id6751737114 Ember: AI Cigar Companion — https://apps.apple.com/us/app/ember-ai-cigar-companion/id6761503587 Whiskey and Cigar Pairing — https://apps.apple.com/us/app/whiskey-and-cigar-pairing/id6762530184 Cigarbase: AI Cigar & Humidor — https://apps.apple.com/us/app/cigarbase-ai-cigar-humidor/id6761301449 Leaf Enthusiasts — https://apps.apple.com/us/app/-/id6757314729 Cigar Journal & Tracker: Puro — https://apps.apple.com/us/app/cigar-journal-tracker-puro/id6760948482 ASHD – Cigar Social — https://apps.apple.com/ca/app/ashd-cigar-social/id6759581213 All of these are humidor/cigar journaling or social apps built around cataloging and tracking tobacco products — the exact category my app was rejected for. Several even use AI companion/recommendation features, which is a superset of what my app does. Full rejection text for reference: Guideline 1.4.3 - Safety - Physical Harm Issue Description: The app includes content or features related to the use of tobacco, nicotine-related, or vaping products, including but not limited to cigarettes, pipes, hookahs, or e-cigarettes. Apps with content or features related to consuming tobacco are considered to encourage the consumption of tobacco. Since these products pose a risk of physical harm to users, it is not appropriate to encourage their use. Next Steps: Your app's current concept is not appropriate because it is focused on these products or activities. It would be appropriate to revise the app or submit a new app that is not focused on these products or activities. My questions for the community: Has anyone successfully appealed a 1.4.3 rejection for a tobacco tracking/journal app (as opposed to a marketplace or vaping-hardware app) by citing comparable live apps? Is there a meaningful distinction reviewers are drawing between "journal/inventory" apps and something else, and if so, what specific wording or framing helped get it approved? Is the right move to reply in App Store Connect citing these examples, or file a separate appeal with the App Review Board? Any input from developers who've navigated this — especially in adjacent categories like whiskey, wine, or other regulated-but-legal-consumable tracking apps — would be hugely appreciated. This is my first submission, so I want to handle the response the right way rather than burning an appeal on the wrong approach. Thanks in advance.

Hi, I'm having a problem because my app stuck in "waiting for review" status since Friday (June 26th). Today is the fifth day we've been waiting for Apple to review the app. We had an app lunch scheduled for today and are stuck with no information. We contacted Apple via the standard contact form and requested expedited app review, but unfortunately, nothing has changed; we haven't received a response to our messages. The app is still "waiting for review." What should I do? Is there another way to contact Apple to expedite the review, or at least get information about the review date? App Name: Genie Vault App ID: 678469924

I want to delete an app from App Store Connect, but I've been unable to do so. App Information: App Name: Need to be removed-MI Apple ID: 6742525904 Current Status: Prepare for Submission I have already followed Apple's official guidelines for removing the app: https://developer.apple.com/help/app-store-connect/create-an-app-record/remove-an-app/ The following operations have been completed: App information has been reset; All in-app purchases have been deleted/cleared; All subscriptions and subscription groups have been deleted/cleared; The app has been removed from all sales regions; App Review Submission has been removed; The submission record in the App Review page now shows as Removed; Logged out and re-logged into App Store Connect; Browser cache and history have been cleared; Attempted to repeat the process using Safari for Mac and different network environments. Currently, when deleting the app, a prompt still appears: “This app is unable to be removed right now. This app cannot be removed. Learn more about removing apps. This app has in-app purchases that are in review. Please try again once these in-app purchases are no longer being reviewed.” The previous error message also included: “Some items related to this app are currently in review. To remove this app, you must first cancel the submission.” However, after removing the App Review Submission, this section has disappeared, and only the prompt related to "in-app purchases that are in review" remains. Currently on the App Store Connect front-end page: The In-App Purchases page is empty; The Subscriptions page contains no subscription items or subscription groups; App Review submission history has been removed; The app is currently in the Prepare for Submission state; No IAPs, subscriptions, or submissions currently under review can be found. Previously, the Subscriptions page displayed a notice: “One or more of the subscriptions listed below requires your attention.” However, the page does not display any subscription items or subscription groups. I'd like to ask if anyone has encountered a similar situation: the front-end page no longer shows any IAP or subscription items, yet when deleting the app, it still prompts that in-app purchases are under review? Is this situation due to residual IAP/Subscription review statuses left behind by Apple's backend, requiring contact with Apple Developer Support for cleanup? Or is there another hidden entry in App Store Connect that can be used to remove these lingering items?

Hi everyone, We're experiencing an unusually long App Review delay for our tvOS application and wanted to check if anyone else is seeing the same behaviour or has any suggestions. App Details Platform: tvOS Xcode Version: 26.4.1 Submission Type: App Update Distribution: App Store Status: In Review Issue We submitted an app update last week, and it remained in the "In Review" state for approximately one week with no updates. Since there was no progress, we rejected that submission, uploaded a new build, and submitted it again. The new build has now also been "In Review" for the last 5 days. Apple has not rejected the app or provided any review notes or requests for additional information. The status simply remains "In Review". What we've tried Submitted an Expedited Review Request. Contacted Apple using the App Review "Contact Us" option. We have not received any response to either request. Since there is no rejection or feedback, we don't have any indication that there is an issue with the app itself. Questions Is anyone else currently experiencing unusually long review times for tvOS apps? Is this likely to be an App Review backlog or a known issue on Apple's side? Has anyone had success getting a response through App Review support or Developer Support in a similar situation? Is there anything else we can do besides waiting? Any insights or recent experiences would be greatly appreciated. Thank you!

Hi all, My first app submission appears to be stalled (16+ days) and I’m completely in the dark as to what is going on. Apple ID: 6776835006 Submission ID: 236039a0-1668-448a-aae6-486d52e6c5b9 Timeline: Ready for Review: Jun 10, 2026 at 3:22 AM Waiting for Review: Jun 10, 2026 at 3:23 AM In Review: Jun 15, 2026 at 5:05 PM Current status: still In Review as of Jun 26, 2026 I have also submitted 2 support cases that are past 48 hour SLA and an expedited review request, but I haven’t received a response yet. Our TestFlight external build has also been stuck in Waiting for Review for 5+ days now. There are no visible unresolved issues, App Review messages, or missing compliance warnings in App Store Connect. Review notes and demo/testing information are provided. Thank you.

Hello Apple Developer Support / Community, Our company's iOS app launch is currently paralyzed due to an automated enrollment block, and we are facing intense customer backlash because our Android version is already live. We urgently need an Apple representative to reset our enrollment status. The Situation: Originally, we started developing our app under a temporary legal entity (Homeflow BV) while our final corporate entity (Luo BV) was being legally formed. We initially opened Case 102912721623 to transfer the account from Homeflow to Luo. However, Developer Support informed us that because Luo is not acquiring Homeflow, a simple transfer isn't permitted. Accepting this, we decided to do it the right way: we abandoned the transfer, unlinked the primary Apple ID (s.aerts@...) from the old Homeflow account, and attempted to enroll Luo BV from scratch as a brand new Apple Developer Program member. The Blocker: When we attempt to enroll the new entity, we are immediately hit with the error: "Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time." It seems our attempt to clean up our accounts and start fresh has triggered an automated security block. We are stuck in a catch-22: we can't transfer the old account, and the system won't let us pay for a new one. Business Impact: • We are a registered energy provider in Belgium • Our Google Play app is live, but our Apple users are entirely blocked from managing their energy contracts. We literally have households where one partner can use the service and the other cannot. • We cannot publish under the old Homeflow entity as it exposes private residential data. Could an Apple representative please clear this security block so we can finalize the enrollment of Luo BV and get our app to our customers? Thank you, Sam Aerts Luo BV

When I was updating the application for release, it was rejected by the Apple 4.3a review team. This update only addressed some crash issues. Our application will only be distributed in specific countries. Our content is protected by copyright and will not appear in other apps; it is unique. id6777977649

App: MahjCheck (Apple ID for app available on request) Subscription Group: MahjCheck Ad-Free (Group ID 22087052) Products: Ad-Free Monthly — com.celebrateeverything.mahjcheck.adfree_monthly (Apple ID 6769124896) Ad-Free Annual — com.celebrateeverything.mahjcheck.adfree_annual (Apple ID 6769126263) Summary of the problem: Both subscriptions were live and fully functional in my approved app version 1.2.1. Customers were able to subscribe successfully. Then, without any changes on my end, both subscriptions reverted to "Missing Metadata" status, and customers can no longer subscribe (the purchase screen spins indefinitely because no offerings can be loaded). I have since completed all metadata: Both individual subscriptions have localizations, pricing, and availability (US and Canada) set I added the subscription group localization that was missing Both products now show "Prepare for Submission" The problem: App Store Connect displays the message "Your first subscription must be submitted with a new app version," but there is NO In-App Purchases & Subscriptions section on my version page to attach them to. I have submitted new app versions (1.2.2 approved, 1.2.3 in progress) and the section never appears, so I have no way to resubmit the subscriptions for review. These subscriptions were already approved and live previously, so they should not be in a "first submission" state. I believe they are stuck in an inconsistent backend state that I cannot resolve from the App Store Connect interface. Request: Please reset or re-approve these two subscription products so they return to "Approved/Active" status, or advise how I can resubmit them given that no In-App Purchases section is available on my version page. Thank you.

Hi has anyone had there app rejected for Guideline 4.3(a) - Design - Spam? my app is a cyber security app which has a VPN and I had this rejection message.. the reasoning was very vague and i am unsure what this means.. I had submitted an appeal and also replied to the reject message but have had no response for over a week. anyone had this and if so, how did you resolve ?

A couple months ago, I got an error when attempting to deploy our app to App Store Connect (see error further below). I used the CLI command xcrun altool --upload-app, and I was trying to upload a new version 1.0.26 build 0, when the previous uploaded version was 1.0.25 build 2 (so the new version is definitely a higher number). I later tried to upload a version 1.0.27 build 1, and that still failed. Note that I have an identical staging app, and I was able to go from 1.0.25 build 2 to 1.0.26 build 0 just fine there. And I have never had issues with version incrementation in the past for either our production or staging app. What could be going wrong here? Here are the error logs: 2026-04-30 23:18:19.430 ERROR: [ContentDelivery.Uploader.6000012404C0] The provided entity includes an attribute with a value that has already been used (-19232) The bundle version must be higher than the previously uploaded version: ‘0’. (ID: 71a9077b-807a-476c-b8a2-04cb8357bc32) NSUnderlyingError : The provided entity includes an attribute with a value that has already been used (-19241) The bundle version must be higher than the previously uploaded version. status : 409 detail : The bundle version must be higher than the previously uploaded version. Failed to upload archive at '[MyApp].ipa'. source : pointer : /data/attributes/cfBundleVersion id : 71a9077b-807a-476c-b8a2-04cb8357bc32 code : ENTITY_ERROR.ATTRIBUTE.INVALID.DUPLICATE title : The provided entity includes an attribute with a value that has already been used meta : previousBundleVersion : 0 previousBundleVersion : 0 iris-code : ENTITY_ERROR.ATTRIBUTE.INVALID.DUPLICATE 2026-04-30 23:18:19.431 ERROR: [altool.6000012404C0] Failed to upload package. 2026-04-30 23:18:19.431 ERROR: [altool.6000012404C0] The provided entity includes an attribute with a value that has already been used (-19232) The bundle version must be higher than the previously uploaded version: ‘0’. (ID: 71a9077b-807a-476c-b8a2-04cb8357bc32) NSUnderlyingError : The provided entity includes an attribute with a value that has already been used (-19241) The bundle version must be higher than the previously uploaded version. status : 409 detail : The bundle version must be higher than the previously uploaded version. source : pointer : /data/attributes/cfBundleVersion id : 71a9077b-807a-476c-b8a2-04cb8357bc32 code : ENTITY_ERROR.ATTRIBUTE.INVALID.DUPLICATE title : The provided entity includes an attribute with a value that has already been used meta : previousBundleVersion : 0 previousBundleVersion : 0 iris-code : ENTITY_ERROR.ATTRIBUTE.INVALID.DUPLICATE

Hello App Review Team, My team's first app submission has been in "Waiting for Review" status for 17 days with no movement, and I would appreciate any visibility you can provide on its current state. Submission details: App name: Motor İzleme Submission ID: fb2151a2-969e-458b-b57b-9fc7a982e168 Submitted: May 20, 2026 at 10:24 PM Version: 1.0 (build 2) Current status: Waiting for Review (17 days) Account type: Organization (first submission under this account) About the app: Motor İzleme is a hardware companion app that communicates with our physical device over Bluetooth Low Energy. Because reviewers cannot physically test the device without the hardware, we have provided the following materials with the submission to support the review: A demonstration video showing the full app-to-hardware interaction (linked in App Review Notes) Detailed App Review Notes explaining the BLE communication flow App screenshots covering all primary screens Clear handling of the no-device state (the app does not crash or hang — it shows appropriate prompts when Bluetooth is off or no device is found) I want to be transparent: I am not requesting expedited review and I understand the team is operating under heavy submission volume in 2026. I am simply asking whether this submission may have been overlooked, or whether there is anything additional I can provide to help the review proceed. This launch is tied to a commitment with our business partner, and the extended delay is beginning to impact business obligations on our end. Any update would be greatly appreciated. Thank you for your time. Best regards, Saadettin Yıldırım

I’ve been using the Age Assurance support page and related Developer News posts as the source of truth for understanding Apple’s expectations around Age Assurance on Apple platforms: https://developer.apple.com/support/age-assurance/ https://developer.apple.com/news/?id=sg176nne Can anyone from Apple clarify whether anything has recently changed with App Review expectations related to Age Assurance? Specifically, are there any new requirements or updated guidance around implementing technologies like DeclaredAgeRange or PermissionKit? I didn’t see any sessions or announcements that indicated these frameworks are now required but with all of the new child safety announcements I thought I'd ask and document for the developer community. I did see the new sample code for implementing Age Assurance and permissions, but nothing suggesting their use is mandatory for App Store approval. https://developer.apple.com/documentation/declaredagerange/implementing-age-assurance-and-permissions Just trying to confirm whether current guidance remains the same, or if App Review expectations are evolving.