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 have been rejected twice under Guideline 2.1(b) because my In-App Purchase subscriptions are not submitted for review. I cannot figure out how to attach them to my submission. Here is my situation: I have 6 auto-renewable subscriptions fully configured in App Store Connect under "Barrel Pro Subscriptions" — all have screenshots, pricing, descriptions, and review notes My app is iOS only, built with React Native/Expo My current version is 1.1, Build 10 (1.1.0) The problem: The "In-App Purchases and Subscriptions" section does not appear anywhere on my version page. I have scrolled to the very bottom and it is not there. I cannot find any way to attach my subscriptions to my submission before clicking "Submit for Review." The blue info box on the Subscriptions page says: "Your first subscription must be submitted with a new app version. Select it from the app's In-App Purchases and Subscriptions section on the version page." But that section does not exist on my version page. What I have tried: Cancelling the rejected submission and starting fresh Creating a new version (1.1) manually Uploading a new build (Build 10) Checking both "In-App Purchases" and "Subscriptions" sections in the sidebar Has Apple removed this section from the version page? How do I attach my subscriptions to my submission in 2026? Any help is greatly appreciated. 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, I am posting here as a last resort after multiple unsuccessful attempts to contact Apple Developer Support through other channels. Timeline of my situation: I enrolled in the Apple Developer Program through the Apple Developer app on iPhone, and the annual membership fee was successfully charged to my credit card. The subscription appears as active under my Apple ID subscriptions. I was then asked by Apple Developer Relations to provide identity verification documents. I submitted my government-issued ID as requested. I received an email from the Apple Developer Relations Team confirming receipt of the documents, stating: "Thank you for providing the documents we requested. We will review them and follow up with you within two business days." That two-business-day window has now been exceeded by more than a week. Total elapsed time since document submission: 10 days. I have since sent three follow-up emails to Apple Developer Support. None of them have received any response. The Apple Developer app shows the message: "Enrollment through the Apple Developer app is not available for this Apple Account", and redirects to the web. On the web, the enrollment page shows "Purchase your membership" and asks me to complete my purchase, as if I had never paid. I have not clicked that button to avoid being charged a second time. reportaproblem.apple.com does not allow me to take any action on this subscription. At this point my payment, my submitted documents, and my enrollment status appear to be disconnected from each other in Apple's systems. The payment is confirmed, the documents were submitted as requested, but the enrollment remains in a pending state with no communication. I have seen several similar cases in this forum during 2026, some of which were resolved when Apple staff intervened directly. I would greatly appreciate if someone from Apple could review my case internally, confirm that the payment is linked to my enrollment, and allow the document review to proceed. If that is not possible, I would need clear guidance on how to obtain a refund of the membership fee that was already charged. I am happy to provide my Apple ID, the date of the charge, or any other information needed via a private channel. Thank you in advance for any help.

Hello, I am unable to install my app from TestFlight even though the build appears valid and is in internal beta testing. The build was uploaded successfully to App Store Connect and shows as Testing / Internal Testing. The build metadata looks valid: processingState: VALID internalBuildState: IN_BETA_TESTING qcState: BETA_INTERNAL_TESTING usesNonExemptEncryption: false minOsVersion: 15.0 deviceFamilies: IPHONE supportedArchitectures: arm64 However, TestFlight installation fails, and the App Store Connect API returns: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Beta contract is missing for the app. My App Store Connect agreements are all active. I checked Business > Agreements and both Paid Apps Agreement and Free Apps Agreement are Active. Bank accounts, tax forms, and compliance also appear Active. This also happens with a newly created app and a fresh build, so it looks like the TestFlight beta contract may be missing or detached on Apple’s backend. Has anyone seen this before, or is there a way to force App Store Connect to refresh the TestFlight beta contract state?

Hello fellow developers and Apple Review Team, I am reaching out to the community and any Apple App Review representatives here as a matter of absolute business urgency. Our essential health app, BeatO Diabetes Management (App ID: 1070739458), has been effectively paralyzed in the review queue for nearly 40 days (since late April 2026), severely impacting thousands of chronic care patients who rely on our ecosystem daily for blood glucose tracking. We are completely aligned with Apple’s rigorous safety standards, but we have reached an operational dead end where detailed, compliant answers are met with week-long silence. ⏱️ The Timeline of the Review Deadlock: Late April 2026: Initial build submitted. Flagged under Guideline 1.4.1 (Safety - Physical Harm) regarding our connection to external hardware (a CE-certified glucometer). May 12, 2026: We provided absolute regulatory documentation: official CE certifications, supplier details, clinical validation reports, and proof of prominent American Diabetes Association (ADA) threshold disclaimers inside the UI. May 15, 2026: Apple responded stating: "Your submission's review will require additional time... We do not require any further information at this time." May 26/27, 2026: After a prolonged freeze, we halted the initial release to clear the pipe and submitted a completely fresh build (Submission ID: a0bf3856-693b-4577-adc7-9199a5f9fe34) hoping to reset any stuck internal states. May 27, 2026: Apple requested information under Guideline 2.1 (Information Needed) asking two specific questions about algorithmic personalization and our "tailored diabetes program" marketing text. May 27, 2026: Within a couple of hours, we provided an exhaustive, definitive response: Clarified ADA Guidelines: Confirmed that high/low glucose classifications are strictly based on standard published clinical data (ADA Standards of Care) and explicitly disclosed in our Terms & Conditions, not personalized by an algorithm. Clarified Program Architecture: Proved that 0% of the program is generated by an algorithm. The app acts purely as an introductory storefront/brochure. The actual care management is fulfilled entirely offline directly by human doctors and certified medical professionals. It is definitively not an algorithmic medical device feature. May 28, 2026 to Present: The app was re-entered into the "In Review" state and has sat completely frozen ever since. 🛑 The Core Problem & Business Impact We have successfully provided every piece of documentation Apple has asked for - legal, medical, clinical, and architecture definitions. The reviewer explicitly stated they have everything they need, yet we are trapped in an endless manual review loop. Because our app manages active diabetic health metrics, this prolonged delay prevents us from deploying critical performance optimizations and bug fixes. Our patient support lines are flooding, and our operational product roadmap for the quarter is completely stalled. 🙏 Request to the Community / Apple Engineers Has anyone else dealing with health hardware/software integration hit this specific wall where your answers are fully compliant, but the review desk simply stops processing the ticket? If any Apple App Review moderators or App Store Connect engineers see this, we respectfully request an internal escalation or an App Review Appointment to unblock this build. We are ready to jump on a call immediately to provide any final clarity required. App Name: BeatO Diabetes Management App ID: 1070739458 Latest Submission ID: a0bf3856-693b-4577-adc7-9199a5f9fe34 Thank you for your time and guidance. Regards, Sanketkumar Biswas

Hi, I can sign in to my Apple ID, but my Apple Developer account shows a “closed” status and I’m unable to access App Store Connect features. My app is currently showing “Ready for Distribution,” so the account appears active, but developer access is restricted. I’ve already contacted Apple Developer Support and am waiting for their response. Also, I temporarily can’t access my primary email due to a verification issue, so I’ve provided an alternate contact email and phone number in my support request. Has anyone experienced a similar situation or knows possible reasons for a “closed” developer status while the app remains approved? Thanks.

About 90% of the time I attempt to upload my app build to App Store Connect 'Internal Testing Only', it gets stuck on either "Sending SPI Analysis to App Store Connect" or "Waiting for App Store Connect SPI Analysis Response". The only solution I've seen is to sign in and out of my dev account in Xcode and close the app - and keep repeating this process until it works again. Sometimes it takes one, sometimes it still won't work after doing this 10 times. I learned that I can export the IPA and upload via Transporter which I have been doing recently. But this is an extremely annoying problem that I do not understand why it continues to happen every session, and I have seen barely any other forums anywhere with this same issue. Can anyone help?

I recognize that Apple has put out documentation on how to do things with the new Age APIs, but I have no idea what my apps are supposed to do to be in compliance with this law. Most of the law sounds like it applies to App Store developers like Apple, more than it pertains to individual app devs. If the age rating of an app changes, wouldn't we just put it in App Store Connect and have Apple disable those apps on the devices of the underage kids?

Hello, I’m currently dealing with an App Review situation that has been stuck with no real progress and no useful feedback from Apple. App Name: Juego de Impostor: Palabras Apple ID: 6757995242 Bundle ID: com.rgioia.impostorwords Version: 1.8.0 Current Status: Ready for Review Previous Version: 1.7.0 Ready for Distribution Timeline: The app/update has been waiting for review for an unusually long time. There has been no clear movement, no rejection, no explanation, and no actionable feedback from the review team. This is especially frustrating because this is not a new experimental app or an unclear submission. The app is already prepared for release/update, and I need to push fixes and improvements for users. What I already did: Requested expedited review → approved Contacted Apple Developer Support multiple times Followed up several times Waited without receiving any meaningful update The only response I received was that the expedited review request was accepted, but after that nothing actually happened. Impact: The app/update is completely blocked I cannot release fixes or improvements There is no rejection reason to fix There is no communication from App Review I have no visibility into whether this is a review queue issue, an account issue, or a pipeline problem At this point, this does not feel like a normal App Review delay. It feels like the submission is stuck somewhere internally with no owner and no progress. Questions: Is anyone else experiencing this kind of delay recently? Is there any real way to escalate a stuck App Review case after an expedited review was already approved? Could this indicate an issue with the App Review pipeline or my account/app status? How can I get someone from Apple to actually look into the submission instead of receiving generic support replies? I understand that delays can happen, but having an app/update blocked for this long with no feedback, no rejection, and no progress is not acceptable for developers trying to maintain a live product. Any help, visibility, or escalation path would be appreciated. — Ramiro Gioia

Hello, My first macOS app has been in “Waiting for Review” status since May 26. I have already checked my Apple Developer account, agreements, tax and banking information, app metadata, pricing, and in-app purchase configuration, and everything appears to be in order. Is there anything else I should check or do at this point, or is it normal for a first app review to remain in “Waiting for Review” for this long? Thank you.

Hello App Review Team, I wanted to follow up because my app, BitzaHugs, is still showing as Waiting for Review, and I was informed that my case was expedited and in active review. I addressed all previously cited rejection issues and resubmitted the app, but I am still waiting for the review to move forward. App Name: BitzaHugs Support Case #: 102903001544 Current Status: Waiting for Review Expedited Review: Requested again / currently active I completely understand that review times can vary, but because my app has already gone through multiple rejection cycles, the issues have been resolved, and my intended launch date has passed, I would greatly appreciate any update or escalation if possible. Please let me know if there is anything else needed from my side to help move the review forward. Thank you again for your time and assistance, Amanda Benavidez

Hello, I ran into an issue today after receiving a metadata rejection. My current situation: Rejection (Guideline 2.3.2): My app was rejected for its Metadata — I needed to update the description to clearly disclose that full access requires an in-app subscription as requested by the reviewer. Accidental Resubmission: Before reading Apple's instructions carefully which stated I did not need to resubmit and only save the new app description, I accidentally hit "Add for Review" instead of simply saving the updated description and replying via App Store Connect. App Store Connect Reply Option: After cancelling the accidental submission, the App Store Connect reply option became inaccessible. Current State: I've since resubmitted via "Add for Review" with the corrected description already in place. Previous Review time: I have previously experienced an unusually long "Waiting for Review" period — significantly past the 24–48 hour window before my review. Current App Status: My Current App Status shows "Waiting for Review" again and I am afraid I may have restarted the entire review even though my app was only rejected for the App Description and I may have to wait a long time now as I did for my previous review. Developer Support Email (Case ID: 102905099480): I've also contacted app support and have received no response as of yet. Developer Support Phone Call: When navigating to App Review under Apple Support, the option to request a phone call is not available for this issue. Has anyone else had this problem? And what should I do? Thank you.

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.

I am experiencing a significantly long review period for my macOS app. I submitted my app for review on May 25th at 8:58 PM, and it has been stuck in the 'In Review' status since then. It has now been over a week without any updates or feedback. I have noticed a recurring pattern of macOS app reviews taking much longer than usual lately. Is there a known backlog or a change in the review process for the macOS platform? It would be helpful to know if others are facing similar delays to understand if this is a broader trend at the moment. Thanks in advance.

Title: Unable to upload app after App Transfer – ITMS-90076 Team ID mismatch (Keychain access issue) Body: Hello, I am experiencing an issue when uploading an iOS app after an App Transfer between two developer accounts. Current situation: The app has already been transferred to a new Apple Developer Team The app appears correctly under the new team in App Store Connect The Bundle Identifier remains the same I am building the app using the new Team's Apple Distribution certificate A new App Store provisioning profile has been created for the new Team However, when attempting to upload via Xcode Organizer (Distribute App → App Store Connect → Upload), the upload fails with the following error: ITMS-90076: Possible loss of keychain access. From my understanding: The previous app versions were signed with the old Team ID The new build is correctly signed with the new Team ID This seems to indicate that although the App Transfer is complete from a UI perspective, the App Store backend still compares against the previous Team ID. Questions: Is this expected behavior immediately after an App Transfer? Is there any required step to fully synchronize or refresh the app’s Team ID internally? Should it be possible to upload successfully after transfer without changing the Bundle ID? Is there a known delay or internal process before uploads from the new Team are accepted? Additional info: Xcode version: [your version] Newly created archive after transfer Certificates and provisioning have been recreated under the new Team Any guidance or similar experiences would be greatly appreciated. Thank you. 日本語 現在、App Transfer後のアプリをアップロードする際に問題が発生しています。 【状況】 ・アプリは新しいApple Developer Teamへ移転済み ・App Store Connect上でも新しいTeamに表示されています ・Bundle Identifierは変更していません ・新TeamのApple Distribution証明書でビルドしています ・新しいApp Store用Provisioning Profileも作成済みです しかし、Xcode Organizerからアップロード（Distribute App → App Store Connect → Upload）を実行すると、以下のエラーで失敗します。 ITMS-90076: キーチェーンアクセスの喪失の可能性 【認識】 ・旧バージョンは旧Team IDで署名されている ・新ビルドは新Team IDで正しく署名されている 【疑問点】 App Transfer直後にこの現象は仕様として起こるものでしょうか？ 内部的にTeam IDの同期や再反映を行う必要はありますか？ Bundle IDを変更せずにアップロードは可能な想定でしょうか？ App Transfer後にアップロードが可能になるまでタイムラグはありますか？ 【補足】 ・アーカイブはTransfer後に新規作成しています ・証明書およびプロビジョニングは新Teamで再作成済みです 同様の事象や解決方法をご存じの方がいらっしゃいましたら、ご教示いただけますと幸いです。 よろしくお願いいたします。

Hello, I am requesting urgent assistance with my app review. I have been through multiple rejection cycles, addressed every issue raised, and resubmitted, but I have not received any response on my most recent submission despite having an active expedited review request. Here are my details: App Name: BitzaHugs Original Submission Date: 05/24/2026 Expedited Review Requested: 05/30/2026 Current Status: Waiting for Review Support Case #: 102903001544 I have fully resolved all previously cited rejection reasons and resubmitted accordingly. My intended launch date has now passed by two days and every additional day of delay has direct business impact. I am not seeing any flags or errors in App Store Connect on my end. I would greatly appreciate any escalation or update on the status of this review. Thank you for your time, Amanda Benavidez

I haven't updated my app in months, but I discovered my app icon color recently changed entirely on its own, and it displays inconsistently in App Store, App Store Connect, and TestFlight. Everything works fine locally during development. It's all as expected in Icon Composer and Xcode. Typically, the icon shows a white symbol on a blue background. But now, online, the white symbol is a dark red color, and there seem to be additional Liquid Glass and shadow effects that I never chose. So, somewhere in Apple's backend processing of my .icon file, it's getting malformed and rasterized with different parameters than expected? And different cached versions are being displayed in different places? On web, it's showing the incorrect version. Same in App Store Connect and TestFlight. In App Store on iOS, the incorrect version is shown in search results, but the correct version is shown on the product page. I've attached some screenshots. Store link: https://apps.apple.com/us/app/kitchenkit-grocery-organizer/id6754018760 Related threads: https://developer.apple.com/forums/thread/812852 https://developer.apple.com/forums/thread/811770 https://developer.apple.com/forums/thread/823078

Hello, I honestly don’t understand what’s going on with my app review. My app was already approved before, and I submitted a new build on April 7th with some new features and important bug fixes. Since then, it has been stuck on “Waiting for Review” with absolutely no update. It’s been 40 days now, which is honestly unacceptable. I even submitted an expedited review request, but that didn’t help either. The worst part is that this build contains bug fixes for users, and the delay is directly affecting the app experience. Waiting this long without any response or progress is really frustrating. Can someone from Apple please look into this and help resolve it ASAP? Thank you.

How do I delete my app which is in the prepare for submission state. My previous version was rejected and so I updated my version number to get back to the prepare for submission state, however I am still getting the same error which is "The app is unable to be removed right now" with no more information.

Hello everyone, I've been unable to install any TestFlight build on my device for over a week. Every build shows "Complete" in App Store Connect, but installation always fails with the same error. I also submitted a support ticket to Apple Developer Support over a week ago but have not received any response. I'm posting here hoping someone from the community or Apple team can help. Error Message "The requested app is not available or doesn't exist" (Turkish: "İstenen uygulama kullanılamıyor veya yok") Environment Device: iPhone 17 Pro Max iOS: 26.4.2 App: Easyway Digital Library Bundle ID: com.abacusai.turkishsocialme.t1777823268 Build Framework: React Native (Expo SDK 54) What I've Tried (Nothing Works) ✅ Multiple builds uploaded (build 4, 5, 6, 7, 8) — all show "Complete" ✅ Deleted and reinstalled TestFlight app ✅ Signed out and back into Apple ID on device ✅ Restarted iPhone ✅ Tried different browsers (Safari, Chrome, Firefox) ✅ Tried Internal Testing — receive email but can't install ✅ Tried External Testing — same error ✅ Tried creating Public Link — same error ✅ Cleared browser cache, tried Incognito mode ✅ Verified Export Compliance (ITSAppUsesNonExemptEncryption: false) ✅ Paid Apps Agreement: Active ✅ Free Apps Agreement: Active ✅ Bank & Tax info: Complete Build Status in App Store Connect Version & Build: 1.0.1 (8) Status: Complete Date Created: May 15, 2026 Timeline May 8, 2026: First build uploaded — same error started May 10, 2026: Paid Apps Agreement activated May 15, 2026: Still the same error after 8 builds Apple Support — No Response Submitted a support ticket on approximately May 8, 2026 Category: App Store Connect & TestFlight Issue: Cannot install builds via TestFlight Status: No response received after over 1 week No case number update, no email reply Questions Has anyone experienced this with a new app on TestFlight? Is there a known issue with TestFlight and new Bundle IDs? Could this be related to the Paid Apps Agreement activation delay? Is there a way to reset the TestFlight state for a Bundle ID? How can I escalate my support ticket if there's no response? I'm completely stuck — I cannot test my app at all. Any help or guidance would be greatly appreciated. Thank you!