ITMS-90158

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

Our application should support locales for Albanian and Albanian(Kosovo). Xcode creates sq.lproj and sq-XK.lproj folders accordingly Everything works fine in xcode, but if we upload to appstore we always see this warning. I tried specifying other names for sq-XK to match https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPInternational/LanguageandLocaleIDs/LanguageandLocaleIDs.html aln, sq-RS, sq-KV, sq-KS, sq-Latn-XQ. The varning was always present. Is there any way to get rid of it? WARNING ITMS-90176: Unrecognized Locale - The locale used in localization directories at (Payload/{AppName}.app/base.lproj) are invalid. iTunes supports BCP47 but not the UN M.49 specification. Refer to the Language and Locale Designations guide for more information on naming your language-specific directories.

We have transferred our app from App Store Connect account to another. Transfer process was smooth and we we were able to move our app to new App Store account While uploading the new build for our app using the new account we received the below email. Can someone shed some lights on this and how can we make user to not to logout. ITMS-90076: Potential Loss of Keychain Access - The previous version of software has an application-identifier value of ['94B63VZT32.com.prasthana.tenmates'] and the new version of software being submitted has an application-identifier of ['G3M3U47GBZ.com.prasthana.tenmates']. This will result in a loss of keychain access.

Hello! So I updated my mac to 15.0 Sequoia Developer Beta and couldn't run Xcode 15.4 because of the Mac version mismatch, so I installed Xcode 16 beta and archived my app, but of course I cannot publish it to App Store because Apple doesn't let you do it with beta soft. So, I downloaded Xcode 15.4 (current latest stable build) and managed to run it following this fix: https://stackoverflow.com/questions/69994916/how-can-i-run-older-xcode-version-on-new-macos-version But, now when I create a new archive and submit it for review I am getting: ITMS-90111: Unsupported SDK or Xcode version - App submissions must use the latest Xcode and SDK Release Candidates (RC). For details on currently supported versions, visit: https://developer.apple.com/news/releases. I tried deleting derived data and build folders, building new archives, but to no avail. Has anybody encountered this before?

Hello. Icon fonts such as Font Awesome 6 and react-native-vector-icons are being rejected submission with the automated Invalid Binary error. ITMS-90853: Invalid font - There was an error validating the font named 'FontAwesome6Free-Solid' at 'private-app-name/FontAwesome6_Solid.ttf'. ‘glyf’ table instructions. These fonts have previously worked over the course of the last 3 years without issue and just stopped working on Monday. GitHub is filled with related issues and bug reports. This is likely affecting thousands of apps.