ITMS-90158

Hello, While we are uploading our App in TestFlight for external testing then after 1 minute we are getting invalid binary issue. Issues have been mentioned below. ITMS-91061: Missing privacy manifest - Your app includes “Frameworks/Capacitor.framework/Capacitor”, which includes Capacitor, 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 manifest - Your app includes “Frameworks/Cordova.framework/Cordova”, which includes Cordova, an SDK that was identified in the documenta

I am creating an AI powered mobile application for my university dissertation that utilises Google Gemini in order to generate tailored responses with a prerequisite prompt. In order to facilitate this, I use an API key which allows the communication to be made. I received an email upon archiving my application that informed me that: ITMS-90683: Missing purpose string in Info.plist - Your app’s code references one or more APIs that access sensitive user data, or the app has one or more entitlements that permit such access. The Info.plist file for the “Amrit AI.app” bundle should contain a NSSpeechRecognitionUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. If you’re using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. I have since made the adjustments to my info.plist by adding a description as to why the API key is being

After I uploaded a new build of my app yesterday with Xcode 16.3, I received an email from App Store Connect about issues with the build: This is for your information only and doesn't require any action: ITMS-90078: Missing potentially required entitlement - Your app, or a library that’s included in your app, uses Apple Push Notification service (APNs) registration APIs, but the APS Environment Entitlement isn’t included in the app signature’s entitlements. However, my app doesn't use APNs registration APIs. It does use CloudKit, which is my only guess about what could be triggering the email. I've never seen this warning before with previous builds of the app, and the only change in the new build was a small bug fix. Has anyone else seen this?

We're building an SDK (let's call it MyFramework) which is distributed as an .xcframework for developers to integrate it into their own apps. Recently, we've added tvOS support by adding it as a supported destination for the SDK. Essentially, the SDK became a cross-platform framework and easy to be adopted in both iOS and tvOS apps. The .xcframework is generated fine, all builds correctly. We've tested the SDK integrated in test apps. We've also submitted an iOS archive app to the AppStore connect, just to make sure all is well with the AppStore submission. However, when I tried submitting a tvOS archive app (that integrates the same SDK) to the AppStore connect, the build was marked as invalid binary and we've got the following error message: ITMS-90562: Invalid Bundle - One of the nested bundles is built for a platform which is different from the main bundle platform. Please make sure that all bundles have correct platform specification. First, I thought that any of the modules of the framework was

So I submitted my app for TestFlight external testing and got this email: ITMS-90078: Missing potentially required entitlement - Your app, or a library that’s included in your app, uses Apple Push Notification service (APNs) registration APIs, but the APS Environment Entitlement isn’t included in the app signature’s entitlements. If your app uses APNs, make sure the App ID is enabled for push notifications in Certificates, Identifiers & Profiles, sign the app with a distribution provisioning profile that includes the APS Environment Entitlement, and upload a new build to ensure that push notifications function as intended. For details, visit: https://developer.apple.com/documentation/usernotifications/registering-your-app-with-apns. But here's the thing: everything this says is 100% bogus. My app uses no libraries and no push notification service registration APIs. The term register is used in my app, because I use table view cell registrations. Could that be the cause of this bogus warning?

Hello, I recently updated my app, and in the Transporter app it said that the processing failed. This is the email I recieved: Please correct the following issues and upload a new binary to App Store Connect. ITMS-90048: This bundle is invalid - Your archive contains paths that are not allowed: [._Symbols] I couldn't find anything related to this in XCode or anywhere else on the internet. What did I do wrong? For context, I am developing using Expo and React Native.

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

Hi there, I uploaded an update bundle for the posted app, but I got a rejection message. ITMS-90048: This bundle is invalid - Your archive contains paths that are not allowed: [._Symbols] The XCode version I'm using is 16.2, and I've been trying to find a route using Run Script and Finder, but I don't know what the hell it is about. Does anybody know what could cause this issue? Any help would be appreciated. Thanks.

I have the problem after I upload build to App Store Connect. I always get error ITMS-90129: The bundle uses a bundle name or display name that is already taken.. when I set CFBundleDisplayName and CFBundleName to be Companion but if I set to others such as ECHO then it can be uploaded without error. I contact to support via email and case number is 102554754170 and Bobby from developer support suggested me. The problem was that the Product Name was different than the Display Name.” I replied email that I tried it as below. Target Name = Companion, Product Name = $(TARGET_NAME), CFBundleDisplayName = $(PRODUCT_NAME), CFBundleName = $(PRODUCT_NAME) Target Name = Companion, Product Name = Companion, CFBundleDisplayName = Companion, CFBundleName = Companion I still get error but if I change CFBundleDisplayName and CFBundleName to be other app name such as ECHO, Facebook then it can be uploaded successfully. I'm not sure if there is something with Companion on validation process. Then he suggest me to co