Search results for

“ITMS-90338”

1,704 results found

Post

Replies

Boosts

Views

Activity

Pkg installation package uploaded to macstore email prompt ITMS-90296
Project Background: I developed a Mac project using Electron and VSCode Successfully uploaded the packaged pkg using Transporter, However, I will receive an email informing me that there are some issues with the project: ITMS-90296: App sandbox not enabled - The following executors must include the 'com. apple. security. app sandbox' entitlement with a Boolean value of true in the entitlement property list: [[com. electron. iflyrecclient. pkg/Payload/iFlytek Listen. app/Contents/MacOS/iFlytek Listen]] ITMS-90886: 'Cannot be used with TestFlight because the signature for the bundle at' iFlytek hears. app 'is missing an application identifier but has an application identifier in the provisioning profile for the bundle.' Bundles with application identifiers in the provisioning profile are expected to have the same identifier signed into the bundle in order to be eligible for TestFlight.' Here is my packaging process: Generate an app using the electron packager tool Sign the app using @ electron
Topic: Code Signing SubTopic: General Tags:
2
0
693
Nov ’24
App Store Connect Error ITMS-90058: This bundle is invalid
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.
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
4
0
215
Sep ’25
Reply to App Store Connect Error ITMS-90058: This bundle is invalid
It’s part of our own framework, not a third-party dependency. For some reason, the DTPlatformName key is missing from the framework’s Info.plist, which caused the ITMS-90058 error during validation. We resolved this by adding DTPlatformName = iphoneos to the framework’s Info.plist, and the build is now passing App Store checks. Right, you won't find this key in the source Info.plist file for any target in Xcode, because it's expected to be generated as part of the build. The value can vary, as a framework can be built for different platforms, so hardcoding this value into your Info.plist isn't the right long-term solution. To figure out the right solution, are you able to share a stripped down version of your framework project with us, either through a link here to somewhere else on the Internet, or if you need to keep it private, you can open a code-level support request to get me a private copy? The stripped down version here is that I only need to see something that builds, so you could delete mos
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Sep ’25
ITMS-90207: Invalid Bundle. The bundle at 'Runner.app' does not contain a bundle executable.
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
2
0
223
Aug ’25
App rejected by App Store Connect with ITMS-90714: Invalid binary
Hi, I am on Mac OS Sequoia 15.5, XCode 16.4 (16F6) Uploading via XCode or Transporter is successful, then binary gets refused by App Store Connect. I have tried: Removing all Other Linker Flags except -ld64 as the app cannot be generated without ld64. My original Other Linker Flags: -all_load -w -Xlinker -no_objc_category_merging -ld64 2. Running xcrun dyld_info -objc Payload/YourApp.app/YourApp | grep (null) return nothing. Please, advise what else can I do.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
3
0
174
Aug ’25
Xcode cloud and multiple bundle ids?
Is it possible to set up Xcode Cloud so it distributes the app to different bundle id? (for example, mock, test and release environment) Right at the moment we are only limited to deploy TestFlight for the bundle ID that configured Xcode Cloud? I would really like to be able automate several different build with different bundle id's... When i try to archive using Xcode Cloud to a different bundle id that the one configuring Xcode Cloud i get the following errors: ITMS-90054: This bundle is is invalid. ITMS-90345: Metadata.Info.plist Mismatch. When I archive manually it works perfectly fine.
Topic: Developer Tools & Services SubTopic: Xcode Cloud Tags:
6
0
3.7k
Apr ’23
Background Assets - Manifest Error
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
Topic: Developer Tools & Services SubTopic: Apple Developer Program Tags:
1
0
288
Aug ’25
Privicay manifest help
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
1
0
125
Aug ’25
Reply to How to add privacy manifest to iOS Xcode project
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
Aug ’25
Pkg installation package uploaded to macstore email prompt ITMS-90296
Project Background: I developed a Mac project using Electron and VSCode Successfully uploaded the packaged pkg using Transporter, However, I will receive an email informing me that there are some issues with the project: ITMS-90296: App sandbox not enabled - The following executors must include the 'com. apple. security. app sandbox' entitlement with a Boolean value of true in the entitlement property list: [[com. electron. iflyrecclient. pkg/Payload/iFlytek Listen. app/Contents/MacOS/iFlytek Listen]] ITMS-90886: 'Cannot be used with TestFlight because the signature for the bundle at' iFlytek hears. app 'is missing an application identifier but has an application identifier in the provisioning profile for the bundle.' Bundles with application identifiers in the provisioning profile are expected to have the same identifier signed into the bundle in order to be eligible for TestFlight.' Here is my packaging process: Generate an app using the electron packager tool Sign the app using @ electron
Topic: Code Signing SubTopic: General Tags:
Replies
2
Boosts
0
Views
693
Activity
Nov ’24
App Store Connect Error ITMS-90058: This bundle is invalid
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.
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Replies
4
Boosts
0
Views
215
Activity
Sep ’25
Reply to App Store Connect Error ITMS-90058: This bundle is invalid
It’s part of our own framework, not a third-party dependency. For some reason, the DTPlatformName key is missing from the framework’s Info.plist, which caused the ITMS-90058 error during validation. We resolved this by adding DTPlatformName = iphoneos to the framework’s Info.plist, and the build is now passing App Store checks. Right, you won't find this key in the source Info.plist file for any target in Xcode, because it's expected to be generated as part of the build. The value can vary, as a framework can be built for different platforms, so hardcoding this value into your Info.plist isn't the right long-term solution. To figure out the right solution, are you able to share a stripped down version of your framework project with us, either through a link here to somewhere else on the Internet, or if you need to keep it private, you can open a code-level support request to get me a private copy? The stripped down version here is that I only need to see something that builds, so you could delete mos
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Replies
Boosts
Views
Activity
Sep ’25
Reply to Icon composer icon contains alpha channel upload error
I have just tried with Xcode 26 RC and still get the same error ITMS-90717: Invalid large app icon. I have tested with only SVG files, with only PNG, where one was w/o alpha, and with combination SVG and PNG. Nothing worked. I sent feedback with attached AppIcon.icon file.
Topic: Developer Tools & Services SubTopic: Instruments Tags:
Replies
Boosts
Views
Activity
Sep ’25
Reply to [REQUEST] for a tool/method/guidance how to create privacy manifest (PrivacyInfo.xcprivacy) when you don't have Xcode/mac
For guidance, see the following resources: App Privacy Configuration Adding a privacy manifest to your app or third-party SDK Be sure to read Handling ITMS-91061: Missing privacy manifest.
Topic: Developer Tools & Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
Sep ’25
ITMS-90207: Invalid Bundle. The bundle at 'Runner.app' does not contain a bundle executable.
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
Replies
2
Boosts
0
Views
223
Activity
Aug ’25
Reply to Icon composer icon contains alpha channel upload error
Getting the same issue 'ITMS-90717: Invalid large app icon' when building my app on Xcode Cloud using the latest beta versions. The versions listed in the workflow are as follows: Xcode Version: Xcode 26 beta 6 (17A5305f) macOS Version: macOS Tahoe 26 beta 7 (25A5346a) Hoping for some updates to this issue soon!
Topic: Developer Tools & Services SubTopic: Instruments Tags:
Replies
Boosts
Views
Activity
Aug ’25
App rejected by App Store Connect with ITMS-90714: Invalid binary
Hi, I am on Mac OS Sequoia 15.5, XCode 16.4 (16F6) Uploading via XCode or Transporter is successful, then binary gets refused by App Store Connect. I have tried: Removing all Other Linker Flags except -ld64 as the app cannot be generated without ld64. My original Other Linker Flags: -all_load -w -Xlinker -no_objc_category_merging -ld64 2. Running xcrun dyld_info -objc Payload/YourApp.app/YourApp | grep (null) return nothing. Please, advise what else can I do.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
Replies
3
Boosts
0
Views
174
Activity
Aug ’25
Xcode cloud and multiple bundle ids?
Is it possible to set up Xcode Cloud so it distributes the app to different bundle id? (for example, mock, test and release environment) Right at the moment we are only limited to deploy TestFlight for the bundle ID that configured Xcode Cloud? I would really like to be able automate several different build with different bundle id's... When i try to archive using Xcode Cloud to a different bundle id that the one configuring Xcode Cloud i get the following errors: ITMS-90054: This bundle is is invalid. ITMS-90345: Metadata.Info.plist Mismatch. When I archive manually it works perfectly fine.
Topic: Developer Tools & Services SubTopic: Xcode Cloud Tags:
Replies
6
Boosts
0
Views
3.7k
Activity
Apr ’23
Background Assets - Manifest Error
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
Topic: Developer Tools & Services SubTopic: Apple Developer Program Tags:
Replies
1
Boosts
0
Views
288
Activity
Aug ’25
Reply to Icon composer icon contains alpha channel upload error
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:
Replies
Boosts
Views
Activity
Aug ’25
Reply to How to add privacy manifest to iOS Xcode project
For more information, see Handling ITMS-91061: Missing privacy manifest.
Topic: App Store Distribution & Marketing SubTopic: General
Replies
Boosts
Views
Activity
Aug ’25
Privicay manifest help
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
Replies
1
Boosts
0
Views
125
Activity
Aug ’25
Reply to Privicay manifest help
For more information, see Handling ITMS-91061: Missing privacy manifest.
Topic: App Store Distribution & Marketing SubTopic: General
Replies
Boosts
Views
Activity
Aug ’25
Reply to How to add privacy manifest to iOS Xcode project
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
Replies
Boosts
Views
Activity
Aug ’25