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

Hello, about a month ago, the Apple Store account of my former company was closed. I was already registered as a developer, so there's no problem with that. Was my personal account also closed when this company account was shut down? I contacted Apple support about this, and they said they would investigate. I still haven't received a response. Was my account closed? Or is there another issue? Nobody is explaining why this happened.

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

I’m having an issue where my TestFlight build is visible to a tester, but installation fails immediately. App details: Platform: iOS Version/builds affected: 0.3.0 (5) and 0.3.0 (6) Device tested: iPhone 14 running iOS 26.5 App status in App Store Connect: Prepare for Submission The app has not been publicly released. What happens: The tester can see the app in the TestFlight app under “Currently Testing”. The Install button is visible. However, tapping Install shows this error: “Could not install "App" Workspace. The requested app is not available or doesn’t exist.” The issue occurred with build 0.3.0 (5), then again after uploading a fresh build 0.3.0 (6). What I have already checked/tried: Build uploads completed successfully in App Store Connect. Build 0.3.0 (5) processed successfully. Build 0.3.0 (6) was uploaded as a fresh build. Build 0.3.0 (6) includes ITSAppUsesNonExemptEncryption = false in Info.plist. The build is assigned to the internal testing group. The tester invite shows as accepted. I tried using a separate Apple ID/email address that I control. The tester account can see the app in TestFlight. I deleted and reinstalled TestFlight on the device. I confirmed the device/TestFlight account is signed in with the tester Apple ID. Pricing has been set to Free. App Availability has been configured for the relevant region. The app is showing “Prepare for Submission”, not “Removed from Sale”. The build appears in TestFlight, but install still fails. Has anyone seen this state before, where TestFlight can display the app and build to an accepted tester, but install fails with “The requested app is not available or doesn’t exist”? Is there any App Store Connect availability, storefront, app version, or backend distribution state that can cause this? Any guidance on what to check next would be appreciated.

Hello App Review Team, My team's first app submission has been in "Waiting for Review" status for 17 days with no movement, and I would appreciate any visibility you can provide on its current state. Submission details: App name: Motor İzleme Submission ID: fb2151a2-969e-458b-b57b-9fc7a982e168 Submitted: May 20, 2026 at 10:24 PM Version: 1.0 (build 2) Current status: Waiting for Review (17 days) Account type: Organization (first submission under this account) About the app: Motor İzleme is a hardware companion app that communicates with our physical device over Bluetooth Low Energy. Because reviewers cannot physically test the device without the hardware, we have provided the following materials with the submission to support the review: A demonstration video showing the full app-to-hardware interaction (linked in App Review Notes) Detailed App Review Notes explaining the BLE communication flow App screenshots covering all primary screens Clear handling of the no-device state (the app does not crash or hang — it shows appropriate prompts when Bluetooth is off or no device is found) I want to be transparent: I am not requesting expedited review and I understand the team is operating under heavy submission volume in 2026. I am simply asking whether this submission may have been overlooked, or whether there is anything additional I can provide to help the review proceed. This launch is tied to a commitment with our business partner, and the extended delay is beginning to impact business obligations on our end. Any update would be greatly appreciated. Thank you for your time. Best regards, Saadettin Yıldırım

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!

Every time I create an update for my application, the "App Clip" section on the "App Information" page on App Store Connect "forgets" the app clip information entered for the previous version. There used to be an "Apply previous" button in this section but it appears to have disappeared? Is there a way I can determine if this is a bug or if something in my configuration changed? I'm not even sure what I would provide if I filed this as a bug report.

Hello, I am posting here because I no longer have access to the communication channels that were previously available to discuss my developer account with Apple. My appeal was denied, but Apple informed me that I could submit a reinstatement request after addressing the concerns that had been identified. Following that communication, I spent considerable time reviewing my applications, metadata, screenshots, codebase, user flows, and business practices. Although I do not believe my account was involved in dishonest or fraudulent activity, I nevertheless made extensive changes in an effort to address any potential concerns Apple may have had. The main difficulty is that the specific conduct that led to the termination decision was never clearly explained to me. Apple cited Section 3.2(f) and provided examples of prohibited behavior, but did not identify which specific action or activity was associated with my account. As a result, I was left attempting to correct every possible issue without understanding what the actual concern was. In addition, throughout my participation in the Apple Developer Program, I had never previously encountered a notice, suspension, or similar action of this nature. This made it even more difficult for me to understand what specific issue Apple believed had occurred and how best to address it. While I was still implementing changes and preparing what I believed would be a reinstatement submission, I received a termination notice. Since the termination, I have lost access to the Contact Us page and the communication channels that were previously available to me. I would therefore appreciate guidance from Apple or from developers who may have experienced a similar situation: How is a developer expected to submit a reinstatement request after termination if the Contact Us page is no longer accessible? Is there an alternative channel through which reinstatement requests can be submitted? Has anyone successfully submitted a reinstatement request after account termination and received a review? I am not asking Apple to reverse its decision through this forum. I am simply trying to understand how a developer is expected to submit a reinstatement request after termination when the previously available communication channels are no longer accessible. Thank you for your time.

I'm hoping someone here has experienced the same issue and can point me in the right direction. My Apple Developer Program membership recently expired and my apps have been removed from the App Store. I've been trying to renew my membership but I'm completely stuck and cannot find a way forward. Here's what I've tried so far: Apple Developer App: There is no "Renew" button visible anywhere in the app. developer.apple.com/enroll: I receive the following error: "Sorry, you can't enroll at this time. Your Apple Account is already associated with the Account Holder of a membership." developer.apple.com/account: The Membership Details section loads but there is no renewal option or button available. I am logged in with the correct Account Holder Apple ID, so that is not the issue. My payment method on file is also valid. Has anyone else run into this? Is there a direct link or a workaround that triggers the renewal flow? Or is contacting Apple Developer Support the only option at this point? Any help would be greatly appreciated. Thanks in advance!

Hi, I’m building an iOS app that uses FamilyControls to let users block distracting apps during study sessions. Everything works fine in Debug on a real device: the authorization request succeeds and app blocking works correctly. The problem is when I try to create an Archive for App Store Connect. Xcode gives me this error: “Provisioning profile ‘iOS Team Store Provisioning Profile: com.(ID)’ doesn’t include the com.apple.developer.family-controls entitlement.” I also get a warning saying that my bundle identifier is using the development-only version of the Family Controls capability and that I should request access to the distribution version. I’ve already added the Family Controls capability, enabled the required entitlements, and I’m using automatic signing. I also tried enabling the capability for my App ID in the Apple Developer portal, but it either doesn’t save or the distribution profile still doesn’t include the entitlement. Does the Family Controls distribution entitlement require approval from Apple before it can be used in an App Store build? If so, where do I request it? Has anyone successfully published an app using FamilyControls and run into this issue? Thanks.

I submitted an updated version of my app for review on May 18, 2026, and its status has remained "Waiting for Review" ever since. It has now been more than two weeks without any progress or communication from Apple. To resolve the issue, I have: Submitted multiple support tickets through Apple Developer Support. Received the standard message that I would receive a response within 48 hours. Waited more than 15 days, but have not received any reply to any of my tickets. Attempted to contact Developer Support by phone during U.S. business hours, but after waiting on hold for more than two hours, I was unable to reach anyone. This delay is affecting my ability to release important updates to my users, and I am running out of options. Has anyone experienced a similar situation recently? Is there any other channel or escalation process that I can use to get assistance or have my submission reviewed? Any guidance would be greatly appreciated. Thank you.

Hello 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 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

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,Does anybody know how I can change my team name? The one that shows up on the app store?Thanks,Julian

Hi everyone, I’m currently developing an iOS app using React Native and implementing consumable In-App Purchases (IAP). I'm facing an issue where getProducts returns an empty array without any error messages when testing on a TestFlight build. I have already completed the following setup: Agreements, Tax, and Banking: All forms are signed and the status is "Active" in App Store Connect. Product Configuration: The Consumable product is created in App Store Connect with the status "Ready to Submit". App Store Connect Integration: The product is correctly linked under the "In-App Purchases and Subscriptions" section of the App version. Xcode Capability: The "In-App Purchase" capability has been added to the project. Implementation: The Product ID in my React Native code (using react-native-iap) matches the ID in App Store Connect exactly. Despite these steps, the product list remains empty. Are there any hidden requirements or specific configurations for TestFlight that I might have missed? Any guidance would be greatly appreciated. Thanks!

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?

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.