ITMS-90158

I've got my Mac app through packaging, archiving, and export, in to the Application Loader. I've ended up using Application Loader because Xcode is only giving me unhelpful iTunes Store operation failed / try again messages. However I'm running in to a roadblock, which manifests as this error message:ERROR ITMS-90135: The executable could not be re-signed for submission to the App Store. The app may have been built or signed with non-compliant or pre-release tools.This is spewed out again and again in the Application Loader log - across every submission attempt I've tried, that message appears 73 times per attempt.My Mac app has a whole bunch of auxiliary executables in its Resources folder, which are invoked with NSTask to do work. There are far more than 73 executables so I don't know if that number is significant or not.There really is no other accompanying information that I can see - this single log line is all it's giving me. So there seems no way to start debugging which of the executables are

Hey, I’m updating all of my apps to target the new versions of all the plugins we use, and for some reason, I have a warning message : ITMS-91053: Missing API declaration - Your app’s code in the “*****” file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryDiskSpace. ... ITMS-91053: Missing API declaration - Your app’s code in the “*****” file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryFileTimestamp. ... Apple Developer Relations But in my Cordova config.xml, I have already added the tag: NSPrivacyTracking NSPrivacyCollectedDataTypes NSPrivacyTrackingDomains NSPrivacyAccessedAPITypes NSPrivacyAccessedAPIType NSPrivacyAccessedAPICategoryDiskSpace NSPrivacyAccessedAPITypeReasons E174.1 NSPrivacyAccessedAPIType NSPrivacyAccessedAPICategoryFileTimestamp NSPrivacyAccessedAPITypeReasons 3B52.1 I have already sent some applications to Apple

I've notarised my app and wrapped it up as a .pkg (I think) correctly. But every time I try and submit my app to the Mac AppStore, apple sends me back this email which I cannot decipher. My certificate should be good, I use the check-signature tool to check both the .pkg and the .app files. It passes Notarisation, which I know is performing similar checks. I'm not sure if there error message it is emailing me is saying the dylib files are the problem or that they have been validated? ITMS-90238: Invalid Signature - The main app bundle APP_NAME at path app_name.app has following signing error(s): -prepared:/Volumes/data01/app_data/app-processing/mz_621478465736756725dir/mz_11614935509311203053dir/com.company.app_name.pkg/Payload/app_name.app/Contents/Frameworks/libMonoPosixHelper.dylib -validated:/Volumes/data01/app_data/app-processing/mz_621478465736756725dir/mz_11614935509311203053dir/com.company.app_name.pkg/Payload/app_name.app/Contents/Frameworks/libMonoPosixHelper.dylib -prepared:/Volumes/data01

Hi, When packaging an application using JDK 17 and the latest version of jpackage I get the below error when uploading to the App Store. All test prior to uploading complete just fine. I think it might be realated to the structure of the .app folder but not sure, any ideas would be helpful ITMS-90238: Invalid Signature - The main app bundle Test at path Test.app has following signing error(s): a sealed resource is missing or invalid. Refer to the Code Signing ... and ITMS-90296: App sandbox not enabled - The following executables must include the 'com.apple.security.app-sandbox' entitlement with a Boolean value of true in the entitlements property list: [[Test.app/Contents/MacOS/Test]] The app verifies in Transporter just fine and codesign as well. codesign --verify --verbose=4 'Test.app' Test.app: valid on disk Test.app: satisfies its Designated Requirement Also entitlements seems to be fine. codesign -d --entitlements :- ./Test.app/Contents/MacOS/Test Executable=/Users/ryan/flat/Test.app/C

We have several Mac Catalyst apps that use UIPrintInfo and UIPrintInteractionController to support printing. Both of these classes are marked as available on Mac Catalyst 13.1 in the documentation and we do not receive any errors or warnings using them in our app. We have successfully uploaded to App Store Connect recently with apps that use those classes, but now are receiving error messages from App Store Connect complaining that the use of these classes is non-public API and receive the ITMS-90338 error, even though no code has changed. Is this an issue on the validation side, or are these classes no longer supported on Mac Catalyst? Thanks in advance for any help!