ITMS-90158

While I'm keen on being on the latest version of macOS, I'm having trouble meeting the requirement that my app can run on a version of macOS that doesn't exist :) I'm using Xcode 15.2 (15C500b), targeting iOS 17.2. I've elected to have the App Store choose the minimum version for Catalyst. I've also tried selecting a version. ITMS-90899: Apple silicon Mac support issue - The app is not compatible with the provided minimum macOS version of 14.2. It can run on macOS 14.4 or later. Please specify an LSMinimumSystemVersion value of 14.4 or later in a new build, or select a compatible version in App Store Connect. For details, visit: ... Is there something I could be doing wrong to prompt this behaviour?

Xcode Cloud succeeds in building the Release configuration of the app, but whenever deployment preparation is set to TestFlight and App Store the last step fails with: ITMS-90035: Invalid Signature. Code failed to satisfy specified code requirement(s). The file at path “{AppName}.app/{AppName}” is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose “Clean All” in Xcode, delete the “build” directory in the Finder, and rebuild your release target. For more information, please consult https://developer.apple.com/support/code-signing. When I build for release (with manual signing) everything work

I have created iOS enterprise app that is not installing using the dropbox url. The app is no longer able to be installed using the itms-services://?action=download-manifest&url=https://dl.dropboxusercontent.com/scl/fi/34j34hj37vl4defedon43hgi/appname.plist?rlkey=bz6sjxhlf349pn7rjk&raw=1. I tried in 2023 year and it worked then. with the URL like - itms-services://?action=download-manifest&url=https://dl.dropboxusercontent.com/s/dz2feq4234h3g4an5/appname.plist . Our Enterprise certificate and provisioning profiles are up to date and valid. I was able to install the app into simulator and iPhone using Xcode. The dropbox links are all shared and accessible to anyone with the link. I can download my IPA file and plist file with no issue if I browse to the URL directly, but it just doesn't work with the itms-services://?action=download-manifest& Does Apple still support OTA installs for enterprise developers? What else can I do to troubleshoot?

Hello, Im currently having signing issues submitting my Swift macOS app to App Store Connect. After submitting it using Xcode I receive an e-mail with these issues: ITMS-90238: Invalid Signature - The main app bundle CodeMenu at path CodeMenu.app has following signing error(s): nested code is modified or invalid . Refer to the Code Signing and Application Sandboxing Guide at http://developer.apple.com/library/mac/#documentation/Security/Conceptual/CodeSigningGuide/AboutCS/AboutCS.html and Technical Note 2206 at https://developer.apple.com/library/mac/technotes/tn2206/_index.html for more information. ITMS-90238: Invalid Signature - The nested app bundle CodeMirror-SwiftUI at path CodeMenu.app/Contents/Frameworks/CodeMirror-SwiftUI.framework has following signing error(s): valid on disk /Volumes/workspace/app_data/SWValidationService/mz_15562079435119469448dir/mz_7860448159412669971dir/id.thedev.marcin.CodeMenu.pkg/Payload/CodeMenu.app/Contents/Frameworks/CodeMirror-SwiftUI.framework/Versions

When I try to submit the app, I get the following error. Is there a way to solve this? Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'UIRequiresFullScreen' in 'Payload/MyApp.iOS.app/MyApp.iOS' is not supported. Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'CFBundleDisplayName' in 'Payload/MyApp.iOS.app/MyApp.iOS' is not supported. Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'UIMainStoryboardFile' in 'Payload/MyApp.iOS.app/MyApp.iOS' is not supported. Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that

Hi, I am receiving the above error after trying to upload it to the App Store. I would know what to do IF Xcode would provide WHICH file is corrupt. The error reads: ITMS-90013: Corrupt Image File - The image file $[IconName] appears to be corrupt. Again, I would know what to do if I had more information about which file(s) to fix. Could anyone FROM APPLE help me or give me a hint? Thanks, Dan Uff

Hi, I am receiving the above error after trying to upload it to the App Store. I would know what to do IF Xcode would provide WHICH file is corrupt. The error reads: ITMS-90013: Corrupt Image File - The image file $[IconName] appears to be corrupt. Again, I would know what to do if I had more information about which file(s) to fix. Could anyone FROM APPLE help me or give me a hint? Thanks, Dan Uff

I have an app that is getting rejected from TestFlight because of this error: ITMS-90683: Missing purpose string in Info.plist - 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 “TurtleTuner.app” bundle should contain a NSCameraUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. If you’re using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. For details, visit: https://developer.apple.com/documentation/uikit/protecting_the_user_s_privacy/requesting_access_to_protected_resources. The app does not use the camera, only the microphone. I cannot find references to the camera in any of the third party libraries I'm using. What are some ways to troubleshoot this beyond looking for camera in the few dependencies? F

When I try to submit the app, I get the following error. Is there a way to solve this? Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'UIRequiresFullScreen' in 'Payload/MyApp.iOS.app/MyApp.iOS' is not supported. Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'CFBundleDisplayName' in 'Payload/MyApp.iOS.app/MyApp.iOS' is not supported. Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'UIMainStoryboardFile' in 'Payload/MyApp.iOS.app/MyApp.iOS' is not supported. Asset validation failed (90045) Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that

As I don't own an Apple Watch, I'm distributing this via an Ad Hoc URL for testing purposes with a few friends. However, no-one has been able to install the app over the air. The files (manifest, ipa, images, etc) are all hosted over HTTPS with valid certs. Emails include a link with itms-services://?action=download-manifest&... etc The user is presented with a Install prompt. I can see 200 OK network requests for the manifest, ipa, and image files. However, even though the ipa is downloaded correctly, the app fails to appear on the watch. Any ideas? or how can I debug on an actual device? I cannot use TestFlight, as the AppStore requires me to film a video of me using the app on an actual real watch (this is a bizarre requirement???)

I have an iPad app on the App Store, and since recently every time I upload a new build to App Store Connect I receive an automated email with the following warning. ITMS-90984: Apple Vision Pro support issue - The details associated with your Apple Developer Program membership indicate that you’re not eligible to publish apps on the App Store for Apple Vision Pro. For more information, contact us: https://developer.apple.com/contact. At the present, my app does not target visionOS API specifically, but I have checked the checkbox for availability on Apple Vision Pro. According to the warning, something makes me not able to distribute apps for Vision Pro, but lacking any details I am not sure how I can solve this issue. What specifically about my account makes me ineligible to distribute apps for Apple Vision Pro and triggers this warning? I have contacted support at the provided URL, but they were unable to help me and redirected me to post in Developer Forums.

I have seen several posts around the internet from years past with complains of such a problem, the review is rejected with : ITMS-90111: Invalid Toolchain - Your app was built with a beta version of Xcode or SDK. Apps submitted to the App Store must be built with the GM version of Xcode 10.1 and the SDK for iOS 12.1 and watchOS 5.1, Xcode 7.1 and the SDK for tvOS 9, or Xcode 6 and the SDK for macOS 10.9 or later. If you are using an Xcode beta version to test your app, make sure you are using the latest supported version. My XCode is 14.1 and I am using github Continuous integration to build it. Any hint on how can I track what is wrong? Each and every post I found on the subject ended either without any answer or just saying to wait for apple to fix it.