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'd like to use Xcode 27 Beta, for its Coding Intelligence features, on existing iOS 17 thru 26 production code. As long as I don't allow iOS 27 as a target, will I be able to use Xcode 26 to submit the Xcode 27 project files now to the App Store for distribution? I can imagine situations where Xcode 27 makes use of a new backward-compatible API feature that Xcode 26 balks at. Perhaps I'll have to watch out for that, unless there's a way to tell Xcode 27 to avoid it automatically?

I am looking for guidance from Apple or developers who have encountered a similar issue. My app is already live on the App Store. I have two auto renewable subscriptions: • PDR Fuel Pro 6 Months • PDR Fuel Pro Annual The subscriptions have been submitted for review multiple times and have been rejected repeatedly. The rejection appears under the subscription localization, but no meaningful explanation is provided. Current status: • Subscription metadata is completed. • Display names and descriptions are present. • App Store agreements, tax, and banking are active. • RevenueCat configuration is functioning. • The app build is already live. • Subscription purchase flow is implemented and accessible from the app. The issue is that App Review continues rejecting the subscription localizations without providing a clear rejection reason or guideline reference. Questions: Has anyone encountered repeated subscription localization rejections without explanation? Is there a known issue where subscriptions become stuck after a build is withdrawn or replaced? Is there a way to determine the exact rejection reason when App Store Connect does not display one? Should this be escalated through Developer Support instead of App Review? Any guidance would be appreciated.

Is anyone else experiencing unusually long App Review times? My app has been in review for about a month now with no progress. After waiting for so long, I cancelled and resubmitted it twice, hoping it might help, but the situation remains exactly the same. I've also contacted App Review and submitted a request for an update, but I haven't received any response yet. At this point, I'm wondering if anyone else has gone through something similar recently. How long did it take to get resolved, and is there anything else I can do besides continuing to wait?

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

I have my first app on the App Store and I’m unsure whether I’m seeing a normal App Store indexing delay or a storefront issue. The macOS version of my app is searchable and can be found normally in the Mac App Store. The iPhone/iPad version was approved, the direct App Store URL works, the app page shows a price, and the app can be reached from my website. However, neither the app name nor the developer name can be found through App Store search on iPhone or iPad. In addition, App Store Connect currently does not allow me to edit screenshots or other metadata, and the Mac storefront appears to be displaying incorrect screenshots. Is there a recommended Apple support path for App Store search indexing and storefront metadata issues, or does this indicate a known App Store Connect problem?

Hi Apple Team, We're looking for guidance from developers who have successfully resolved a rejection under App Review Guideline 3.2.1(viii). Our app is mPokket: Instant Loan App, a consumer lending application that has been live on Google Play for nearly 10 years. The app is published by Maybright Ventures Private Limited, which owns and operates the mPokket lending business and brand. While consumers know the service as "mPokket," the legal entity behind the business and the developer account is Maybright Ventures Private Limited. Our iOS app has now been rejected twice with the following message: "The app provides loan services but the domains listed on the app's Product Pages are not clearly under your control or ownership." Apple also mentions that the Product Page domains and the email domains of the Apple Accounts associated with the developer account should clearly identify the company providing the loan services. Has anyone faced a similar situation where: The consumer brand name is different from the parent/legal entity name? The developer account is under the parent company while the app is marketed under a consumer brand? App Review requested additional clarification regarding ownership of the lending business and website domains? If so, what documentation or changes helped obtain approval? Did you need to: Change the Account Holder/Admin Apple IDs to use the parent company's domain? Add additional ownership documentation? Provide a corporate structure explanation or trademark/brand ownership details? Any guidance or experience would be greatly appreciated. Thank you.

Hello, I'm hoping someone from the App Review team can look into this situation, which has specific context that I believe makes it worth a careful look. Thank you in advance for your time. I'm hoping someone from the App Review team can look into this situation, which I believe has specific context that makes it worth a careful look. My app YADA: You've Already Met (App ID: 6759586097) has been in "Waiting for Review" since Wednesday May 6 at 7:44 PM ET - now over 96 hours. I have an open support case (20000112508151) filed Friday with no response yet. I'm not writing simply to flag the wait - I want to explain why this submission deserves a thoughtful second look on the merits. When YADA was submitted for TestFlight beta review, it was flagged under Guideline 4.3(b) for the same reason as the App Store rejection. I appealed, explained the differentiating mechanic, and an Apple reviewer evaluated the argument and approved the app for external testing. That approval is on record. I'm asking for consistency with that prior decision. YADA's core mechanic is genuinely unlike any dating app currently on the App Store. A user privately adds someone they already know to a list. That person receives no information about who added them. A match is only revealed when both people have independently and privately added each other. If the feeling isn't mutual, nothing is ever disclosed. There is no browsing of strangers, no algorithmic recommendations, no swiping, and no rejection possible because neither party knows they've been added until both have added each other simultaneously. Critically, YADA does not ask users to declare their gender or sexual preferences - because the mechanic doesn't require it. This makes YADA the only interest-discovery platform on the App Store that works entirely without those declarations, which creates a uniquely safe experience for LGBTQ+ users and young people who are not ready to publicly disclose their orientation. No equivalent experience exists on the App Store. The App Store rejection also included 5.1.1 and 2.1 issues, both of which I fully resolved - redesigning the contacts permission flow with a proper in-app explanation screen and directly answering Apple's question about data handling - with a new build submitted alongside my Resolution Center reply. I'm not asking for special treatment. I'm asking for the opportunity to have the full argument evaluated by a reviewer with the time to consider it, consistent with how the TestFlight review was handled. Support case: 20000112508151. App ID: 6759586097. Submission ID: abdf8b5b-5ea0-46a4-8a0b-fb58320fa701. Thank You

Hello everyone, I submitted the first update for my app on April 14. On April 18, I canceled that submission and immediately resubmitted it the same day, as many people suggested that resubmitting might help speed up the review process. Today is June 4, and after 47 days, the update is still stuck in “Waiting for Review.” I’ve seen that many other developers are experiencing the same issue, but 47 days is a very long time for me, and I have no idea how much longer I should expect to wait. I hope we can all find a solution to this situation soon. Any advice, insights, or shared experiences would be greatly appreciated. Thank you all.

Hello App Review Team, Our app submission has been stuck in the “Waiting for Review” status for an extended period, and we would like to kindly ask whether there is any issue or additional action required from our side. We have already uploaded the latest build and verified the In-App Purchase configuration in App Store Connect. Since the status has not changed, we wanted to check if the submission queue is functioning normally or if there is anything preventing the review from starting. We would appreciate any clarification or guidance you can provide. Submission ID: 85a6b879-5218-4f2c-b444-de09d148268e Apple ID: 6766198981 Best regards, Mert Akgün

Hello, I’m posting again because our previous forum post received the following Apple Staff reply: “Thank you for your post. We're investigating and will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us.” However, the issue has not been resolved yet. We have not received any separate contact in App Store Connect, the Resolution Center, or email. We currently have two active apps in the same developer account that are stuck in Waiting for Review. Because multiple apps in the same account are affected at the same time, this seems like it may be an account-level App Review queue or routing issue rather than an individual app binary issue. For one of the affected apps: App ID: 6760743106 Review submission ID: 6950ecff-f833-404d-b04b-ac34ec552b85 Submitted: June 1, 2026 Review submission state: WAITING_FOR_REVIEW Review submission item state: READY_FOR_REVIEW App Store version state: WAITING_FOR_REVIEW Build processing state: VALID Build audience type: APP_STORE_ELIGIBLE Build expired: false TestFlight installation works normally, and there is no Resolution Center message. We are also unable to submit an expedited review request because the expedited review form itself fails. After selecting the correct app and platform, the form sends a POST request and receives HTTP 200 OK, but the response page displays: “Sorry, we didn’t receive your request. An error has occurred and your submission wasn’t completed. Please go back and try again. If you continue to have issues, contact us.” The POST payload includes the correct app ID and platform: expedite_app_id_req: 6760743106 expedite_app_platform: ios Could Apple Staff please check whether our developer account or these submissions are affected by an internal App Review queue/routing issue? We are currently blocked because the review has not started for multiple apps, we have not received any follow-up contact, and the expedited review request form cannot be submitted.

Hello Apple Staff, Thank you for your previous reply. After my initial post, I understood that my app would enter the review process shortly. However, another three days have passed, and the status of my app remains “Waiting for Review.” I am becoming increasingly concerned about whether my app has successfully entered the review queue. Prior to this, I have already tried the following support channels without success: Contacting Apple support by phone Reaching out via email Requesting an expedited review Posting on developer forums I fully understand that app review times may vary, and I truly respect the work of the App Review team. However, this situation is becoming more serious for us. This submission is critical for our users, and the ongoing delay is having a significant impact on our operations and business. App Details: App ID: 6764726742 Submit time: 2026-06-01 Submission ID: 187011d0-1390-4abe-9252-f13410307c31 Current Status: Waiting for Review I would greatly appreciate it if Apple could kindly verify the following: Whether the current submission is properly queued for App Review Whether there is any internal processing or queuing issue preventing the review from starting Whether any action is required from my side that is not visible in App Store Connect If possible, could an Apple staff member please escalate this case to the App Review team, or at least confirm that the submission is correctly queued? I would be extremely grateful for any help or clarification. We feel stuck because we have tried every available support channel, yet the app remains in “Waiting for Review” with no progress. Thank you very much for your time and support. Best regards, Leon

Hello, I’m posting again because our previous forum post received the following Apple Staff reply: “Thank you for your post. We're investigating and will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us.” However, the issue has not been resolved yet. We have not received any separate contact in App Store Connect, the Resolution Center, or email. We currently have two active apps in the same developer account that are stuck in Waiting for Review. Because multiple apps in the same account are affected at the same time, this seems like it may be an account-level App Review queue or routing issue rather than an individual app binary issue. For one of the affected apps: App ID: 6760743106 Review submission ID: 6950ecff-f833-404d-b04b-ac34ec552b85 Submitted: June 1, 2026 Review submission state: WAITING_FOR_REVIEW Review submission item state: READY_FOR_REVIEW App Store version state: WAITING_FOR_REVIEW Build processing state: VALID Build audience type: APP_STORE_ELIGIBLE Build expired: false TestFlight installation works normally, and there is no Resolution Center message. We are also unable to submit an expedited review request because the expedited review form itself fails. After selecting the correct app and platform, the form sends a POST request and receives HTTP 200 OK, but the response page displays: “Sorry, we didn’t receive your request. An error has occurred and your submission wasn’t completed. Please go back and try again. If you continue to have issues, contact us.” The POST payload includes the correct app ID and platform: expedite_app_id_req: 6760743106 expedite_app_platform: ios Could Apple Staff please check whether our developer account or these submissions are affected by an internal App Review queue/routing issue? We are currently blocked because the review has not started for multiple apps, we have not received any follow-up contact, and the expedited review request form cannot be submitted.

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 would like to explain the current situation regarding our subscriptions and ask a few clarification questions to ensure that our implementation fully complies with App Store requirements. Current Status We have successfully configured our subscriptions in App Store Connect. All subscription products currently appear as “Waiting for Review.” Paid Apps Agreement has been accepted and is active. Banking and tax information are completed and active. RevenueCat integration is working correctly. In TestFlight, the app is now able to: Fetch products successfully Display localized Turkish pricing Open the native Apple purchase sheet Start sandbox purchase flow successfully We can now see Apple’s native TestFlight subscription purchase popup with the correct products and prices, which indicates that StoreKit communication is functioning correctly. However, we are still confused about the review/submission relationship between: The app version submission The first subscription review Existing “Waiting for Review” subscription states Questions Since the subscriptions already show “Waiting for Review,” does this mean they are correctly attached to the currently reviewed app version? Or do we still need to create an entirely new app version submission and manually re-add all subscriptions from the “In-App Purchases and Subscriptions” section before review can continue? The subscriptions are already accessible in TestFlight sandbox purchase flow. Does this confirm that our StoreKit configuration is now technically valid for review? If there is still a configuration issue on our side, could you please clarify exactly which step is missing: attaching subscriptions to a specific binary, submitting the first subscription with a new app version, or another App Store Connect configuration requirement? Our goal is to fully comply with App Store policies and avoid submitting another incorrect review build.

Hello, I'm hoping someone from App Review can help look into two submissions that have been stuck in "Waiting for Review" far beyond the normal window. Both are from the same (recently created) developer account, and both have been waiting for weeks without moving to "In Review". App 1 — EyeRest App ID: 6762698407 Submission ID: 9a1e697d-df86-4ba4-b8e9-977ceb290638 Version: 1.0.0 (build 11), iOS Submitted: 2026-05-07 — over 30 days in "Waiting for Review" App 2 — breathcare App ID: 6767147235 Submission ID: 8fedc120-b43b-48c5-8d73-c39157c75286 Version: 1.0.0 (build 6), iOS Submitted: 2026-05-19 — over 18 days in "Waiting for Review" What I have already checked / tried: Agreements, Tax, and Banking are all active (Paid + Free Applications agreements active, tax forms and banking complete). Resolution Center shows no messages from App Review for either app — I have not been asked for anything. No alerts/banners on the account or app pages. Both apps are already live on Google Play, so the builds are functional. I would prefer NOT to withdraw and resubmit, since that would send them to the back of the queue and likely won't address whatever is holding them. Could someone please check why these two submissions are not progressing? Thank you.

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.

hello app review: My app was submitted for review at 11:07 PM on June 1st, and as of now, on the afternoon of June 4th, it has not yet entered the review process. Please urge the review team to proceed with the review as soon as possible. If there are any areas that need to be rectified, we will immediately make the necessary changes. Thank you

App Store Connect displays the In-App Purchases and Subscriptions section on your app's version page when your app has an In-App Purchase or subscription with a Ready to Submit status. To locate the In-App Purchases and Subscriptions section: In Apps, select the app you want to view. In the sidebar, select the app version. On the version page, scroll down to the In-App Purchases and Subscriptions section. For more information, see Submit an In-App Purchase.

Hi Apple Developer community and Apple Review team, I'm hoping to get assistance with a persistent 4.3(a) rejection for our app ByGate (net.bygate.vpn). Submission ID: c8278a90-8e90-45b2-9256-d2e6b34e9518 Latest review date: May 19, 2026 Our situation: ByGate is not a generic VPN tool. It is a dedicated client application for ByGate's proprietary server infrastructure. The app works exclusively with ByGate servers - users cannot enter custom addresses, import third-party configurations, or connect to any other provider. It is functionally similar to a banking app or a streaming app: it only connects to one specific service. We have been operating ByGate as a cross-platform service: Android app live on Google Play Windows desktop app distributed via our website macOS desktop app distributed via our website Active paying subscriber base across all platforms Our existing users regularly contact our support team asking when the iOS version will be available. They are already using our servers and subscriptions on other devices and want the same experience on iPhone. Why we believe the rejection doesn't apply: Apple's own guidelines (4.8) recognize "apps that are a client for a specific third-party service" as a distinct, legitimate category. ByGate fits this exactly - the same way Netflix, Spotify, or any banking app is a dedicated client for one specific service. The concern about "similar binary" is understandable - like many VPN apps, we use an open-source networking library. But using a shared networking library (like WireGuard, OpenVPN, or in our case libbox) does not make an app conceptually identical to others, just as using SQLite doesn't make a database-backed app a duplicate of every other such app. Unique features of ByGate not found in other apps on the App Store: Split tunneling mode specifically pre-configured for Russian-language internet services Anonymous account creation (no email or phone number required) Freemium model with 100 MB free tier, no registration required Access exclusively to ByGate's own server nodes in Europe and USA Our 24/7 support on Russian-language We have responded to every rejection with detailed explanations, but receive only the standard templated response. We are genuinely committed to compliance and would welcome direct guidance on what specifically needs to change, or a review call with the App Review team. Thank you for your time.

Hello everyone, I would like to ask whether other developers are currently experiencing unusually long App Review delays for new apps. Here is the timeline for my app (Apple ID: 6759361892): Build 1 — Feb 19, 2026: Initial build submitted Feb 21, 2026: Rejected because ads were not working properly Build 2 — Feb 23, 2026: Updated build submitted Build 3 — Feb 26, 2026: Another updated build submitted Mar 11–18, 2026: Status remained “Waiting for Review” and never entered the “In Review” stage Mar 18, 2026: Submission cancelled and resubmitted Current status: Still “Waiting for Review” During this period, I have already tried several ways to resolve the issue: Contacted Apple Developer Support multiple times Submitted an expedited review request Sent several follow-up emails regarding the delay Contacted Apple Support and asked them to leave messages for the App Review team Each time, I was told that the situation would be checked or that the review would “begin shortly.” I have now received that same response multiple times, including after my expedited review request was accepted, but there has still been no visible progress or transition into active review. While browsing the Developer Forums, I also noticed that several recent posts seem to describe similar situations, especially involving new app submissions remaining stuck in “Waiting for Review.” So I would like to ask: Are other developers currently experiencing similar delays? Has anyone recently seen their app finally move from “Waiting for Review” to “In Review” after a very long delay? Could this possibly be related to a broader App Review queue slowdown? I’m mainly trying to understand whether this is an isolated issue or something other developers are also currently facing. Any recent experiences or information would be greatly appreciated. Thank you.