I'm successfully creating the AAR file on my system: Manifest file: { assetPackID: my-ba, downloadPolicy: { essential: { installationEventTypes: [ firstInstallation, subsequentUpdate ] } }, fileSelectors: [ { file: file1.bin }, { file: file2.bin } ], platforms: [ iOS ] } Command: xcrun /Applications/Xcode-beta.app/Contents/Developer/usr/bin/ba-package my-ba.json -o my-ba.aar I'm using Transporter on my Sequoia 15.6 system - when I'm uploading the AAR file, I'm getting the following error: ITMS-91140: Invalid manifest file. Invalid manifest file. Your asset pack’s manifest file can’t be verified. Make sure it follows the manifest template, then upload again. Full Debug Log: full-transporter-output.txt
Search results for
ITMS-90158
1,681 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I am still unable to upload to Testflight with an icon composer file as the main app icon on Beta 5. I continue to get: ITMS-90717: Invalid large app icon
Topic:
Developer Tools & Services
SubTopic:
Instruments
Tags:
For more information, see Handling ITMS-91061: Missing privacy manifest.
Topic:
App Store Distribution & Marketing
SubTopic:
General
For more information, see Handling ITMS-91061: Missing privacy manifest.
Topic:
App Store Distribution & Marketing
SubTopic:
General
How can I fix Hello, We noticed one or more issues with a recent submission for App Store review for the following app: • Level 1 to 10 Sudoku Puzzles • App Apple ID 6748925776 • Version 0.0.1 • Build 2 Please correct the following issues and upload a new binary to App Store Connect. ITMS-91061: Missing privacy manifest - Your app includes “Frameworks/_hashlib.framework/_hashlib”, which includes BoringSSL / openssl_grpc, an SDK that was identified in the documentation as a commonly used third-party SDK. If a new app includes a commonly used third-party SDK, or an app update adds a new commonly used third-party 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. ITMS-91061: Missing privacy ma
Topic:
App Store Distribution & Marketing
SubTopic:
General
how to fix Hello, We noticed one or more issues with a recent submission for App Store review for the following app: • Level 1 to 10 Sudoku Puzzles • App Apple ID 6748925776 • Version 0.0.1 • Build 2 Please correct the following issues and upload a new binary to App Store Connect. ITMS-91061: Missing privacy manifest - Your app includes “Frameworks/_hashlib.framework/_hashlib”, which includes BoringSSL / openssl_grpc, an SDK that was identified in the documentation as a commonly used third-party SDK. If a new app includes a commonly used third-party SDK, or an app update adds a new commonly used third-party 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. ITMS-91061: Missing privacy manif
Topic:
App Store Distribution & Marketing
SubTopic:
General
App Store Connect rejects the build with the following error: Please correct the following issues and upload a new binary to App Store Connect. ITMS-90058: This bundle is invalid - The value for key CFBundleVersion [iphoneos] in the Info.plist file must be a period-separated list of at most three non-negative integers. Please find more information about CFBundleVersion at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion But we double-checked at the app level; in all places the CFBundleVersion and versions is mentioned in the correct format. Even though we tried to upload via Xcode and Transporter, both show success. but the build is not reflecting in TestFlight. Receive the above error message via mail. data: { attributes: { cfBundleShortVersionString: 3.25.9, cfBundleVersion: 25, p Validated with the delivery log, but the delivery log also shows correct versioning only.
@AkhileshNak, your bug report is on its way back to you soon with this information, but I'm sharing what we found here for the community's benefit in the future. An app receiving this ITMS error can have Objective-C entries with empty names in the Objective-C metadata. To identify the binaries with those conditions, you can run the following Terminal command on each binary inside the app: % xcrun dyld_info -objc Payload/YourApp.app/YourApp | grep (null) Once you have that output, you can begin to work backwards based on the various class and method names to identify where in your project these are defined. If these are coming from a third-party library you're integrating in your app, you'll then need to talk to the vendor. — Ed Ford, DTS Engineer
Topic:
Community
SubTopic:
Apple Developers
Sharing the full email I sent to Apple Support I am consistently encountering the ITMS-90207 error Invalid Bundle. The bundle at 'Runner.app' does not contain a bundle executable. when attempting to upload my Flutter iOS app to App Store Connect via both Transporter and direct upload from Xcode Organizer. This issue persists despite extensive troubleshooting and thorough local validation, which shows the IPA is correctly formed. App Details: App Name: OnOn App Store Connect App ID: 6502598657 Bundle Identifier: com.onon.app Latest Version/Build Attempted: Version 1.0.24, Build 50 Error Details: Exact Error Message: Invalid Bundle. The bundle at 'Runner.app' does not contain a bundle executable. (ID: [e.g., f548c384-73e9-4f09-96a0-363b7d67f650 from your log]) Transporter Log Reference: From my Transporter logs, the specific iris-code is STATE_ERROR.VALIDATION_ERROR. Example Build ID from Transporter Log: [e.g., 6bd99937-1283-486e-a245-419ea29443f0] (This ID might vary with each attempt, but providing
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
I am using multi-targeted react native app i have deployed most of then but i didi''t get any error but one of my app greeted validated successfully and uploaded successfully but i got error message from play store that's is given below , ITMS-90338: Non-public API usage - The app references non-public selectors in ETCiso: _isKeyDown, _modifiedInput, _modifierFlags. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at every setting are same as other, If there any error and issue in binaory then why its geeting approved in validation and geeted upload
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
I am working on a multi-targeted React Native app. I have deployed most of them without any issues. I didn't receive any errors during the process. One of the apps was even validated and uploaded successfully. However, I later received an error message from the Play Store, which is shown below. ITMS-90338: Non-public API usage - The app references non-public selectors in ETCiso: _isKeyDown, _modifiedInput, _modifierFlags. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at All the settings are the same as the other apps. If there is an error or issue in the binary, then why is it passing validation and uploading successfully? Any one help me to solve this
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
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
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