ITMS-90338

We have a CD pipeline set up for many apps (we're an app dev agency, we're uploading apps all the time). Uploads of our apps to AppStoreConnect using the iTMSTransporter command line tool started failing a few days ago. If we attempt to upload the same bundle using the Mac Transporter app, it uploads just fine. The problem only seems to be the iTMSTransporter command line tool. The version of the tool we're using is: iTMSTransporter, version 3.3.0 I've also tried running these commands pointing at the version of iTMSTransporter running at /Applications/Transporter.app/Contents/itms/bin/iTMSTransporter but this won't even start due to some Java security certificate issue. An example of the command we are calling is: /usr/local/itms/bin/iTMSTransporter -m upload -v eXtreme -f /path/to/Bundle.itmsp -jwt {generatedJwtHere} The bundle appears to actually upload to the AppStore OK, after lots of logs we get a message like: INFO: Reservation committed: (CPUSource221/v4/0b/e5/74/0be57409-0479-3c02-0

I get the folling error when trying to upload an app to TestFlight with an iMessage stickers extension with XCode 8.0 beta 3:ERROR ITMS-90644: Missing Image Asset. Your app is missing the Large App Icon asset 'iMessage App Icon' in 'Payload/App.app/PlugIns/StickerPackExtension.appex'.Is ITC accepting TestFlight builds at the moment, or is there something wrong with my extension? I've allocated images to every space in my iMessages App Icon in my .xcstickers bundle.I did notice though that the various settings images and the 1024x768 iMessages App Store image don't make it through to the built .appex file though.

Hello, i know this topic is here since ever, also in other forums, however this topic i face for a month and cant get pass it, I tried all other suggestions which didnt bring me anywhere. so, project using cmake in order for Qt creator (so c++ base project with enabled swift), however once i run a cmake which generates *.xcodeproj for Xcode, i open it via xcode and can properly build and deploy to device. however when I try to archive and sent to Testflight/AppStore, I get: ITMS-90426: Invalid Swift Support and when I try to followup guides to create it manualy, copying libs from: $(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME) plese here note, that ALL guides indicate to use folder swift, however there are no *.dylib files... they are only in swift-5.0 folder then I receive an error type: ITMS-90429: Invalid Swift Support - The files libswiftMetal.dylib, libswiftHomeKit.dylib, libswiftsimd.dylib, libswiftCallKit.dylib, libswiftos.dylib, libswiftNetwork.dylib, libswiftMapKit.dylib, libsw

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

Hi, I have an error while uploading to test flight by fastlane and transporter. 07:13:05 [Transporter Error Output]: Return status of iTunes Transporter was 1: ERROR ITMS-90165: Invalid provisioning profile signature. The provisioning profile included in the com.test.example bundle [“Payload/Example.app”] can't be used to upload apps to App Store Connect until it has a valid signature from Apple. My xcode version is 15.4 and the iTMSTransporter is 3.3.0. It seems like this error has been reported the other internet recently. https://stackoverflow.com/questions/79118087/getting-error-invalid-provisioning-profile-signature-in-transporter-while-ios-ap https://www.yunedit.com/article/error90165 Has anyone solved this?

Hi, I uploaded an updated version of my app to App Store Connect yesterday, usually my build would show up under half an hour but this time it hasn't after over 16 hours. It's a simple app. I cleared an earlier version, then there was an email saying Although delivery was successful, you may want to correct the following issues in your next delivery. Once you've corrected the issues, upload a new binary to App Store Connect. ITMS-90899: Macs with Apple silicon support issue - The app isn‘t compatible with the provided minimum macOS version of 13.5. It can run on macOS 14.0 or later. I unchecked the box that says use for Mac option. I have written to Apple support, yet to hear from them, Meanwhile should I re upload the app with a newer build number and version? Thanks a lot. (I saw quite a few threads on this topic with no one close to any solution so asking again just in case)

I'm trying to upload a build to app store connect. It's a build from a Unity project with the polyspatial SDK, and I also need to include a c++ library, which I've added as a dylib signed with the same provisioning profile as the app. The profile is an Apple Distribution profile created from an enterprise account. It succesfully uploads to Appstore connect, but fails with the following error message: ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. This is unhelpful as I'm using a current version of Xcode. I've read that it's a provisioning issue, but I'm using the provisioning profile for apple distribution on an enterprise account, not an ad hoc profile. I've tried manually adding the SwiftSupport folder from the Xcode toolchain to the ipa/xarchive, resign and upload with Transporter, but that doesn't work. After spending a day trying to troubleshoot this, I'm at a loss. Any help with this is muc