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

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.

Hello, Our game is scheduled for official release tomorrow, Wednesday, August 5, and we would like to request an expedited review. This build was first submitted on July 23 and has been in the review process for about two weeks; our latest submission is currently in "Waiting for Review" status. All marketing and promotional campaigns have already been rolled out based on the August 5 launch date. This date is especially important because the new theatrical film of the original animation 'Catch! Teenieping' premieres on the same day, and the game is planned to launch alongside the film. The previous film drew over 1 million moviegoers, becoming the first Korean animation to do so in 12 years. Many children and family fans have long been looking forward to this day. This is the first official match-3 puzzle game based on the Teenieping IP, and we have put great care into making it a game families can enjoy together. After launch, we are fully committed to operating the game responsibly in compliance with the App Store guidelines. We apologize for the urgent request and would sincerely appreciate it if the review could be completed in time. App Name: Teeniping Magic Match App Apple ID: 6786589102 App Bundle ID: com.plaium.tmm

Hello everyone, I’m wondering if other developers are currently seeing unusually long “Waiting for Review” times. I currently have multiple apps waiting for review. Some have been in the queue for more than a week, while others have now been waiting for over two weeks without ever moving to “In Review.” This is unusual compared to my previous submissions, which normally entered review much sooner. There are no messages in the Resolution Center, no guideline issues, and nothing indicating that any action is required on my side. Has anyone experienced the same thing recently? Are review queues currently slower than usual? Have your apps eventually moved to “In Review” after waiting this long? Is there anything else worth checking besides Agreements, Tax & Banking, and App Store Connect metadata? I’m not trying to complain—I’m simply trying to understand whether this is affecting other developers as well or if it’s something specific to my account. Thanks in advance for sharing your experience.

Title: iOS update stuck in Waiting for Review for 7 days (Apple ID 6784986397) Hello App Review Team, Our iOS update has been in Waiting for Review for seven days with no movement. App: LiveLens Apple ID: 6784986397 Platform: iOS Version: 1.2.5 (build 23) Submitted: 28 July 2026 Submission ID: 250f2676-169c-435e-989e-81321b22849b Status: Waiting for Review, unchanged since submission What we have already verified on our side: No Developer Action Needed items No unaccepted agreements, and banking and tax information are complete No unresolved metadata flags and no messages in the Resolution Center Demo credentials for the reviewer are provided in App Review Information and are current We have not withdrawn the submission and have not requested an expedited review. The Android release of the same version has been live since 28 July, so our iOS users are still on the previous version and are not receiving the fixes in this build. Could someone please check whether this submission is stuck in the queue, or let us know if anything is required from our side? Thank you.

Hello, My app submission has been stuck in "Waiting for Review" since Sunday, July 26, 2026 (over 100 hours) and has not moved to "In Review". There are no messages in the App Store Connect Resolution Center or requests for additional info. Here are the details of the submission: App Name: Lab Escape: Zombie Survival Apple ID: 6782424764 Platform: iOS Version: 1.0 (Build 1.0.0 (11)) Date Submitted: Sunday, Jul 26, 2026 at 10:05 AM Submission ID: 6b869be6-aa51-45d0-9b80-ffba4dd5ae8c Current Status: Waiting for Review This is the initial release of the app. All agreements, tax, and banking details are active, and metadata, export compliance, and age ratings are complete. Could someone please check if the submission is proceeding normally or if any action is required on my side? Thank you in advance!

Hello, My iOS app, Chef Library, version 1.2.0, has remained in “Waiting for Review” for several days. App Store Connect shows no unresolved issues, missing information, or messages from App Review. I contacted Apple Developer Support on July 28 and followed up again on July 30. Both messages appear under support case 20000121706395, but I have not received a response and the review has not started. The submission details are: App: Chef Library Platform: iOS Version: 1.2.0 Current status: Waiting for Review Support case: 20000121706395 Could an Apple representative please check whether this submission is progressing normally or whether it has become stuck in the review queue? If anything is required from me, I am ready to provide it immediately. Thank you, Bart

Hello everyone, I’m writing this post in the hope of hearing from other developers who may have experienced a similar situation, and to better understand whether this level of action without transparency is common. Our company, VISION VENTURES TEKNOLOJİ TASARIM VE PAZARLAMA A.Ş., is the developer of Watchlabb, an app that has been available on the App Store for approximately six months. Watchlabb is not an online watch retailer. We do not own watches, buy watches, or sell watches. Our platform simply connects independent buyers and sellers of authentic watches, allowing them to publish listings, create auctions, and communicate directly with each other. From the very beginning, our goal has been to build one of Turkey’s safest marketplaces for authentic watches. To achieve this, we have invested significant effort into protecting users by: Reviewing listings before publication. Rejecting counterfeit and replica watches. Verifying user identities. Moderating marketplace activity. Building a transparent and trustworthy environment for collectors and buyers. In other words, our platform exists to prevent fraud, not enable it. Despite this, Apple terminated our entire corporate Developer Program membership under Section 3.2(f) of the Apple Developer Program License Agreement. The notice states that Apple has “documented indications of fraudulent conduct associated with your account.” However, it does not explain: What specific conduct allegedly violated the agreement. Which feature, transaction, listing, or activity is involved. Whether the concern relates to a specific user. What evidence led Apple to this conclusion. Before the termination: We never received a warning. We were never informed that our account was under investigation. We were never asked to provide additional information. We were never given an opportunity to explain or correct anything. Even more confusing, our latest app update was approved through App Review just three days before our developer account was terminated. This decision affects much more than our company. We currently have approximately: 2,800 registered users, hundreds of active listings, ongoing auctions, professional stores operating on our platform. Many businesses rely on our application to reach customers, and many users depend on it to buy and sell authentic watches safely. As a registered company, we have contractual obligations, commercial partnerships, and responsibilities toward both our sellers and our users. Having our entire developer account terminated without knowing what specific conduct Apple believes occurred has placed both our business and our community in an extremely difficult position. We fully support Apple’s efforts to protect users and maintain the integrity of the App Store. Those are values we share. What we struggle to understand is how such a severe action can be taken without identifying the specific facts behind the allegation or giving a company the opportunity to respond before permanently terminating its developer account. Has anyone else experienced a similar situation? Were you able to obtain more detailed information from Apple or successfully resolve the issue? Any advice or shared experience would be greatly appreciated. Thank you.

App update stuck in “Waiting for Review” after replacing an approved build (possible queue issue?) Hello, I would like to know whether other developers are experiencing a similar issue with App Review this weeks. App: Spherag IOT Platform: iOS Current build: 1.2.34 (234) Status: Waiting for Review Timeline Friday, July 24: build 1.2.30 was reviewed and approved successfully. We decided not to release that approved build. Monday, July 27: we removed it from release and submitted 1.2.31 (231). Build 1.2.31 remained in Waiting for Review for about 3 days and never moved to In Review. We then submitted 1.2.34 (234), Today, August 04: after waiting several days with no progress, we removed the submission and re-submitted the same build, 1.2.34 (234), which is currently still in Waiting for Review. I have already opened two Developer Support cases regarding this issue, but I have not yet received a resolution. What concerns me most is that, after submitting build 1.2.34, the version history in App Store Connect appears inconsistent and previous entries are displayed as 1.2.34 (234). This makes me wonder whether there could be a display issue or a problem with the review queue state. All Agreements, Tax and Banking information are active, and all required metadata, privacy details, export compliance and age rating information are complete. This delay is becoming difficult to manage operationally: one release is already blocked, a second release is now waiting, and a third release will likely be ready before the current submission is reviewed. Has anyone experienced a new submission remaining in “Waiting for Review” for several days after withdrawing a previously approved build and submitting a newer build? If so, did it eventually move to review automatically, or was any action from Apple required? Thank you.

Xcode 26.6 It's showing crashes from the App Store Analytics. But no crash logs from Xcode Organizer. I have tried to sign out and log in to Xcode again. I also changed the folder /Library/Developer/Xcode/Products and View > Reload the Organizer. Nothing helps. It's still empty for all versions.

Hello, We are reaching out because I haven't received any response from App Review for about 220hours, The date We had planned to make my proposal has already passed. App: Apple ID 6782845619, version 1.2 Submission ID: 2722eda8-9429-44d2-9971-092f4ed28ffb Rejection: Guideline 4.3(a) — Design (Spam) I have already taken the corrective steps suggested in the rejection message (I withdrew the duplicate prototype app from review and removed it from all 175 storefronts, so there is no overlap anymore), and I replied to App Review in App Store Connect with this information. However, it has now been about 220 hours with no reply. I understand the review team is very busy, and I truly appreciate their time. I'm not trying to dispute the review process itself — I would simply be grateful if someone could check whether my reply has been received and is being looked at, or advise me on the best way to get a status update. Thank you very much for your help.

Hello App Review Team, I'm reaching out because our submission has been stuck in "Waiting for Review" for over 90 hours with no visible movement, and this is time-sensitive on our side. App Name: Mibanco Platform: iOS Version: 4.3.0 (Build 10000528) Submission ID: 32cbac81-e5f8-43d4-b09f-363d33aba256 Apple ID: [add your numeric Apple ID here] Timeline: Jul 30, 2026, 12:33 PM: In preparation for submission Jul 30, 2026, 12:39 PM: Submitted / Waiting for Review Aug 3, 2026 (today): Still "Waiting for Review" — no rejection, no messages, and no information requests in the Resolution Center Context: this version slot was previously used for a build tied to a certificate-related change. We had to developer-reject that earlier build, which is why the version number jumped from 4.2.x straight to 4.3.0 rather than a normal increment. What we've already tried: Contacted Apple through the general Contact Us form with our Apple ID and submission ID — no response so far. Submitting an Expedited App Review request through the official form alongside this post. Why this is urgent: This release needs to go live before a scheduled backend certificate rotation on our side. Once that rotation completes, the app versions currently live on the App Store will stop being able to authenticate with our backend — so every day this stays in review increases the number of users who will lose access. We understand App Review is handling a high volume of submissions right now and we're not trying to jump the line — we just want to confirm this hasn't fallen into a technical gap, since there's been zero communication in either direction. Any update, or confirmation that it's actively being looked at, would be greatly appreciated. Thank you for your time.

Hello! I have a new organization-level Apple Developer account and I'm stuck on the Tax Forms step in App Store Connect (https://appstoreconnect.apple.com/business). The system is showing me U.S. Form W-9 as the only option, but in my case filling out a W-9 would be incorrect — and I'd appreciate guidance from anyone who has resolved this. My setup: I am a non-US individual (not a US citizen, not a US resident, never lived in the US). I am the sole owner of a single-member LLC registered in the US (set up via Firstbase specifically to distribute a mobile app). For US federal tax purposes, this LLC is a disregarded entity — it's not treated as a separate taxpayer from its owner. Why W-9 is not the correct form in my case: The IRS instructions for Form W-9 explicitly state: "If the owner of the disregarded entity is a foreign person, the owner must complete an appropriate Form W-8 instead of a Form W-9. This is the case even if the foreign person has a U.S. TIN." Form W-9 also requires me to certify, under penalty of perjury, that I am a US person — which I am not. The LLC itself doesn't certify anything on a W-9 because it's disregarded; the IRS looks through to the beneficial owner, who in my case is a foreign individual. The correct form for me should be W-8BEN (Certificate of Foreign Status of Beneficial Owner — Individuals). What I've already tried: I opened two support cases 4 days ago and have not received a substantive response yet: Apple Developer Support — Case ID: 20000112974233 Ack Tax / Tax category settings — Team ID: 7YYWN3MYCY, Case ID: 19944616 My questions: Has anyone in the same situation (non-US individual, sole owner of a US single-member LLC) successfully switched the tax form from W-9 to W-8BEN inside App Store Connect? If so, how? Is there a specific path in the Business / Tax Forms section to declare the beneficial owner as a foreign individual that I might be missing? Is there an escalation channel beyond the standard support cases for tax-form issues that are blocking onboarding? Thanks in advance for any pointers.

Hello, My Digital Services Act trader compliance submission in App Store Connect has remained in “In Review” status since July 6, 2026. The status appears under: App Store Connect → Business → Agreements → Compliance → Digital Services Act My agreements, banking information, and tax forms are otherwise active. I have already contacted Apple Developer Support and received case confirmation emails, but I have not yet received a substantive response. Has anyone experienced a similar delay recently? Did the review complete automatically, or was any additional verification required? Thank you.

TITLE: App transfer to new organization account — what happens to the Tap to Pay on iPhone entitlement? BODY: Hi, We have an iOS app live on the App Store that uses the Tap to Pay on iPhone entitlement, approved for App Store (production) distribution. Active merchants use it daily to accept contactless payments. We are planning to transfer the app from the current individual developer account to a new organization account (our company, enrolled with D-U-N-S). The app meets all the app transfer criteria listed in App Store Connect Help. Before initiating the transfer, we'd like to confirm the correct sequence regarding the managed entitlement: Does the Tap to Pay on iPhone entitlement follow the app through the transfer, or does the receiving team need to request it from scratch, including the production distribution review (videos of the user flows, checklist, etc.)? Can the receiving organization account request and obtain the Tap to Pay entitlement (including production approval) BEFORE accepting the app transfer, so there is no gap? During the window between the transfer and the new entitlement approval (if required), does the currently published App Store version keep working normally for end users, including Tap to Pay? Our understanding is that only new builds/updates would be blocked — is that correct? Our goal is zero disruption for active merchants. Thanks in advance for any guidance on the correct sequence.

Hello, My QueenBoard app update was submitted more than four days ago and is still awaiting a review decision. There are no messages in the Resolution Center and no requests for additional information. Details: App: QueenBoard - Logic Puzzle Games Apple ID: 6774414102 Platform: iOS Version: 1.2.4 Build: 26 Submitted: July 26, 2026 at 6:40 PM Current status: In Review Submission ID: 1d5aa681-6804-4aab-9a2c-50c411d856de This is an update to an existing app that has already been approved and published. All required app information has been completed, and I have not received any notice indicating that action is required from me. Could someone confirm whether the review is proceeding normally or whether there is anything I need to provide? Thank you for your help. Best regards, Tim Nguyen

Hello, Our app was removed from sale following a Guideline 5.6 (Developer Code of Conduct) notice on July 22, 2026, citing concerns about "hidden functionality". We responded in detail explaining our multi-tenant, role-based architecture and provided full Review account access with no restrictions. We submitted a corrected build (version 1.1) on July 24, 2026, which has now been in "Waiting for Review" for 11+ days with no update, rejection, or further communication. App Name: Stay Easie Apple ID: 6784701866 Current version: 1.1 Submitted: July 24, 2026 Guideline referenced: 5.6.0 Developer Code of Conduct We have already: Submitted an expedited review request Called Apple Developer Support multiple times Provided complete role-based review credentials and detailed clarifications The app is currently unavailable on the App Store and this is directly impacting our client's business operations. Could someone from the app review team please take a look at this case? Happy to Provide any additional information needed. Thank you.

Hi everyone, I'm wondering if anyone else is experiencing unusually long App Review delays. My app has been in "Waiting for Review" since July 22 at 11:04 PM, and it still hasn't entered the review process. As of today, it's been nearly two weeks with no review activity. I understand that review times can vary depending on workload, app category, and other factors, but this is significantly longer than what I've experienced before. Has anyone else recently faced similar delays? How long did your app remain in "Waiting for Review"? Did it eventually get reviewed without taking any action? Did contacting Apple Developer Support help in your case? I'm mainly trying to understand whether this is a broader issue affecting other developers or if I should reach out to Apple Support. Thanks in advance for sharing your experience.

Our app BandPro (Apple ID 6793207475) has been rejected three times under Guideline 2.1(b) because the In-App Purchase products were "not submitted for review". Everything is ready on our side, but App Store Connect will not let us put the app version and the IAPs into the SAME review submission: New binary uploaded: iOS 1.0 (build 22), attached to the version. 7 IAPs in "Ready to Submit": 4 auto-renewable subscriptions in the group "BandPro Pro" + 3 consumables. All have prices, availability in 175 storefronts, review screenshots and review notes. The app version is locked inside the REJECTED submission ("Unresolved Issues"). The only action available there is "Resubmit to App Review", which sends the version ALONE - exactly what caused the 2nd and 3rd rejections. Adding the IAPs for review creates a SEPARATE draft submission. That draft cannot be sent: it shows "To submit your items for review, add an app version for the selected platform" - but the version cannot be added because it is held by the rejected submission. We replied to App Review in the Resolution Center on Aug 1 explaining this. No response yet. We also saw the recent reply from an App Store Commerce Engineer saying the In-App Purchase submission experience was recently updated and an issue affected some submitted IAPs - our timeline matches that window. Could someone from Apple help us either: (a) attach the 7 ready IAPs to the existing submission so everything is reviewed together, or (b) release the app version from the rejected submission so we can create ONE new submission containing the version + all IAPs? We would like to avoid deleting and recreating the subscription group, since the product IDs are already live in our billing stack and on Google Play. Thank you!

Hello Apple Developer Forum, We have implemented the Declared Age Range API exactly as described in Apple's documentation. Our implementation checks isEligibleForAgeFeatures before calling requestAgeRange, as recommended. We have been testing with different users located in Texas (US) and Brazil. However, for all users, isEligibleForAgeFeatures consistently returns false, so the Declared Age Range prompt is never displayed. We would appreciate some clarification on the following: Under what conditions does isEligibleForAgeFeatures return true? When is the Declared Age Range prompt expected to be shown? Besides the user's region, are there any additional eligibility requirements, such as whether the Apple ID has a verified payment method (credit/debit card), verified identity or address, account age or a phased rollout? Since all of our test users are in supported regions (Texas and Brazil), we expected at least some users to be eligible. However, all four test accounts consistently return false. Could you please clarify how Apple determines eligibility for the Declared Age Range feature and when developers should expect the prompt to appear? Thank you for your guidance.

I paid the $99 annual Apple Developer Program membership fee and submitted my first iOS game, Pippin Plaza, for App Store review on July 21, 2026 at 9:54 PM. Apple publicly states that most app submissions are reviewed within approximately 24 to 48 hours. It has now been nearly 12 days, and my submission is still sitting in “Waiting for Review.” It has never entered “In Review.” There has been no request for additional information, no message from App Review, no explanation for the delay, and no indication that anyone has looked at the submission. I understand that review times can vary and that a first release may sometimes require additional time. However, nearly 12 days without even entering review is far beyond Apple’s publicly stated review timeframe and does not appear to be a normal delay. I contacted Apple Developer Support on July 29, 2026 through the App Review Status support category. Case ID: 20000122288868 Despite contacting support, I have still received no reply, no explanation, and no update regarding the submission. Developers are required to pay Apple $99 annually before they are allowed to distribute apps through the App Store. It is therefore reasonable to expect that a completed submission will at least enter the review process within a reasonable period, or that Apple will communicate when there is a significant delay. Is this currently considered normal for first-time app submissions? At what point should a developer conclude that a submission is stuck rather than merely delayed? Why has there been no response from Apple Developer Support since July 29, despite the submission already being delayed far beyond the stated review timeframe? I am not asking for special treatment, guaranteed approval, or an expedited review. I am asking for my completed submission to enter the review process, or for Apple to explain why it has remained untouched for nearly 12 days.

Hi everyone, My app has been stuck in "Waiting for Review" since July 22, 2026 (more than 11 days). The app is in the Productivity/Lifestyle category and only uses Sign in with Apple for authentication. It does not contain any sensitive content or unusual functionality. I have already contacted the App Review team twice and also reached out to Apple Developer Support, but I haven't received any response yet. Has anyone experienced such a long "Waiting for Review" period for a first submission? Is there anything else I can do besides waiting? Thank you!