I am reaching out regarding the ITMS-91061 rejection issue we encountered while submitting our app to the App Store. The rejection is related to missing privacy manifests for Firebase and related SDKs. Currently, our PrivacyInfo.xcprivacy file is structured as follows: Could you please confirm whether we can modify this file to include Firebase-related privacy information to resolve the rejection? If so, could you provide guidance on the correct format and the necessary entries we should add? We appreciate your support and look forward to your response.
Search results for
ITMS-90158
1,685 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
I am attempting to upload an application to the app store. The selected method was using Transporter through terminal commands. In this sense, I keep receiving a metadata error which is as follows : Command (Assume values are filled in) /usr/local/itms/bin/iTMSTransporter -m upload -u MY_EMAIL -p YOUR_APP_SPECIFIC_PASSWORD -f /Users/isseyyohannes/Desktop/ALGORA_Performance.itmsp --asc-provider GL5BCCW69X -v detailed I receive the following error Package Summary: 1 package(s) were not uploaded because they had problems: /Users/isseyyohannes/Desktop/ALGORA_Performance.itmsp - Error Messages: ERROR ITMS-3000: Line 9 column 25: element data_file incomplete; missing required elements checksum and size at XPath /package/software_assets/asset/data_file ERROR ITMS-3000: Line 12 column 24: element software_metadata not allowed here; expected the element end-tag or element metadata_token at XPath /package/software_metadata ERROR ITMS-3000: Line 13 column 19: element software not
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect API
Tags:
App Store Connect
App Submission
UPDATE : I was able to narrow down my metadata errors vaslty. The only error that sustains is as follows. Package Summary: 1 package(s) were not uploaded because they had problems: /Users/isseyyohannes/Desktop/ALGORA_Performance.itmsp - Error Messages: ERROR ITMS-3000: Line 16 column 15: element versions not allowed here; expected the element end-tag or element metadata_token at XPath /package/versions ERROR ITMS-3000: Package null failed schema validation. [2025-02-20 12:23:44 EST] DBG-X: Returning 1 This is the structure of my metadata file. GL5BCCW69X GL5BCCW69X ALGORA_Performance.pkg ALGORA Performance Trading made easy. This app is optimized for macOS trading. Any insight on to what I may be doing wrong in my metadata.xml file would be appreciated. Thank you. Note : md5 was hidden on purpose.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect API
Tags:
I encountered the same issue. I received an email from Apple stating that the app was rejected due to ITMS-91061: Missing privacy manifest in third-party SDKs. The list of affected SDKs is as follows: https://developer.apple.com/support/third-party-SDK-requirements.
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Do you have the complete report to see the list of dependencies? The error message 'ITMS-91061: Missing privacy manifest' indicates that your iOS app is missing the necessary privacy manifest files for certain features you are using in your app. The privacy manifest files are required to disclose how your app uses sensitive user data, such as location, contacts, photos, etc. In your case it seems like is a third party library. Third-party frameworks also require a privacy manifest and signature. It seems like your report is asking for the privacy manifest for GoogleDataTransport that may be a dependency. Check all their dependencies for GoogleToolboxForMac. https://developer.apple.com/support/third-party-SDK-requirements/ Please refer to the link provided above. The library you are currently using, GoogleToolboxForMac as well as GoogleDataTransport, is included in the list. It seems by the error that could be one of the dependencies. Do you have the complete report? The third-party library you receiv
Topic:
Privacy & Security
SubTopic:
General
Same Here ITMS-91061: Missing privacy manifest - Your app includes “Frameworks/FirebaseCore.framework/FirebaseCore”, which includes FirebaseCore, 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.
Topic:
Privacy & Security
SubTopic:
General
Tags:
We are developing a Flutter application targeted for MacOS and Windows . We are using the FlutterMacOS and connectivity_plus packages in our app But whenever we are releasing a version to App Store we are getting the privacy manifest file missing for above 2 packages We tried to add xcPrivacy file inside the Runner Xcode project. But that doesn't solve the issue Adding the relevant lines from the warning email getting from App Store below ITMS-91061: Missing privacy manifest - Your app includes “Contents/Frameworks/FlutterMacOS.framework/Versions/A/FlutterMacOS”, which includes Flutter, an SDK that was identified in the documentation as a commonly used third-party SDK. Starting February 12, 2025, 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 or you won’t be able to submit the app for review in App Store Connect. Please contact the provider of the SDK that includes this file to get an updat
Hi I have an app with an Intents extension and a Widget extension that is failing to upload to App Store connect. I am receiving the following error and I have no idea how to fix it ERROR ITMS-90896: Invalid Mach-O header. The __swift5_entry section is missing for extension bundle Payload/[AppName].app/PlugIns/WidgetsExtension.appex, which prevents the extension from running. You can run the otool command against your binary to ensure there is a __swift5_entry section. This worked fine a couple of months ago on last submission. Thanks Alan
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Store Connect
App Store
I am trying to submit my app for review on appstoreconnect, but after every attempt it immediately says your app has been changed to invalid binary and rejected. The error related to this rejections is: ITMS-91064: Invalid tracking information - A PrivacyInfo.xcprivacy file contains invalid tracking information at the following path: “Frameworks/MapboxCoreSearch.framework/PrivacyInfo.xcprivacy”. NSPrivacyTracking must be true if NSPrivacyTrackingDomains isn’t empty. Keys and values in your app’s privacy manifests must be valid. Despite the fact that my app's PrivacyInfo.xcprivacy states no that there are no tracking domains, privacy tracking is not enabled and that the Privacy Nutrition Label Types clearly state that there are no particular tracking happening across the selected the labels, which are course location, precise location and search history. The information in the IPrivacyInfo.xcprivacy in the app privacy settings and reflect that there is no tracking happening. I have attempted changing
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags:
App Tracking Transparency
App Store
Frameworks
Privacy
I am trying to set up a workflow where Apple Vision Pro users in my organization can install a signed enterprise .ipa file from an internal web page. The relevant link looks something like this: <a role=button href=itms-services://?action=download-manifest&url=https://my.example.com/path/manifest.plist>Click here to download</a> After verifying that all the mime types were correct on the server and the certificate was valid, I finally attached my AVP headset to my Mac's console app and saw that the errors look like this: [com.example.myapp] Skipping due to incompatible platform: com.apple.platform.xros Could not load download manifest with underlying error: Error Domain=ASDErrorDomain Code=752 Not compatible with this platform: com.apple.platform.xros UserInfo={NSDebugDescription=Not compatible with this platform: com.apple.platform.xros} This manifest.plist was made by the Distribute App workflow in Xcode 16.0. Multipart question: Is installing VisionOS apps via m
I've received this email when attempting to upload my app to test flight, but I have a long description like This app collects motion data to track user activity and provide accurate workout insights. Motion tracking helps improve fitness and health-related features. specified in the project.pbxproj file, which is where all of these parameters are (and where I've specified them in the past).
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
Using JWT token generated by following these steps , I successfully uploaded .ipa via iTMSTransporter on Linux using the following command as described here sudo /usr/local/itms/bin/iTMSTransporter -m upload -o ~/Desktop/mylogFile.log -jwt myGeneratedJWT -v eXtreme -assetFile AppName.ipa -assetDescription AppStoreInfo.plist
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
This is the altool command -> FAILURE xcrun altool --verbose --list-providers -u USERNAME --password APPLICATION_PASS 2025-01-28 11:54:56.589 Verbose logging enabled. 2025-01-28 11:54:56.591 Will look for transporter at executable bundle relative path: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/itms/bin/iTMSTransporter 2025-01-28 11:54:56.591 Looking for Transporter at path: /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/itms/bin/iTMSTransporter 2025-01-28 11:54:56.591 Looking for Transporter at path: /Applications/Xcode.app/Contents/Developer/usr/bin/../SharedFrameworks/ContentDeliveryServices.framework/itms/bin/iTMSTransporter 2025-01-28 11:54:56.591 Looking for Transporter at path: /Applications/Xcode.app/Contents/Developer/usr/bin/../itms/bin/iTMSTransporter 2025-01-28 11:54:56.591 Looking for Transporter at path: /Applications/Transporter.app/Contents/itms/bin/iTMSTransporter 2025
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
I archived and uploaded a build with Xcode 16 RC earlier today since it wasn't available in Xcode Cloud at that moment. The upload was successful. Since then, Xcode Cloud was updated with Xcode 16 RC and I can build and deploy to TestFlight and App Store Connect that way too. Now, upon submitting my app to App Review, the binary is being rejected as invalid due to unsupported version of Xcode. Rejections Sept 9th at 11:28 PM Central and Sept 10th 12:37 AM. Here is the error message I received via email: ITMS-90111: Unsupported SDK or Xcode version - App submissions must use the latest Xcode and SDK Release Candidates (RC). For details on currently supported versions, visit: https://developer.apple.com/news/releases. Upon visiting the site, you can see a developer news article stating that App Review is now accepting builds created from Xcode 16 RC. I assume this is just the system going through upgrades and the whole system isn't updated yet. Is anyone else having issues submitting Xcode 16 RC builds
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags:
Xcode
App Store Connect
App Review
Xcode Cloud
I'm dealing with a problem uploading our release binaries that is completely perplexing. If I use the ITMS Transporter desktop app to upload my IPA, everything works fine. If I use the ITMS Transporter command line interface (which i'm calling from inside the desktop app's directory /Applications/Transporter.app/Contents/itms/bin/iTMSTransporter -m upload...) to upload my IPA, I get the following error ERROR ITMS-90529: Invalid package. Applications built with sdk 9.0 or later must be packaged as proper IPA files. No idea why this error is coming up. I can also use altool to upload my binaries successfully. The issue is altool is being deprecated and I need to be able to use the ITMS command line interface as part of some deployment scripts we have. Please help!
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Store Connect
Command Line Tools