“ITMS-90338”

Hi, When submitting manually signed macOS apps then this warning is shown after submission: WARNING ITMS-90889: Cannot be used with TestFlight because the bundle at is missing a provisioning profile. Main bundles are expected to have provisioning profiles in order to be eligible for TestFlight. I use the following commands for signing the app: export VM_CERTIFICATE=Apple Distribution codesign --deep -f -s $VM_CERTIFICATE -v --entitlements $VM_SOURCE_PATH/macos/App.entitlements $VM_APPNAME productbuild --component $VM_APPNAME /Applications --sign 3rd Party Mac Developer Installer: MyCompany outmac.pkg How can I get rid of the warning, so that the package can be used in TestFlight? Regards,

I am getting this issue on my apple developer mail. We identified one or more issues with a recent delivery for your app, 6.6 (6.7). Please correct the following issues, then upload again. ITMS-90036: This bundle is invalid - The Info.plist file for PassKit.framework is missing or could not be read. My app is running fine in debug mode and also it's archiving fine too.

I have made an app with Python and Kivy and am trying to get it going on TestFlight. The app also uses the Pyrebase module and its dependencies. I am Archiving it just fine with Xcode and moving through the steps just fine except when I try upload it. It fails and has about 38 very similar errors pop up saying: App Store Connect Operation Error ERROR ITMS-90171: Invalid Bundle Structure - The binary file 'weatherstrip.app/lib/python3.9/site-packages/Cryptodome/Hash/_MD2.abi3.so' is not permitted. Your app can’t contain standalone executables or libraries, other than a valid CFBundleExecutable of supported bundles. Refer to the Bundle Programming Guide at https://developer.apple.com/go/?id=bundle-structure for information on the iOS app bundle structure. But with different file names in each error. It seems that all of the listed errors are from the Cryptodome module from either the Hash or Cipher folders. All of the listed errors also happen to be .so files... I have tried to find answers all over bu

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 know this seems to be a issue with signing the application using Apples new Code Signature Format and there have been various fixes going round but they don't seem to apply/fix my issue. I'm seeing this with one of our In-House apps, our other apps have compiled/installed/run on iOS devices with no issues but this one app is proving stubborn. I've also tried creating a completely new project and strangely I'm seeing this issue with the new app as well. I'm running Monterey 12.0.1 with Xcode 13.1. The app is targeting iOS 15, it builds and runs on device running iOS 15.1.1 from Xcode fine. I've Archived and Exported with automatic code signing like all our other apps. Extracting the .ipa file and running codesign -dvvvvv ./Payload/AppName.app on the .app file gives: CodeDirectory v=20400 Page size=4096 -7=f98e5aa1b62669f050c7f71f4a36834a291ba177b4b8ce8a746de324098ce336 -6=0000000000000000000000000000000000000000000000000000000000000000 -5=d1343f304ebed50ddd6d18e38b6602a00cd6e784e02bfe9c5aef1240ace1734e -4=00

Hi All, I'm developing a security application that uses an endpoint security extension. The application has two parts main and extension. I have an entitlements for Security Extension Client from Apple. I'd like to distribute apps through the Apple Store. Locally the app runs without problems on enabled machines, but when I try to get it through Testfligt to the appstore I get two errors: ITMS-90285 - Invalid Code Signing Etitlements. Your application bundle’s signature contains code signing etitlements that are not supported on MacOs. Specifically, key ‚com.apple.developer.endpoint-security.client‘ ITMS-90296 - App sandbox not enabled on extension When I turn on sandbox for extension, the extension fails to register endpoint security client let res = es_new_client(&client) { _, event in self.eventDispatcher(msg: event) Without sandbox it runs without any problem. Thank you very much for your help I don't know how to proceed. Martin

We have developed a Watch App for our React-Native IOS app using SwiftUI. After the the integrations are completed, we've tried to upload the build to TestFlight for testing purposes. In the process, since enabling bitcode is mandatory for WatchOS apps, it is enabled through Project Target -> Build Settings -> Build Options -> Enable Bitcode : Yes (And also tried to enable bitcode for Pods target). However, there is no other option to enable bitcode in the Watch Targets (both watch app and watchkit extension). When we tried to upload the build to TestFlight, it got rejected with the error code: ITMS-90496: Invalid Executable - The executable {ProjectName}/Watch App WatchKit Extension.appex/WatchKit Extension does not contain bitcode. I have also read that in order to make the whole project bitcode enabled, you need to make sure that the libraries are also bitcode compatible. And since the app is a React-Native app, it contains a lot of 3rd party libraries. If anyone who tried to add a Watch

Hi guys, I am getting the following error when trying to upload for macOS. The same code works fine for iOS. 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 references non-public symbols in Contents/MacOS/XXX: _CMTimebaseCreateWithMasterClock. 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 Just FYI: I am not using CMTimebaseCreateWithMasterClock at all, but rather the preferred variant CMTimebaseCreateWithSourceClock. Neither of these are private AP

I have an application, released a few years back. The bundle ID starts with a digit, this used to be allowed. Now Xcode replaces the digit with a dash -, ie. 7K998EA8RN.org.nelsonmandela.quotes becomes -K998EA8RN.org.nelsonmandela.quotes Therefore on upload I get an error saying that the bundle ID does not match. If I end it the info manually and set the Bundle ID there, I can make it further down the process but still errors out as the application-identifier still becomes A8V6VR9K7C.-K998EA8RN.org.nelsonmandela.quotes the error returned is: ERROR ITMS-90046: Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, value 'A8V6VR9K7C.-K998EA8RN.org.nelsonmandela.quotes' for key 'application-identifier' in 'Payload/MandelaQuotes.app/MandelaQuotes' is not supported. This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle identifier. Any idea on how to resolve this