ITMS-90158

Hello, My team is currently having an issue uploading our app to the AppStore because of the following issues: ITMS-90562: Invalid Bundle - Bitcode failed to compile for your watchOS binary because it includes assembly source code or inline assembly. To resolve this issue, rewrite the corresponding code in a higher-level language such as Objective-C or Swift and redeliver your app. ITMS-90562: Invalid Bundle - There's an issue with the app's bitcode compilation. Rebuild the app using the current public (GM) version of Xcode and upload it again. Firstly, we do not have a watchOS app at all. Our last release was successful when built on Xcode 11.6 and we're currently using Xcode 11.7. According to Apple, Xcode 12 isn't required until April of 2021, so I'm not sure what it's complaining about. Here's what we've tried. We created an AppStore build and ran it through the validator and that succeeded. It even uploads fine, but doesn't successfully process once uploaded. We created an Enterprise ve

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'm an indie developer. My latest minor update for my game which has been on the Mac App Store for 13 years and which has spent time at #1 on the download charts just started getting rejected for the following reason: Guideline 2.5.2 - Performance - Software Requirements The app installed or launched executable code. Specifically, the app uses the itms-services URL scheme to install an app. However my app is certainly not installing any apps and to the best of my knowlege it is not using any itms/itunes/etc. type URLs in any way, so I can't figure out what would be triggering this claim. Inquiries as to what app I am supposedly installing or what URL I am supposedly using have yielded 'no further information can be provided'. Has anyone run into something similar? Any ideas on obscure scenarios that could trigger this particular rejection? Or any advice on what one should do in my situation? I feel a bit stuck. Has anyone had luck with the appeal process for this sort of thing (to at least g

I keep getting the ERROR ITMS-90125 : Invalid Binary everytime I try submitting to the App Store.I'm trying to get this up for external beta testers on iOS 9.I'm using Xcode 7 beta 6. (I submittted a build 2 days ago and it worked fine)Is this an Apple issue?

Hi together,yesterday I just tried to upload a minor update and I got the error Invalid Icon Name - The watch application '...' contains an invalid icon file name '.../AppIcon44x44@2x.png'. I've to mention, that I didn't make any changes at my icon set.I tried to fix this issue by changing all the names of my icons as suggested (AppIconXXxXX@YY.png). However, same error message. Then I deleted my image assets, the dervied data and added new assets with new catalogs (for watch, for iPhone/iPad). This solved the error above, but I got two new errors: (ITMS 90363 & 90391). I tried to fix that by deleting all CFBundleImage entries in my plists. Then I still got the error 90391.After spending hours on hours I don't no how to proceed! Does anyone know this issue? How to solve that?Walter

Recently I started getting emails from AppStoreConnect when I submit new builds The email states: ITMS-90863: Macs with Apple silicon support issue - The app links with libraries that aren’t present in macOS: /usr/lib/swift/libswiftCloudKit.dylib I can run this app on apple silicon from TestFlight or directly from Xcode and it runs just fine including all iCloud functions. This app has been using iCloud for several years now. So my question is: Should I just ignore the email or do I need to change something to bring this app into compliance?

ITMS-90334: Invalid Code Signature Identifier - The identifier 'bundle id followed by 30 random characters' in your code signature for 'bundle id' must match its Bundle Identifier 'bundle id' Currently, any app I’ve tried is getting this error when submitting from the app. I’ve got all the places where you put the name, the sku, and bundle id set with the same value (copy/paste), and I’ve tried different variations, but now that long string of random characters is appended and I can’t use TestFlight. Maybe because this is a beta iPad OS? Been on a beta for what seems like forever. It’s worked in the past. Great. Totally innocuous post that has something that is not permitted. Be nice if you TELL me what’s NOT PERMITTED!

Hey There, I'm trying to build a project on github, so I can get it working in testflight. The project can be found here: https://github.com/coderjoris/StructureScannerSwift I've downloaded it, added icons and all that good stuff and now I'm trying to archive and upload it. I can't seem to find out how to modify the project so it will submit successfully, I keep getting an email follow up with: ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. My submission steps are as follows: clean the build folder Product > Archive Then I follow the prompts to upload to the app store. Trying to fix the issue, I've tried every single recommendation I can find on the internet, and nothing seems to fix it. Some examples: updated OS and Xcode to their most recent versions toggled Always Embed Swift Standard Libraries between Yes/No for both project and target tried using the deprecated build system to build etc..

Hi guys, need some help on this issue when I submit my testing app to TestFlight using GitHub Actions and Fastlane, I get this warning from App Store Connect: We noticed one or more issues with a recent delivery for the following app: 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-90725: SDK version issue - This app was built with the iOS 16.2 SDK. Starting April 29, 2024, all iOS and iPadOS apps must be built with the iOS 17 SDK or later, included in Xcode 15 or later, in order to be uploaded to App Store Connect or submitted for distribution. I am using React Native CLI, and Fastlane to run and build my app through Github Actions. After scouring around, from what I understood was that all I needed to do was just to update my Xcode and iOS SDK to the latest, which I did. Currently my Xcode is 15.2 and iOS SDK is on 17 already. However, I still receive this warning w

From appstore receive email with this issues: ITMS-90738: Invalid purpose string value - The “NSPhotoLibraryUsageDescription” value for the NSPhotoLibraryUsageDescription key isn’t allowed in “.....”. Your app’s code references one or more APIs that access sensitive user data, or the app has one or more entitlements that permit such access. The Info.plist file for the “.....” bundle should contain a NSPhotoLibraryUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. ITMS-90738: Invalid purpose string value - The “NSCameraUsageDescription” value for the NSCameraUsageDescription key isn’t allowed in “....”. Your app’s code references one or more APIs that access sensitive user data, or the app has one or more entitlements that permit such access. The Info.plist file for the “.....” bundle should contain a NSCameraUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. I