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，新增In-app Purchase，6小时后正在审核,一周过去了，还是In Review,没有收到结果，发邮件询问，让继续等待，正常都是48小时有结果的,,不知道遇到什么问题， 如何去解决这个问题呢？ 挺焦虑的....... On the already listed App, I added "In-App Purchase". It was under Review 6 hours later. A week has passed and it's still "In Review". I haven't received the result yet. I sent an email to inquire and asked to keep waiting. Normally, there is a result within 48 hours. I don't know what problem I encountered and how to solve it. Quite anxious....... Quite anxious.......

I've been able to submit my app without issue so far until today, but it looks like app icon requirements either changed or being enforced differently? Validation failed Missing required icon file. The bundle does not contain an app icon for iPhone / iPod Touch of exactly '120x120' pixels, in .png format for iOS versions >= 10.0. To support older versions of iOS, the icon may be required in the bundle outside of an asset catalog. Make sure the Info.plist file includes appropriate entries referencing the file. See https://developer.apple.com/documentation/bundleresources/information_property_list/user_interface. (ID: 954a36b1-b212-4d7f-8a12-db2d6abe83e2) Validation failed Missing required icon file. The bundle does not contain an app icon for iPad of exactly '152x152' pixels, in .png format for iOS versions >= 10.0. To support older operating systems, the icon may be required in the bundle outside of an asset catalog. Make sure the Info.plist file includes appropriate entries referencing the file. See https://developer.apple.com/documentation/bundleresources/information_property_list/user_interface. (ID: 7ded4fb3-a0f0-4542-9373-a3dcf9ace3ef) Validation failed Missing app icon. Include a large app icon as a 1024 by 1024 pixel PNG for the 'Any Appearance' image well in the asset catalog of apps built for iOS or iPadOS. Without this icon, apps can't be submitted for review. For details, visit: https://developer.apple.com/documentation/xcode/configuring-your-app-icon. (ID: 43a6785a-3917-4ac9-90b1-dc85d5b2fdd8) Contents.json I already have a 1024x1024 PNG for 'Any Apperance' so not sure what that one is about. The others I cannot find slots for, to provide a generic icon even though they wont be used since my app is only for iOS18+ I attempted adding a new icon set "App Icon" with the 120x120 PNG but that did not seem to work so I removed it. Any suggestions? *note I am also using the .Icon file created by Icon Composer (v3)

Hello, I am encountering the following error when uploading a build to App Store Connect: ITMS-90555: Thinned app size is too large – Your on-demand resources in the universal variant are 30 GB, which exceeds the maximum allowable size. After app thinning, the total size of your on-demand resource asset packs in any variant must be less than 30 GB. Our application includes a large amount of font resources delivered via ODR. Before making structural changes, I need clarification because the documentation does not fully explain how ODR size calculations work per variant. Environment Xcode: (latest stable) Distribution method: App Store submission ODR total size before thinning: approximately (28 GB) Build processing fails immediately with the ITMS-90555 error Questions How exactly does App Thinning compute the size of ODR asset packs per variant? Is ODR size evaluated: Per device-specific variant, Or is the “universal variant” treated as an additional variant that must independently stay under 30GB? The documentation mentions a 30GB limit per variant, but the universal variant error message is ambiguous. If device-specific variants are below 30GB but only the “universal variant” exceeds it, is the build still rejected? In our case: iPhone-only variants appear to be below the limit, But the universal variant exceeds 30GB due to aggregated resources. Is this expected behavior? Best practices for managing very large ODR sets (e.g., fonts) Fonts are small individually, but thousands of them produce very large ODR groups. Is there recommended guidance from Apple for: Structuring ODR bundles to avoid the universal variant exceeding the limit Segmenting ODR by device class / feature sets Any alternative packaging strategies Are there tools or logs that reveal how App Store Connect decides variant groupings and ODR size? At the moment, the failure only shows the ITMS-90555 error without further detail. Case-ID for DTS reference DTS advised submitting this question here. Case-ID: 17273913 Any clarification from Apple engineers or community members who have navigated ODR size limits would be greatly appreciated. Thank you very much!

I'm running into a contradictory requirement involving the DeviceActivity Report extension (com.apple.deviceactivityui.report-extension) that makes it impossible to both: upload the app to App Store Connect, and install the app on a physical device. This creates a complete catch-22. 📌 Overview My extension: Path: Runner.app/PlugIns/LoADeviceActivityReport.appex Extension point: com.apple.deviceactivityui.report-extension Implementation (SwiftUI): import SwiftUI import DeviceActivity @main struct LoADeviceActivityReport: DeviceActivityReportExtension { var body: some DeviceActivityReportScene { // ... } } This is the standard SwiftUI @main DeviceActivityReportExtension template. 🟥 Side A — iOS runtime behavior (device installer) If I add either of these keys to the extension's Info.plist: NSExtensionPrincipalClass NSExtensionMainStoryboard then the app cannot be installed on a real iPhone/iPad. The device installer fails with: Error 3002 AppexBundleContainsClassOrStoryboard NSExtensionPrincipalClass and NSExtensionMainStoryboard are not allowed for extension point com.apple.deviceactivityui.report-extension. To make the app install and run, I must remove both keys completely. This leaves the extension Info.plist like: NSExtension NSExtensionPointIdentifier com.apple.deviceactivityui.report-extension With this, the app installs and runs correctly. 🟥 Side B — App Store Connect upload validator However, when I upload the IPA with the runtime-correct Info.plist, App Store Connect rejects it: State: STATE_ERROR.VALIDATION_ERROR (HTTP 409) Missing Info.plist values. No values for NSExtensionMainStoryboard or NSExtensionPrincipalClass found in extension Info.plist for Runner.app/PlugIns/LoADeviceActivityReport.appex. So ASC requires that at least one of those keys be present. 💥 The catch-22 If I add PrincipalClass / MainStoryboard: ✔ App Store Connect validation passes ❌ But the app can NOT be installed on any device (Error 3002) If I remove PrincipalClass / MainStoryboard: ✔ The app installs and runs correctly ❌ ASC rejects the upload with “Missing Info.plist values” There is currently NO Info.plist configuration that satisfies both: Runtime: "NSExtensionPrincipalClass and NSExtensionMainStoryboard are not allowed." App Store Connect: "You must include NSExtensionPrincipalClass or NSExtensionMainStoryboard." 📌 Expected behavior For SwiftUI @main DeviceActivityReportExtension, the documentation and examples suggest the correct configuration is: NSExtensionPointIdentifier com.apple.deviceactivityui.report-extension with no principal class or storyboard at all. If that is correct for runtime, ASC seems to need updated validation rules for this extension type. ❓My Questions What is the officially correct Info.plist configuration for a SwiftUI DeviceActivityReportExtension? Should principal class / storyboard not be required for this extension type? Is this a known issue with App Store Connect validation? Is there currently a workaround that allows: installation on device and successful App Store Connect upload, without violating runtime restrictions?

I am trying to submit my app for review but when I click on the 'add to review' button, I am getting the message: Unable to Add for Review The items below are required to start the review process: There are still screenshot uploads in progress. However, there is nothing I am uploading... I tried removing all screenshots, nothing works. It has been 4 days, I cant update my app on the app store... impossible to get any response from Apple... Any inputs will be greatly appreciated.

Can multiple apps be published under the same organization that use the same logo and the same app name, but are intended for different regions? Each app will target a specific country or region, and the core functionality will be similar. I could not find any specific App Store Review Guideline stating whether it is allowed to have the same app name and branding for different regional versions. Is it necessary to differentiate the branding or name for each regional version to get approval during App Review?

Hi. We have an app that includes an app clip. We have been submitting several versions for review without any problems, but a change at App Store Connect backend just caused a blocking issue to us. Every app clip is required to have a default app clip header image. It must be uploaded and saved before we submit a new app version for review. Yet we are currently unable to upload a default app clip header image. When we select the image to upload, nothing happens in the web UI. If we inspect it by Safari's web inspector, we can see that an upload-related backend API endpoint returns HTTP409-Conflict response. We have an ongoing support request with ID 102748924651. Because the request is progressing extremely slowly we have to try alternatives to just submit for review. Is there any other means for submitting an app for review other than App Store Connect? Or what else would you recommend us to do? Thanks

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://api.appstoreconnect.apple.com/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.