ITMS-90158

I'm struggling to get past the following error from Transporter. I've tried everything I can think of and I'm not sure what else to do. WARNING ITMS-90885: Cannot be used with TestFlight because the executable “${executable}” in bundle “${bundle}” is missing a provisioning profile but has an application identifier in its signature. Nested executables are expected to have provisioning profiles with application identifiers matching the identifier in the signature in order to be eligible for TestFlight. Setup I'm using electron with a main.app and nested helper apps (e.g. Main.app/Contents/Frameworks/Main Helper (Renderer).app) I'm trying to upload to the Mac App Store I'm codesign-ing the contents with Apple Distribution: ... and signing the pkg installer with 3rd Party Mac Developer Installer: ... I'm using osx-sign to manage the code signing for me: basically it's doing a whole bunch of this: codesign --sign {40-char-hash} --force --timestamp --options runtime --entitlements $CHILD_PLIST packages/mas

I suddenly started to receive the following email with the error in it stating that my uploaded app is not available to be used in TestFlight: ITMS-90886: 'Cannot be used with TestFlight because the signature for the bundle at “MyApp.app/Contents/PlugIns/MyAppWidgetExtension.appex” is missing an application identifier but has an application identifier in the provisioning profile for the bundle. Bundles with application identifiers in the provisioning profile are expected to have the same identifier signed into the bundle in order to be eligible for TestFlight.' It was all working fine and now I am not sure even where to start looking. Signing, provisioning and everything else is managed automatically.

After uploading a debug build to testflight getting an email stating ITMS-90755: Invalid Binary - The following binaries in your app contains prohibited instructions: AppName.app/App. Remove the instructions from the binaries, rebuild and resubmit.. To the best of our knowledge we haven't added any prohibited instructions of any kind, and the email also doesn't provide any information on what the offending instruction is. After much trial and error we found switching a property from an array to a non-array makes the error go away and testflight accepts the build, which obviously doesn't make any sense as to why that change produces this error. Is this some kind of false positive happening or what else is going wrong? Any help to resolving the issue is much appreciated.

I write this macOS app with Python PyQt and build a “.pkg” file, without using Xcode, and use Transporter app to verify. I successfully build the “.pkg” file which can pass Transporter app’s verification. When I do the code signing with my.app, I get the error message my.app: replacing existing signature my.app: bundle format unrecognized, invalid, or unsuitable In subcomponent: my.app/Contents/MacOS/lib/PyQt5/Qt5/qml/QtQml/Models.2 so I find the answer https://github.com/pyinstaller/pyinstaller/wiki/Recipe-OSX-Code-Signing-Qt to solve this problem. Below is my command: python Installer/mac/fix_app_qt_folder_names_for_codesign.py Installer/my.app pkgbuild --install-location /Applications --component my.app my.pkg productbuild --distribution dist.xml --package-path ./my.pkg ./my_final.pkg productsign --sign xxx my.pkg my_signed.pkg my.app directory tree my.app ├───Contents ├───_CodeSignature ├───embedded.provisionprofile ├───Frameworks ├───Info.plist ├───MacOS └───Resources ├───icon.icns └───lib └───PyQt5 └───

I've added NFC support for my app. So, my UIRequiredDeviceCapabilities were extended from armv7 to armv7 nfc. This means I've prevented this application from running on devices supported by previous versions. Now I've received a message from Apple: ITMS-90109: This bundle is invalid - The key UIRequiredDeviceCapabilities in the Info.plist may not contain values that would prevent this application from running on devices that were supported by previous versions. What is the right way to add new functions?

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

Do any Apple tools exist that currently enable Bulk IAP management? I have been trying to use the iTMSTransporter, and the following command does respond appropriately, but the metadata.xml that is returned is incredibly bare, and does not include any of the 50+ IAPs we have in our app. ./Transporter.app/Contents/itms/bin/iTMSTransporter -m lookupMetadata -u *** -p *** -destination ~/Desktop/IAP -apple_id *** -app_platform ios -subitemtype InAppPurchase

After a successful app delivery I received the email from App Store Connect. It says: Dear Developer, We identified one or more issues with a recent delivery for your app, XXXXX. Please correct the following issues, then upload again. ITMS-90626: Invalid Siri Support - Sample phrase 'Play Fan on deep sleep sounds' cannot contain 'fan' ITMS-90626: Invalid Siri Support - Sample phrase 'Find Fan on Deep Sleep sounds' cannot contain 'fan' ITMS-90626: Invalid Siri Support - Sample phrase 'Play Fan on Deep sleep sounds' cannot contain 'fan' .... and some more all complaining about 'fan'. I couldn't really find anything on Google related to Siri Support and cannot contain. Does anybody have idea what could be wrong? Thank you!

Hi all, I recently uploaded my app to the App Store and received the following error message: ITMS-90961: Invalid bundle - The app at 'xxx.app' contains a single-size app icon but has a value of 11.0 for the MinimumOSVersion key in its Info.plist file. Include all app icon sizes to support iOS 11.0 or later, or update the iOS Deployment Target to 12.0 or later to support uploads with a single-size app icon. I have checked my assets and confirmed that the AppIcon is set to All Sizes and not Single Size. Is this an issue with Apple's systems or is there something I am doing wrong? Any help would be greatly appreciated. My Xcode version is 14.3 Thanks in advance.

I developed a companion apple watch app for our iOS app. I was able to successfully archive the build but I am getting this error mail from Appstore connect when submitting the build - 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. Any idea how to fix this issue?

We are trying to upload new build for our already existing app to appstore, with a build script to embed framework(Which is just copying from build directory to MyApp.app/Frameworks). Everything builds and works fine in my local machine. But getting this error while uploading to appstore. ITMS-90432: Invalid Swift Support - The file MyApp.app/Frameworks/Framework1.framework, MyApp.app/Frameworks/Framework2.framework doesn’t have the correct file type for this location. Ensure you’re using the correct file, rebuild your app using the current public (GM) version of Xcode, and resubmit it. We are copying to the correct directory, but still getting the above error while uploading. Are we missing the obvious here?

I submitted a test package and got the following email: ITMS-90345: Metadata/Info.plist Mismatch - The value for bundle_identifier in the metadata.xml file does not match the value for CFBundleIdentifier in test [net.neolib.test.pkg/Payload/test.app]. I really don't have any idea what's wrong. It's a simple (almost blank) app with nearly no modification (except linked with a dylib). What is the metadata.xml? I cannot find it in my test project.