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.

Our account containing our 800 apps was closed down as part of anti Jewish sentiment. We have now had our 2nd account closed via cyber (made inaccessible via cyber). Sometimes it's re-opened before Shabbat starts and re-closed after shabbat to iritate. We are actively prevented from appealing our account closure, etc. We warned Apple we were having these issues over a period of around 6 months.

Hi everyone, My TestFlight build has been stuck in 'Waiting for Review' for over 32 hours and I'm hoping someone can help or share their experience. The situation: I have an External Testing group with a Public Link set up. The build was submitted for Beta App Review on March 19th but it's been over 32 hours with no update. I have 25+ testers waiting to install the app. What I've tried: Waited patiently Checked App Store Connect multiple times No rejection emails received No issues flagged by Apple Questions: Is anyone else experiencing unusually long review times for TestFlight external builds right now? Is there anything I can do to speed up the process or check if something is wrong? Has anyone successfully resolved this by contacting Apple Developer Support directly? Any advice would be greatly appreciated. Thank you! Apple Support Case ID: 102846633409

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?

大家好， 想请教一下是否有开发者遇到过类似情况，并愿意分享处理经验。 假设某 App 收到第三方发起的知识产权投诉（例如图片、字体、素材等相关内容）。 开发者收到投诉后已经： 完成内部核查； 删除或替换了被投诉内容； 发布整改版本； 当前 App 及相关线上服务中已无法访问被投诉内容。 但投诉方认为双方争议并未解决，并持续基于历史使用行为提出异议或再次发起投诉。 想了解大家是否遇到过类似情况： 开发者完成整改后，Apple 是否曾针对同一事项再次联系过你们？ Apple 是否要求过额外材料，例如整改说明、授权证明或其他补充文件？ 如果当前版本和线上服务已经无法访问被投诉内容，Apple 在后续处理中通常更关注哪些方面？ 有没有开发者遇到过已经完成整改，但仍然因为同一事项被进一步处理甚至下架的情况？ 对于这类已经完成整改、但双方仍存在历史争议的问题，Apple 后续通常是如何处理的？ 我理解每个案件情况不同，也理解 Apple 会根据个案进行评估。 这里只是希望了解其他开发者的实际处理经验，以便更好地理解 App Store 在知识产权投诉方面的一般处理方式。 感谢大家分享经验。

Hello, I forgot to renew my Paid Apps Agreement when the previous one expired. As a result, all of my In-App Purchases and subscriptions became unavailable. I have now signed the new agreement, and it appears as active in App Store Connect. However, my In-App Purchases are still unavailable and purchases cannot be completed in my apps. Is there a propagation delay after signing the agreement before In-App Purchases become available again? Does Apple need to perform any manual action on their side after the agreement is renewed? If there is a delay, how long did it take in your experience? My products are still marked as "Ready for Sale" and everything else appears to be configured correctly. This issue is currently affecting live apps and preventing customers from making purchases, so I'm trying to understand whether I should simply wait or contact Apple Support. Thanks for any insights.

Hello, I noticed the webhook event BUILD_BETA_DETAIL_EXTERNAL_BUILD_STATE_UPDATED does not fire when a build is submitted for external beta review. It is only fired when the review completes. It would be great if we can get notified when an external beta review has started, similar to how we do get notified when a review gets started for the App Store build. Thank you for your time and consideration.

Hi, I'm the founder of a small independent mobile app company based in Istanbul, Turkey. I'm sharing this because I'm trying to understand whether anyone else has experienced something similar and whether there are any realistic paths forward after a final Apple Developer Program termination. In April 2026, our app received several App Review rejections. We addressed the issues raised by Apple and submitted updated versions of the app as requested. On April 27, 2026, we received a Pending Termination Notice alleging App Review circumvention. We submitted a formal appeal on April 28 and followed up with additional information and documentation on May 15. On June 2, Apple informed us that our appeal was insufficient and that our membership would be terminated. What caught my attention was that the same communication also stated that submitting a reinstatement request could potentially lead to reconsideration. I took that seriously. We immediately shifted our focus toward a complete compliance review of the app, brought in outside assistance, and reviewed everything we could think of: app metadata, screenshots and marketing assets, user flows, source code, business logic, and third-party integrations. The changes were not cosmetic. Entire features were removed, workflows were redesigned, and significant parts of the application's architecture were revised. Our goal was to address every concern we could identify and submit a comprehensive reinstatement request. Then, on June 6, before we were able to complete and submit that request, we received the final termination notice. To be clear, I'm not claiming Apple made the wrong decision, nor am I posting this to generate outrage. What I found difficult to understand was being told that reinstatement could be considered, investing significant time and resources into preparing that submission, and then receiving a final termination before having the opportunity to submit it. For context: We never used external payment systems. We never purchased or manipulated ratings or reviews. We never distributed binaries hidden from App Review. We never intentionally attempted to deceive Apple or bypass review procedures. I'm 24 years old and this is my first company. Looking back, I can see that some of my decisions came down to inexperience. That's exactly why I took the reinstatement process seriously. I wanted to fix what I could. A few questions: Has anyone received reconsideration after a final Apple Developer Program termination? Has anyone experienced receiving a final termination while actively preparing a reinstatement request? Are there any official communication channels available once App Store Connect access has been removed? Thank you for reading. Batuhan Özdemir Founder, Liquid Apps Team ID: 7K3Z69D85W

Hi everyone, Thanks in advance to anyone who shares their experience.

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で再作成済みです 同様の事象や解決方法をご存じの方がいらっしゃいましたら、ご教示いただけますと幸いです。 よろしくお願いいたします。

We are stuck in AppStoreConnect limbo. We have a new subscription group + two Subscriptions in Ready To Review state in appstoreconnect, but Apple Review rejected our latest app version because they weren't included with the version. Our app version has been rejected for a few issues before this which maybe broke something. When I go to edit the version, there is no Subscriptions & Purchases section to add them for review. I tried editing the subscriptions and subscription group localization to see if that got it out of Waiting For Review state or showed the version section but no luck. So we can't add the Subscriptions for review and we are rejected from App Review if we don't. I submitted an Apple support email 8 days ago and haven't received any response. Does anyone know of a way to get this unblocked?

I have an app published on the App Store (https://apps.apple.com/us/app/junto%24/id1563846408) and, if someone accesses this URL from a device other than an iOS device, for example, a Windows computer with Chrome, a Linux machine with Chrome, or even an Android device, the page doesn't work. Access only works on iOS devices. I tried accessing URLs from other apps to check if it was a general problem, but the problem only occurs with my app's URL. Example of a working URL: https://apps.apple.com/br/app/juntos/id6449265641 My URL: https://apps.apple.com/br/app/junto%24/id1563846408 One difference is the "%24", which is the "$" in the code automatically inserted by Apple, and that's not the problem, since I can access the page on iOS devices. When I access my app's page through a search on the App Store, I can access the page, but if I refresh the page (F5), it stops working again. My app is public and all countries available. Why does this happen?

I am writing to follow up regarding the reactivation of our Apple Developer account. We paid the amount requested for the reactivation of the account on the 6 of July and have not yet received any green light to go ahead, please can anyone tell me what to do?

Hello Apple Staff, I’m posting again because this issue has not been resolved yet. We currently have two active apps under the same developer account that are still in Waiting for Review. For one of the affected apps, the details are as follows: App ID: 6760743106 Review submission ID: 6950ecff-f833-404d-b04b-ac34ec552b85 We also tried to submit an expedited review request, but the expedited review form does not complete successfully. The following error message is displayed: “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.” Could Apple Staff please check the current status of these review submissions and let us know if any additional action is required from our side? We would greatly appreciate your assistance, as the review process has not started and we are currently unable to submit an expedited review request. Thank you for your time and support.

Hello, I'm a first time developer and both of my submissions for NexFi - Portfolio Tracker have been suck in Waiting for Review for an extended time. TestFlight: My first build was submitted on Feb 15th (25+ days) and still Waiting for Review Production/Distribution: Submitted March 2nd (10 days) and still Waiting for Review. It is a finance category app (portfolio tracker) that requires no login, no account creation, and no server side user data so I figured it should be a relatively quick process as there is a minimal privacy footprint. App Name: NexFi - Portfolio Tracker Platform: iOS App ID: 6759226354

Can not update app privacy information about tracking user after remove the tracking functionality and "NSUserTrackingUsageDescription" from info.plist. Always reminds us App contains "NSUserTrackingUsageDescription"

Hello, I am experiencing the exact same ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING issue. I cannot submit builds for External TestFlight review. When I click "Submit for Review" in TestFlight, App Store Connect returns: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING "Beta contract is missing for the app." All agreements, banking information, and tax forms are Active. Completed and verified: • Paid Apps Agreement = Active • Free Apps Agreement = Active • Bank Account = Active • W-8BEN Tax Forms = Active • Compliance information completed • Account Holder role assigned correctly I have already: • Added and activated a bank account • Completed all tax forms • Uploaded new builds after activation • Waited several days for synchronization • Opened a case with Apple Developer Support Developer Support has already escalated my case to the senior team, but the issue remains unresolved. The browser console confirms: 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING This issue is currently blocking External TestFlight testing. Has anyone experienced this recently? Could someone from Apple verify whether the TestFlight Beta Contract associated with the account needs to be reset, recreated, or manually refreshed? Thank you.

Hi everyone, I'm looking for some advice regarding my app review. My app was previously removed from sale by Apple because it had not been updated for a long time. I have now completely updated it, fixed compatibility issues, and submitted a new version. The submission has been in "Waiting for Review" since June 9, and nothing has changed since then. There are no messages in the Resolution Center and no requests for additional information. I understand that apps returning to the App Store may require a full review, but waiting for more than a week without any progress seems unusual. Has anyone experienced a similar situation? Is there anything I can do to have the review started, or should I simply continue waiting? Any advice or feedback would be greatly appreciated. Thank you.

Hi everyone, I’m trying to get two auto-renewable subscriptions reviewed for my iOS app. Both subscriptions are in the same subscription group. The app binary already includes the subscription screen and the products are visible in the app. The subscription screen shows the subscription title, duration, price, Privacy Policy link, and Terms of Use (EULA) link. However, App Review returned the subscription products with this message: “Guideline 2.1(b) - Performance - App Completeness We have returned the In-App Purchase products as the required binary was not submitted. Once you have resolved all the outstanding issues that were identified and are ready to submit the binary, resubmit the In-App Purchase products with the binary.” What confuses me is that the app binary was already submitted, and all current app versions include these two subscriptions. I also cannot find a separate place on the app version page to attach these subscriptions again. After updating the subscription metadata, I resubmitted the two subscriptions directly from App Store Connect. They are now in “Waiting for Review” status. My questions are: Is it valid to resubmit returned auto-renewable subscriptions directly from the subscription page after the app binary has already been approved or submitted? If App Review says “required binary was not submitted,” where exactly should I attach auto-renewable subscriptions to an app version in the current App Store Connect UI? If the subscriptions are already included in the app binary and are now Waiting for Review, is there anything else I need to do? Thanks.

Submitted Thursday, June 12 at 5:53pm ET. It is now Monday, June 15 at 5pm ET. Status has not moved from "Waiting for Review." No reviewer has opened the app. I'm a small indie developer — this is my second app (GoShed is live). I've been through the rejection cycle before so I know the process. The submission is clean: guest-browse architecture, Stripe for payments, PostHog analytics, reviewer credentials included, notes written specifically to preempt common flags. Apple's own page currently reads "90% of submissions reviewed in less than 24 hours." I'm at 96. I submitted a support email Sunday night and am within the 2-business-day response window. Not panicking. Just flagging for anyone else in the queue — and genuinely curious if others are seeing delays this week specifically.

On the iOS App Version page in App Store Connect, clicking Save shows an exclamation-mark error icon on the button, but no error message or field-level validation appears anywhere on the page. The Add for Review button stays greyed out, so I can't submit. This happens on every new version. What I've verified: •⁠ ⁠Build is attached and shows "Validated" in TestFlight, no warnings or compliance issues •⁠ ⁠All required metadata populated: Description, What's New, Keywords, Support URL, Marketing URL, Copyright, Version, Sign-In Information (working credentials), Contact Info •⁠ ⁠Export compliance answered •⁠ ⁠Release set to "Manually release this version" •⁠ ⁠Screenshots present for iPhone 6.5" (same assets that worked on a prior version) •⁠ ⁠Media Manager shows no warnings on any size •⁠ ⁠Account has the Account Holder role •⁠ ⁠Reproduced in Chrome (latest) and in Incognito Observation: on clicking Save, the screenshots section briefly refreshes/reloads, then the error icon appears on Save. No other error is surfaced anywhere. Current workaround: my engineer uploads the build directly from Xcode to App Store Connect, which lets the version through - but the web Save/submit path is broken on every release. Question: what validation is failing here without being surfaced in the UI, and how do I get the web Save/submit flow working so I don't have to fall back to a manual Xcode upload each release?