ITMS-90158

An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes , which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting 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. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privac

We have prepared the Package of our Application for MacOS using Delphi Sydney 10.4. When we upload it using Transporter the delivery appears correct, but after a few minutes we received an eMail from AppStore Connect reporting errors ITMS-90238: Invalid Signature. The errors refer to dynamic libraries, .a, that we have located in the Frameworks folder of our package, all the libraries have been developed with XCode and signed with CodeSign using Certificate 3rd Party Mac Developer Application ....., the same certificate that we use to sign the application. Installing the package generated by Delphi on our MAC and analyzing the signature of the libraries with CodeSign, we see that the signatures have not been lost and are correct. WE DO NOT KNOW WHAT WAY WE SHOULD TAKE, we would ask you to indicate a solution to finally be able to publish our Application in the AppStore. THANK YOU.

We have prepared the Package of our Application for MacOS using Delphi Sydney 10.4. When we upload it using Transporter the delivery appears correct, but after a few minutes we received an eMail from AppStore Connect reporting errors ITMS-90238: Invalid Signature. The errors refer to dynamic libraries, .a, that we have located in the Frameworks folder of our package, all the libraries have been developed with XCode and signed with CodeSign using Certificate 3rd Party Mac Developer Application ....., the same certificate that we use to sign the application. Installing the package generated by Delphi on our MAC and analyzing the signature of the libraries with CodeSign, we see that the signatures have not been lost and are correct. WE DO NOT KNOW WHAT WAY WE SHOULD TAKE, we would ask you to indicate a solution to finally be able to publish our Application in the AppStore. THANK YOU.

I have had the same problem. The apple ids I have used include com.appname, com.domain.appname, com.domain.appname.XXX. None of these bundle identifiers have worked. This is the error message I receive each time:ERROR ITMS-90347: Bad bundle identifier. The bundle identifier 'com.Signal' of the application extension Signal.app/PlugIns/Signal.appex should start with the application's bundle identifier 'com.Signal' and not contain more than one period “.” after the application's bundle ID. ERROR ITMS-90347: Bad bundle identifier. The bundle identifier 'com.Signal' of the application extension Signal.app/PlugIns/Signal.appex should start with the application's bundle identifier 'com.Signal' and not contain more than one period “.” after the application's bundle ID.The domain is always drewbennettappname: SignalI have looked at all of these sites:An App ID with Identifier 'com.example.app.extention' is not available. Please enter a different stringhttps://forums.developer.apple.com/thread/15712ER

Hi Apple developer folks,I have in-house IPA which stored in my local/internal server with configured self-signed certificate. And we are intented to deploy ipa via OTA with intranet.My IPA file and .plist file are stored in the same document root path. However, when I tried to exeucte the itms-services command in my idevice (version 10.0.x-10.3.x), it shows the error message Cannot connect to 192.168.x.xif apple has blocked the entirely selt-signed certificate? could not find any article related from apple forum though. Kindly enlighten me if there is possibility to install ipa via OTA with self-signed certificare (OpenSSL) configured.Below is my itms-services URL sample:itms-services://?action=download-manifest&url=https://192.168.x.x/plist/c.plistI can download my IPA file and plist file with no issue if I browse to the URL directly, but it just doesn't work with the itms-services.Any idea on what's going on?Thank you very much.

To Whom It May ConcernWhen uploading my IPA file using Application Loader I am getting the error ITMS-90166 - Missing Code Signing Entitlements. I am getting the ITMS-90166 Missing Code Signing Entitlements error when trying to upload my Xamarin IOS App to the App Store. I noticed some information about removing executables from the IPA but this caused another error whereby it stated it did not contain an AppBundle executable. I also tried deleting the .exe file from the IPA but this caused the Payload directory to be invalid. I ensured that Entitlements.plist was not in the IPA as it is a known contributor to the issue. I am wondering if anyone could point me in the right direction?

I want to create a hyperlink for OTA installation of my iOS app on the Azure DevOps wiki page, has anyone tried it? I have tried using html tag, but when I click it, it only refreshes the wiki page. This is the link example using tag. My App I have also tried using markdown link, but it seems it doesn’t recognize itms-services syntax, this is the link example [My App](itms-services://?action=download-manifest&url=https://my.app.com/install.plist)

I got this error while attempting to upload to test flight:ERROR ITMS-90502: Invalid Bundle. Apps that only contain the arm64 slice must also have 'arm64' in the list of UIRequiredDeviceCapabilities in Info.plist.I searched around I found solutions including:Setting Build Active Architecture to Yes (didn't affect since my project only supports arm64)Changing Archive Build Configuration to Release (already did)Unplug the device from my mac when Archiving (I am already praying to the machine spirits by this part)Lastly,Adding UIRequiredDeviceCapabilities with item arm64 to all target's info.plist This is the one I am troubled with. It is most certainly what the error requires me to do but I did for every info.plist I can find in my project. Including the main one created automatically when I created my project, one for each test build(not sure if needed just did anyway), one for the everyday widget extension my app has, one for every framework I used added via cocoapods (I edited the podfile to do it b

We are facing the below mentioned error frequently while submitting the different apps in the App Store. When we are uploading the first build, we are receiving the below mentioned error and if we increment the build version, and on re submitting we are not facing the same issue again. Could you please guide us on what caused this issue? Xcode Version: 14.2 Error : ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.. 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.

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

I'm absolutely certain this is just a result of me missing something very obvious, but I keep getting a string of errors when uploading from Xcode 11. All my icons are in place, but the errors are asking for alternative sizes ( i.e. 54 x 40, 148 x 100), that are even listed in the app icon location. I ended up switching back to an older version of xcode, and it uploaded just fine. But I would really like to sort this out so I can use the most recent Xcode in the future. I also get an Error ITMS- 90642: Missing Info.plist Key, for some reason. Again, had none of these errors in the previous xcode.

Build the archive, validating and uploading it to App Store Connect - TestFlight is successful from Xcode (16.0, macOS 15.1.1). Although after that the build is rejected stating : ITMS-90429: Invalid Swift Support - The files libswiftCoreFoundation.dylib, libswiftCoreData.dylib, libswiftCore.dylib, libswiftFoundation.dylib, libswift_Concurrency.dylib, libswiftObjectiveC.dylib aren’t at the expected location /Payload/Runner.app/Frameworks. Move the file to the expected location, rebuild your app using the current public (GM) version of Xcode, and resubmit it. Cross checked the Archive and .ipa file, where we found that the mentioned .dylib files are actually present inside the /Payload/Runner.app/Frameworks folder, and all the .dylib files are also present in the SwiftSupport/iphoneos folder. Scenario : using tdLib compilation libtdjson.xcframework (embedded & signed) for ios arm64 placed under Framworks, in my Flutter application, calling methods via Method Channels, interacting with AppDelegate.

We have an app that we had in TestFlight, submitted a version for release, was approved, and had the build in state waiting for developer release. In the meantime, our TestFlight build is about to expire, and will expire before we are ready to release the app to the App Store. Every time I try to upload a new version of the app, I get the error ITMS-90129: The bundle uses a bundle name or display name that is already taken. I've tried just abut everything I can think of: I changed the bundle versions (from 1.0 to 1.0.1, and incremented the build number). I cancelled the build that was pending developer release. I still get the same error. I've confirmed that the bundle ID and display name are the same as the ones for the build we had submitted for approval previously.

Hi guys,we are trying to upload our App bundle with xCode 7.1 (we tried also with App Loader 3.0) but we are constantly getting this error:ERROR ITMS-90207: Invalid Bundle. The bundle at 'xxxxxxxxx' does not contain a bundle executable.All the Certificates/Identifiers are correct (we checked with Apple support). Of course the IPA package has the executable file, we checked a million times. Did you ever experienced something similar? Any suggestion? Thanks in advance.P

ITMS-90338: Non-public API usage - The app references non-public selectors in SMMplanner: _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 http://developer.apple.com/support/technical/