“ITMS-90158”

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?

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.

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 am trying to submit my AppleTV app to the store but I am getting 2 of these errors when the archive is uploaded:Missing info.plist KeyCGBundleicons.CFBundlePrimaryIcon key is missingTVTopShelfImage.TVTopShelfPrimaryImage key is missingAll images are included int eh assett catalog. Anyone else have this issue?

FB not allowedi want a link in my app to open facebook profile.an idea?thanksSabino

I am trying to upload my app to the App Store and keep getting this error and I dont know what to do. This bundle is invalid. The Info.plist file is missing or could not be parsed. Please check it for embedded control characters. Can anyone help me with this?

in this weeks i received this error: ITMS-91055: Invalid API reason declaration - The PrivacyInfo.xcprivacy for the “VanigliaPro” file contains “App Functionality” as the value for a NSPrivacyAccessedAPITypeReasons key instead of a valid reason code for using an API in the NSPrivacyAccessedAPICategoryFileTimestamp category. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, values for NSPrivacyAccessedAPITypeReasons keys in your app’s privacy manifest must be valid reason codes for the corresponding API category. 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. ITMS-91053: Missing API declaration - Your app’s code in the “xxxx” file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryUserDe

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. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/ Best regards, The App Store Team !!! Please tell us how to solve this problem step by step !!!

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

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.

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/

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)

We received this error after submitting to apple connect today. How can we resolve this issue? Dear Developer, We identified one or more issues with a recent delivery for your app, ****** 1.14 (33). Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public selectors in ErgoAuditor: 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/ Best regards, The App Store Team

Hello, we are having this response when submitting our application, but in the return email from the Apple Store Connect it does not show what would be the point to correct. Is anyone else having this too? any idea what to do? Thanks in advance.. Dear Developer, We identified one or more issues with a recent delivery for your app, []. Please correct the following issues, then upload again. 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. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/ Best regards, The App Store Team