ITMS-90158

Trying to upload an iOS26 app archive with Xcode 26 beta 7 and getting ITMS-90717: Invalid large app icon, meaning my app is not eligible for TestFlight testing. My App contains an IconComposer .icon asset, so I'm not sure what it's complaining about. I'm not seeing anything in the release notes about this, and I'm not sure if I'm doing something wrong or not.

I'm trying to distribute an app for internal testing but I'm always getting the below error and the SwiftSupport folder is not created although I tried different fixes/configurations. How can I debug/see the reason why the SwiftSupport folder is not generated? Xcode 16.4 Build version 16F6 I tried distributing from the Transporter, Xcode organizer, I tried to archive it both from Xcode and from the command line. There are a couple of answers on StackOverflow, nothing helped. What could be the problem? One of the things I tried: xcodebuild -project PhotoBook.xcodeproj -scheme PhotoBook -configuration Release -archivePath Release/PhotoBook.xcarchive -destination 'generic/platform=iOS' -verbose archive xcodebuild -exportArchive -archivePath Release/PhotoBook.xcarchive -exportPath Release -exportOptionsPlist ExportOptions.plist -destination 'generic/platform=iOS' -verbose ExportOptions.plist method app-store-connect teamID T672CQXP54 uploadSymbols uploadBitcode signingStyle manual provisioningP

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.

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

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

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.

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

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