ITMS-90158

I submitted my app for review and I get an invalid binary error and this email: App Store Connect Hello, We noticed one or more issues with a recent submission for App Store review for the following app: matrixcargo - Motorista Version 1.27.12 Build 10 Please correct the following issues and upload a new binary to App Store Connect. ITMS-91054: Invalid API category declaration - The PrivacyInfo.xcprivacy file at the “ReactNativeMapsPrivacy.bundle/PrivacyInfo.xcprivacy” path contains “NSFileModificationDate” as the value for a NSPrivacyAccessedAPIType key, which is invalid. Values for NSPrivacyAccessedAPIType keys in your app’s privacy manifests must be valid API categories. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api.

Got this error running the following commands on Linux: /usr/local/itms/bin/iTMSTransporter -m provider -u username -p password -v eXtreme ERROR: Could not download Defaults.properties (launcher) Also, running java --version bash: java: command not found... But Java is installed on this directory: /usr/local/itms/java/bin/java Thanks Try to send Appele packages via iTMSTransporter

Hello guys i have a problem. I have one template package. and I publish many applications using this package. i change only names and colors. my other other project working fine , there is no problem. But I get this error on new one of them. My PrivacyInfo like this and my copy bundle resources like this i cant handle this problem . please help

After submitting our binary for review, we are receiving the Invalid Binary error, which appears to be related to the absence of privacy manifests for our third-party SDKs. Here is the part of an Appstore Connect email response (it's a part of a long email, containing such errors for 18 SDKs): ITMS-91061: Missing privacy manifest - Your app includes “Frameworks/AppAuth.framework/AppAuth”, which includes AppAuth, 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. Our application is built using Xamarin, and there are currently no available updates for the libraries that include the required manifests. Instead, we have a single consolidated privacy manifest that contains data for all the SDKs used

Hi, We recently migrated our iOS app icon to use the new 'single size' feature in xCode 14. However upon submission to App Store Connect we are getting the following issues: ITMS-90892: Missing recommended icon - The bundle does not contain an alternate app icon for iPad of exactly '167x167' pixels, in .png format for iOS versions supporting iPad Pro. 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/cfbundleicons ITMS-90892: Missing recommended icon - The bundle does not contain an alternate 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

We have a macOS app that has a Photos Extension, which shares documents with the app via an app group container. Historically we used to have an iOS-style group identifier (group.${TeamIdentifier}${groupName}), because we were lead by the web interface in the developer portal to believe this to be the right way to name groups. Later with the first macOS 15 betas last year there was a bug with the operating system warning users, our app would access data from different apps, but it was our own app group container directory. Therefore we added a macOS-style group identifier (${TeamIdentifier}${groupName}) and wrote a migration of documents to the new group container directory. So basically we need to have access to these two app group containers for the foreseeable future. Now with the introduction of iOS-style group identifiers for macOS, Xcode Cloud no longer archives our app for TestFlight or AppStore, because it complains: ITMS-90286: Invalid code signing entitlements - Your application bundle’s si

Xcode Cloud succeeds in building the Release configuration of the app, but whenever deployment preparation is set to TestFlight and App Store the last step fails with: ITMS-90035: Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “{AppName}.app/{AppName}” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/support/code-signing. When I build for release (with manual signing) everything work

I currently manually resign my application for distribution. Until recently I haven't had any issues with the provisioning profile which I place inside the bundle. However, I just got the following message from the store: ITMS-91109: Invalid package contents - The package contains one or more files with the com.apple.quarantine extended file attribute. The file it is referring to is: Contents/embedded.provisionprofile When I check the xattr on the provisionprofile I see the following line: com.apple.quarantine: 0081;675c6072;Chrome; So it seems like the provisionprofile I have downloaded from developer.apple.com has this attribute set. Any insights on how to properly deal with this submission issue?

Hi, our team received this message ITMS-90725: SDK version issue - This app was built with the iOS 17.0 SDK. Starting April 24, 2025, all iOS and iPadOS apps must be built with the iOS 18 SDK or later, included in Xcode 16 or later, in order to be uploaded to App Store Connect or submitted for distribution. We still have a requirement to support iOS 12.5.7 for our users. If I change to build SDK iOS18 using Xcode 16 or later, will my app submission be rejected during review process? (since I specified my minimum iOS version to be 12)

Flutter iOS App. Previous version submitted passed. Only change the version and some text, submit has 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. the release steps: flutter clean; flutter pub get; flutter build ios --release; xcode - clean build folder; archive; distribute app Searched online and tried many suggestions, none works.