ITMS-90158

My app (com.onon.app) consistently fails App Store Connect validation (ITMS-90207: Invalid Bundle) despite passing all local diagnostics (valid arm64 binary, correctly signed, appropriate entitlements). Is there a known issue with Apple's validation server, or are there obscure validation rules I might be missing? Diagnosic info Architecture Check (lipo -info Runner): Non-fat file: Runner is architecture: arm64 Code Signing Verification (codesign -vvv Runner): Runner: valid on disk Runner: satisfies its Designated Requirement Local Environment Details: Operating System: macOS 15.5 24F74 (arm64) Xcode Version: 16.3 (16E140) Transporter Version: 1.3.3-13326 Flutter Version: 3.29.0 CocoaPods Version: 1.16.2 Has anyone encountered a similar issue with a Flutter app that passes local code signing checks but is rejected by App Store Connect? Are there any known edge cases or obscure validation rules that aren't covered by standard code signing diagnostics? I've also opened a Technical Support Incident with

Hi guys, I have an app ready for testing/distribution. But when I used Transporter to send the app to Apple Store Connect, I got the following warning. ITMS-90885: 'Cannot be used with TestFlight because the executable “${executable}” in bundle “${bundle}” is missing a provisioning profile but has an application identifier in its signature. Nested executables are expected to have provisioning profiles with application identifiers matching the identifier in the signature in order to be eligible for TestFlight.' The executable and bundle values were missing from this warning message, which does not help find the warning cause. Could someone give me some advice to resolve this issue? Thanks!

Hello, I added a new iOS 26 app icon created with Icon Composer (named AppIcon) to my app, while keeping the previous version's icon (in Asset Catalog format, also named AppIcon). However, I found that once the bundle contains the Icon Composer icon file, the app cannot be submitted to App Store Connect. I received the following App Store Connect errors: ITMS-90022: 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. ITMS-90023: 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 oper

General: Forums topic: Privacy & Security Forums tag: Privacy Developer > Security — This also covers privacy topics. App privacy details on the App Store UIKit > Protecting the User’s Privacy documentation Bundle Resources > Privacy manifest files documentation TN3181 Debugging an invalid privacy manifest technote TN3182 Adding privacy tracking keys to your privacy manifest technote TN3183 Adding required reason API entries to your privacy manifest technote TN3184 Adding data collection details to your privacy manifest technote TN3179 Understanding local network privacy technote Handling ITMS-91061: Missing privacy manifest forums post Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

We are an Apple Enterprise Developer account holder distributing an in-house iOS application via an itms-services installation workflow. On macOS devices with ARM architecture (Apple Silicon), our app is supported and can be installed as a compatible iOS application. However, when an update is detected, and we attempt to reinstall the app using a .plist manifest file (still via itms-services), the system installs the new version as a separate app—even though the bundle ID is exactly the same—resulting in duplicate app icons appearing on the macOS home screen. We would like to know: Is there a recommended approach to prevent this duplicate icon behavior? Is there a supported way on macOS to programmatically remove or replace the existing version of the iOS app before installing the updated version?

Hi, Recently our App is facing a generic error with no error details. This error is happening once Build has been successfully uploaded to AppStore Connect through Xcode Organiser. Steps followed while uploading the build: Archive the Build through Xcode Once Archive is successful, Distributing the App through Xcode Organiser using AppStore Connect distribution method. Build Uploaded successfully to AppStore Connect After 5 min we are receiving a email with below message Hello, We noticed one or more issues with a recent delivery for the following app: AppName App Apple ID 2121111 Version 3.6.9 Build 75 Please correct the following issues and upload a new binary to App Store Connect. ITMS-90755: Invalid Binary - The following binaries in your app contains prohibited instructions: AppName.app/AppName. Remove the instructions from the binaries, rebuild and resubmit. Apple Developer Relations Solutions tried till now Updating Xcode to latest version of 16.4 Recreating new Distribution certificates and P

ITMS-90328: Your package contains a file AppName.app/Info.plist /Users/admin with a name that contains invalid characters. Avoid using control characters in the file names. ITMS-90328: Your package contains a file AppName.app/Info.plist with a name that contains invalid characters. How do I resolve this issue? My Info.plist file has no control character

Hi all, Im trying tu publish an app for iOS and I get it rejected by the lack of this privacy manifest, but unless I understood this wrong, this manifest is needed for external tools used, or maybe Im wrong, Im publishing an app made in Unity, so in this case, one has to include a privacy manifest by default? Sorry Im lost in all these terms, so I don't know if im asking something redundant, if you know how to fix this issue please tell me or direct me to the process because I haven't been able to identify the issue. Thanks a lot for any clue beforehand really

Does anyone encounter this email from the Apple Store Connect? Please correct the following issues and upload a new binary to App Store Connect. ITMS-90398: Invalid WatchKit support - The bundle contains architectures that aren’t allowed or is missing architectures that are required. Verify in the Xcode build settings that the architectures on which your app is built are correct. I'm trying to upload my app with a WatchKit app and WatchKit extension. I'm using standard architecture in build setting architectures settings for my iOS, WatchKit app and WatchKit Extension. I also added excluded architecture of armv7 for the iOS and none for the watchkits. The minimum build deployment for iOS is 12.0 and 4.0 for watchOS. Im using Xcode Version 16.4 (16F6)

Hello Apple Support Team, We are developing a macOS application that allows users to import and view PST files (Microsoft Outlook archives). These files contain a complex, proprietary format that requires specialized parsing libraries. To achieve this, we are using Aspose Email for Java, which is currently one of the few reliable libraries that support complete PST parsing across platforms. Why we are using Java & Aspose The Aspose Email Java library provides a comprehensive API to extract mail data (including metadata, attachments, and folder structure) from .pst files. A native Swift or Objective-C alternative with full .pst parsing capability does not exist, which is why we opted for a Java-based helper module that runs in the background and communicates with the macOS app over a Unix domain socket. How we bundle it We package the AsposeEmail.jar and a custom JRE (Java Runtime Environment) created using jlink, tailored to run only our jar. This entire setup (JAR + JRE) is bundled within the Contents/Re