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 app update (Huroofi, Apple ID 6818857035, version 1.0.3) was submitted on October 14, 2026 and is still in "Waiting for Review" after 6 days. There are no messages in App Store Connect. I also contacted App Review on October 18 (Case ID 103000800575) and have not received a reply yet. Could someone from App Review please check whether anything is blocking this submission? Thank you.

Hello Apple App Review Team, I'm seeking urgent assistance with Carrying The Fire (Apple ID: 6820179361), submitted on 9 October 2026, which has now remained in "Waiting for Review" for over eight days, without progressing to active review. An expedited app review request was also submitted. The app is an essential component of a major government-funded public arts event on 7 November 2026 in Albany, Western Australia, involving approximately 2,000 community participants. The event is presented by FORM as part of Albany 2026, with support from the Australian Government's Festivals Australia program and Lotterywest. The performance depends on participants downloading and preparing the app well in advance. Our planned distribution period is already underway, and the continued delay is directly affecting participant preparations and putting the event at risk. The Android version has already been approved and published on Google Play, but iOS participants are currently unable to download or prepare the app, creating an increasingly concerning issue as the event approaches. We have submitted a formal expedited-review request and contacted Apple Developer Support twice (Case ID: 102994798591), but have received no response. Given the fixed event deadline and the significant number of participants affected, could an Apple App Review representative please urgently investigate our submission and escalate it to the appropriate team? Official event information: https://www.albany2026.com.au/events/carrying-the-fire Any help here would be truly appreciated. Thank you for your assistance.

Our Apple Developer Program membership for Avorp LLC was recently terminated under Section 3.2(f), citing “documented indications of fraudulent conduct associated with” my account. I am trying to understand the basis for this decision. Avorp LLC is a legitimate and independently operated U.S. software company. Its enrollment information was verified by Apple, and the account currently has no published apps on the App Store. I have not engaged in fraudulent reviews, payment fraud, account circumvention, or any other dishonest activity through this developer account. Like I said we don't even have a published application yet. I also work professionally as a freelance software developer and have previously worked on unrelated client projects involving Apple development resources. If an association with a former client account, project, device, or development environment contributed to this termination, I would like to clarify that such client work is entirely separate from Avorp LLC and does not imply ownership of or responsibility for the client's account or activities. The termination notice does not identify the specific activity, account, transaction, application, or association that Apple considers fraudulent. I have already submitted a reinstatement request. I am posting here to ask whether an Apple representative can clarify the appropriate escalation path for a manual review of the account associations involved in a Section 3.2(f) termination. I am fully prepared to provide company records, contracts, client-work documentation, or development records if needed to verify that Avorp LLC is independent and legitimate.

Hi App Review team, Our app has been in "Waiting for Review" since October 4, 2026, with no status change and no message in the Resolution Center. App name: Hangpost Apple ID: 6784063100 Version: 1.0.0 (build 49) Submitted: October 4, 2026, 5:51 PM ET Submission ID: 82c9fd8e-b56e-4491-afbd-f4295573edae Release option: Manual release What we've done so far: Checked the Resolution Center and our developer account email regularly Submitted an expedited review request through Contact Us Kept the build and metadata unchanged so as not to reset our place in the queue Two demo accounts with fixed sign-in codes are in the Sign-In Information, and the review notes explain the sample content and how to test account deletion. If anything about the submission needs to change, we're happy to fix it right away. We'd appreciate any update on its status. Thank you!

Our app (Apple ID 6813163966), has been in "Waiting for Review" since October 6, 2026, with no movement. Timeline: Sep 29: Version 1.1 (build 18) submitted along with our first subscriptions. Oct 6: Rejected under Guideline 5.1.1(iv). The only issue was the button wording on our Health permission pre-prompt. Oct 6: Fixed exactly what was asked, resubmitted the same day as version 1.2 (build 30), and replied to App Review in App Store Connect explaining the change. Since then: "Waiting for Review" for 9 days. The submission and all four items (the app version, the subscription group, monthly and annual) show the same status. Submission ID: 0a3b29e8-9d30-4ff6-972b-08a324a69034 This is our first release, so the app is not on the App Store at all yet. We pay $99 a year for the Apple Developer Program, and we have yet to ship anything with it. We planned our launch around the first review timeline and have paid marketing running and committed for it. Every day in the queue is budget spent sending people to an app they cannot download. We already had to drop an October in-app event because of the delay, and our featuring nomination has a publish date of October 20. We understand review volume changes, and we are not asking to skip anything. We would just like to know: Is this submission actually in the queue, or is it stuck in a state that needs someone to look at it? Is there anything on our side (metadata, review notes, the reply) that is holding it? If anyone from App Review can take a look at the submission ID above, we would be very grateful. Thank you.

We are experiencing an issue when inviting a user to join our Apple Developer Program team through App Store Connect Users and Access. The purpose of adding this user is to include them as an internal TestFlight tester after the invitation is accepted. The invited user received the Apple Developer invitation email and clicked the "Accept invitation" link. The invitation link opens the following page: https://appstoreconnect.apple.com/activation_ds?key=... The page displays "Sign in to accept your invitation" and asks the user to sign in with an Apple Account. After the user signs in successfully, the page redirects back to the same sign-in page and asks the user to sign in again. The invitation cannot be accepted, and the user cannot join the Apple Developer Program team. Steps to reproduce: Go to Users and Access in App Store Connect. Add a new user and send an invitation to join the Apple Developer Program team. The invited user receives the Apple Developer invitation email. The invited user clicks the "Accept invitation" link. The page opens appstoreconnect.apple.com/activation_ds. The user signs in with an Apple Account. After signing in, the page redirects back to the same sign-in page. Repeating the sign-in process results in the same redirect loop. Expected result: The invitation should be accepted after the user signs in, and the user should be added to the Apple Developer Program team. Actual result: The page keeps redirecting back to the sign-in page, and the user cannot accept the invitation. Troubleshooting already tried: Safari and Chrome Private browsing mode Clearing browser cookies Signing out of Apple ID before opening the invitation link again Opening the link directly in the browser instead of an email app embedded browser The issue still occurs.

The specs page is ambiguous. If the device has two screens, how do we decide which screen to market for? The console accepts both sizes right away, but it's only 10 slots. Any and all help appreciated.

Hello, Our new app Grab&Go (Apple ID 6821716640, iOS 1.0.0) was submitted on October 12, 2026 and has remained in "Waiting for Review" ever since. The review has not started. Submission ID: f110bb29-a29b-4fe7-bd8f-51852fbc48a3 The submission contains the iOS app version and a custom product page. Expedited review was requested and approved twice. Agreements, Tax, and Banking are all active, and there are no messages or issues in App Store Connect. Our other apps on the same account are live and in good standing. We have contacted App Review (case IDs 102999390329 and 103002511991) but have not received a response yet. Has anyone experienced a similar delay with a first submission? And could someone from App Review check whether anything is holding this submission or if anything is needed from our side? Thank you.

Hello, We submitted two related iOS apps for review and neither has been approved yet: App ID [1234567890]: submitted 29 Sep 2026, status: [Waiting for Review] App ID [1234567890]: submitted 8 Oct 2026, status: [Waiting for Review] Neither app has had any update or message for more than 20 days. The demo account and review notes are filled in for both apps. If anything is missing, please let us know and we will fix it straight away. Any guidance would be appreciated. Thank you.

My last two approved versions of my app are showing "Ready for Distribution" in App Store Connect, but none of the storefronts lets the user gets the latest update. Here's what happened 0.13.1 (build 49) was approved on 13 October. The release type was “Automatically release after approval”. The state is READY_FOR_SALE with downloadable = true, and no phased release is set. 0.13.2 (build 50) was approved on 18 October with the same release type. It is also Ready for Distribution. The App Store and Apple’s public lookup API (itunes.apple.com/lookup?bundleId=…) still return 0.11.0 (released 3 October, minimum iOS 17.6). I checked the US, IN, GB, CA, AU, DE, SG and AE storefronts. It is not a device issue. iPhones on iOS 18.2 and iOS 27 also show 0.11.0 as the latest version. Impact Our iOS users cannot get the new version. The in-app update prompt sends them to a store page that offers only 0.11.0. We had to turn off open challenge events that need the new version, so users cannot join them. This release introduces new in-app purchases, including an annual plan with a free trial, so the delay also affects our revenue. The app ID is 6760958527. I opened Apple Developer Support case 102996444113 and have not had a reply yet. Has anyone seen a release stay stuck like this for days? Is there anything on the developer side that I should check or try? I would be grateful for any pointers.

Hello App Review Team, We would like to request an expedited review, and confirmation of the status, for our iOS app. It has been in "Waiting for Review" for 8 days since we resubmitted it after fixing a 2.3.6 rejection, and it has not moved to "In Review". Why this is time-sensitive Sijangpass is used in person: customers scan a QR code at partner restaurants and show the benefit screen to the owner at the counter. Our in-store service went live on October 14 at our partner restaurants. Android and web users are already using it, but iPhone users cannot get the version the restaurants now use, so customers and owners are running into problems at the counter every day. This is a live, real-world service, not just a release date. App information App name: Sijangpass App Apple ID: 6804940537 Bundle ID: com.blacktae.sijangpass Version / build: 1.1.0 (12) Submission ID: a09bf07f-d892-443f-afb5-f8d5cac78d10 Submitted: October 13, 2026, 1:21 AM KST Timeline Oct 12: Build 8 was rejected under Guideline 2.3.6 because one of our age rating answers had been selected by mistake. The app has no such content: the in-app "draw" is a free promotional giveaway by partner restaurants. Nothing is purchased to take part, and nothing of value is at stake. Oct 12: As the rejection message instructed, we corrected those age rating answers to None/No, replied in App Store Connect, and resubmitted. Oct 13: Resubmitted with build 12. The App Review notes also explain the rating correction. No messages since. Oct 13 and Oct 17: Requested expedited review; both confirmations said the review would be expedited. Oct 15 and Oct 17: Contacted Developer Support (case 102997225516). Oct 19: Phone call with Developer Support (case 103001164366); we were told it was forwarded and we would hear back by email. For comparison, our other app on the same account (Sijangpass Owner, 1.0.3) was submitted on Oct 16 and approved within a day. What we are requesting The Oct 12 rejection included the "Extended Review" notice. Is Extended Review applied to this app, and does it still apply now that the rating has been corrected? Is there anything we should do about it? Is anything else required from our side for this submission? If nothing else is needed, an expedited review of the October 13 submission. We are not withdrawing and resubmitting, so as not to lose our place in the queue. Thank you very much for your time. If you are in the same situation, please share your submission date below or boost this post so App Review can see how widespread this is.

Hello Apple Developer Team, I am experiencing a serious TestFlight issue affecting multiple applications under my Apple Developer account. The issue started on October 9, 2026. 1. All existing TestFlight builds suddenly expired On October 9, all previously available TestFlight builds across multiple applications unexpectedly changed to "Expired" at the same time. These applications were previously available for testing. 2. Newly uploaded builds cannot be installed I uploaded new builds to replace the expired ones. The uploads completed successfully, and App Store Connect shows the new builds as "Ready for Internal Testing." For example: App: Mai Anh Kiếm Version: 1.0 Build: 135 TestFlight shows approximately 89 days remaining. However, when an internal tester taps Install or Update, TestFlight displays the following error: "Could not install Mai Anh Kiếm. The requested app is not available or doesn't exist." Therefore, even newly uploaded builds cannot be installed through internal testing. 3. External Beta App Review submission fails When I attempt to submit a new build for external TestFlight review, App Store Connect returns HTTP 422 with the following error: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Error detail: "Beta Contract is missing." 4. Account information I am the Account Holder and Admin. My Free Apps Agreement and Paid Apps Agreement are both Active. New builds can be uploaded and processed successfully. The issue affects multiple applications, not just one app. 5. Apple Developer Support response I contacted Apple Developer Support. Support Case ID: 102990933108 Apple Support confirmed that build 1.0 (135) is ready for internal testing, but this does not resolve the actual problem: internal testers still cannot install the build. My questions: Why did all existing TestFlight builds suddenly expire at the same time? Why are newly uploaded builds unavailable for installation, even for internal testers? What causes BETA_CONTRACT_MISSING when all visible agreements are active? Could this indicate an account-level TestFlight distribution or Beta Contract issue that requires intervention from Apple? Could an Apple TestFlight engineer please investigate this issue or advise how to get it escalated? I can provide screenshots of the installation error and the API response. Thank you for your assistance.

Submitted my first app on October 12 and it’s been sitting in Waiting for Review ever since. Never moved to In Review, no messages, nothing in App Store Connect asking me for anything. It’s CFI Copilot, an iOS app for flight instructors. Submitted with a subscription group and two subscriptions (monthly and yearly). Agreements, tax and banking are all done, and there’s no login so no demo account needed. I sent a status request through Contact Us on the 16th but haven’t heard back. Is anyone else stuck this long on a first submission right now? If yours finally went through, how long did it take and did you do anything to get it moving? Apple ID: 6817115452 Submission ID: 6b2d4d89-3601-42b8-af76-2d813ac0b1b6

Hello, I am the sole owner of a single-member LLC registered in Wyoming, USA. I am not a US person and I live outside the United States. For US tax purposes the LLC is a foreign-owned disregarded entity, so as I understand it the correct form is a W-8BEN in my name as the foreign owner, not a W-9. In App Store Connect, under Business > Agreements, Tax, and Banking, the tax form section only offers the W-9 because the account is set up as a US entity. Because of this I cannot complete the tax information, and the Paid Apps Agreement stays inactive. My app is ready and has in-app purchases, so I cannot submit it for review until this is resolved. I have already contacted Apple Developer Support and I am waiting for a reply. Questions: Has anyone with a foreign-owned single-member US LLC solved this? How did you submit a W-8BEN instead of a W-9? Is there a way to change the tax form type in App Store Connect, or does Apple need to change it from their side? Is there a specific contact or form for this case? Any guidance would be appreciated. Thank you.

Hello Apple App Review Team and Community, We would like to request an expedited review of a critical bug fix update for HungryAliens (App ID: 6449141384), which is currently live on the App Store. Our large-scale competitive multiplayer feature, Guild Conquest, launched on September 15, is experiencing critical issues, including a bug that prevents players from defeating a boss. These issues are directly affecting active players and disrupting normal gameplay progression. On October 13, our update was rejected due to an issue with an App Store screenshot. We corrected the screenshot and requested a re-review within approximately two hours. However, the review did not resume, so we withdrew the original submission and submitted a new build on October 19. The latest submission remains in "Waiting for Review" status, preventing us from delivering the necessary critical fixes to our players. App Information App Name: HungryAliens App ID: 6449141384 App Bundle ID: com.DetailGames.HungryAliens Timeline September 15: Launched Guild Conquest, a major competitive multiplayer feature. October 13: The update containing critical bug fixes for Guild Conquest was undergoing App Review. October 13: Received a rejection under Guideline 1.1 (Safety – Objectionable Content) related to an App Store screenshot → Corrected the screenshot and submitted the revised material through App Store Connect within approximately two hours, requesting the review to resume. October 13–19: Despite our prompt response, the review did not resume, delaying approval of the critical bug fix update. October 19: Withdrew the previous submission and resubmitted a build containing the necessary fixes. October 20: The latest submission remains in "Waiting for Review" status. Why This Is Urgent Guild Conquest is a large-scale competitive multiplayer feature involving many players, where accurate information display is essential. However, issues affecting this functionality are currently occurring. A critical bug is preventing players from defeating a specific boss in Guild Conquest, disrupting normal gameplay progression. These issues directly affect the gameplay experience and competitive fairness of players currently participating in the content. Although we promptly addressed the review feedback on October 13, the update has still not been approved, preventing us from delivering the necessary bug fixes. What We Are Requesting Expedited review of our October 19 submission, considering the critical gameplay issues affecting our live service. Confirmation of the current review status. Guidance on any additional information or actions required from our side. We understand and respect Apple's App Review Guidelines and review process, and we have made every effort to respond promptly to the feedback provided. We apologize for the urgent request and would sincerely appreciate your assistance in reviewing this critical bug fix update as soon as possible. Thank you for your time. We look forward to your response.

Hello App Review team, I’m requesting assistance with two private internal business apps for our employees: • Crew Safety — Apple ID: 6816491059 • CrewOS Hub — Apple ID: 6816324323 Crew Safety was submitted on September 28, 2026, and has remained in “Waiting for Review” for three weeks without progress or an explanation. CrewOS Hub was originally submitted around the same time, then withdrawn and resubmitted in October after changes. It is also waiting for review. We have previously received approvals under this developer account, including some within 24 hours. App Review support case: 102993493885 I contacted support on October 11 and followed up on October 14. The case was subsequently closed without a substantive response or resolution. Phone support has been unavailable when I checked. I also submitted an expedited review request today, October 19. Our company legally changed its name from Crew Electrical Services Ltd. to Crew Technical Services Inc. The developer account still displayed the former name. Account information update case: 102997958035. Could someone please investigate whether either submission is blocked by an outstanding account verification, the company name update, or missing review information? These apps are intended strictly for our employees’ internal workflows. Please confirm what action, if any, is required from us and provide a clear next step. Thank you, Cory Magee Owner, Crew Technical Services Inc.

My first app submission has been in "Waiting for Review" since October 4, 2026. I cancelled and resubmitted on October 15; the current submission ID is 6d46b9b6-ed68-4d3c-a49c-20a9c97c15c9. An expedited review was accepted on October 13 for the earlier submission, and I requested one for the current submission today. Developer Support case 102995608270 has had no reply. Agreements and DSA status are active, and there are no messages in App Store Connect. Could someone from App Review check whether this submission is stuck, or whether anything is needed from my side? Thank you.

Hello, Our first iOS app, Kaikōdo: Travel your way (Apple ID: 6798173537, version 1.0), was submitted for review on October 4, 2026 at 15:00 CEST and has been in "Waiting for Review" ever since, with no messages or feedback in App Store Connect. We contacted App Review on October 11 (case ID 102993087879) without a reply, and followed up on the same case today. The submission includes a demo account and reviewer notes. Could someone from App Review take a look, or let us know if anything is missing on our side? Thank you.

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

Our first app has been in “Waiting for Review” for 7 days following a resubmission, and I'd appreciate help understanding whether anything on our side is holding it up. App name: Tirata Apple ID: 6770620365 Version / build: 1.0.0 Submission ID: 823c3bd8-1add-433d-a7f2-dae3682a562c Sep 27: First submitted Oct 7: Rejected under guideline 2.1; addressed the issue and resubmitted the same day (within 30 min), with notes in the App Review reply thread Emailed developer support twice; received the standard high-volume reply All agreements, tax, and banking info are active in App Store Connect No unread messages in the App Review section Demo account credentials in review notes are valid We need the app for a live launch event on October 18 and requested an expedited review but found no movement. It's been a week since our request. If there's anything we can do on our end, please let me know.