“ITMS-90158”

We have two targets.MCOM and MCOM QA and both are built using iOS 12 SDK.But when we submit the MCOM build to Test Flight, we get following message.We identified one or more issues with a recent delivery for your app, Macy's 8.4.2 (8042.200501.150315). Your delivery was successful, but you may wish to correct the following issues in your next delivery:ITMS-90725: SDK Version Issue - This app update was built with the iOS 12.4 SDK. As of June 30, 2020, updates to apps for iPhone or iPad must be built with the iOS 13 SDK or later.But when we try to upload MCOM QA build to Test Flight, we get different messageERROR ITMS-90725: SDK Version Issue. This app was built with the iOS 12.4 SDK. New apps for iPhone or iPad must be built with the iOS 13 SDK or later. Return status of iTunes Transporter was 1: ERROR ITMS-90725: SDK Version Issue. This app was built with the iOS 12.4 SDK. New apps for iPhone or iPad must be built with the iOS 13 SDK or later.So basically Test Flights assumes our QA apps as

Hello,We contacted Apple Developer Support due to an automatic message we receive when trying to publish a new version of our appDear Developer, We identified one or more issues with a recent delivery for your app. Please correct the following issues, then upload again. ITMS-90338: Non-public API usage - The app references non-public selectors in Idealys: applicationWillTerminate, ddSetLogLevel:, localTarget, newSocketQueueForConnectionFromAddress:onSocket:, setOrientation:animated:, socket:didConnectToHost:port:, socket:didReadPartialDataOfLength:tag:, socket:didReceiveTrust:completionHandler:, socket:didWritePartialDataOfLength:tag:, socket:shouldTimeoutReadWithTag:elapsed:bytesDone:, socket:shouldTimeoutWriteWithTag:elapsed:bytesDone:, socketDidCloseReadStream:, socketDidSecure:, terminateWithSuccess, webSocket:didReceiveMessage:, webSocketDidOpen: If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged

I'm trying to submit an app to the store that contains a bundle of `.mlmodel` files.When I archive the app and upload it to the app store I get a list of errors, one for each `.mlmodel` file that is in the bundle.An example of such an error is:Invalid Bundle Structure - The binary file 'MyApp.app/Frameworks/MyFramework.framework/AIModels.bundle/bot2emb51.o' is not permitted. Your app can’t contain standalone executables or libraries, other than a valid CFBundleExecutable of supported bundles. Refer to the Bundle Programming Guide at https://developer.apple.com/go/?id=bundle-structure for information on the iOS app bundle structure.In this particular case I have a file that's marked for inclusion in the `AIModels` bundle called `bot2emb51.mlmodel`. I'm not sure why the file is being compiled into an object file, I thought it would be copied as an `mlmodel` file.Are there any Xcode settings I need to change, or flags that I can set in the compiled to work around this?

Hi EveryoneI got this warning from Apple:SDK Version Issue - This app was built with the iOS 12.0 SDK. Starting March 2019, all iOS apps submitted to the App Store must be built with the iOS 12.1 SDK or later, included in Xcode 10.1 or later. After you’ve corrected the issues, you can use Xcode or Application Loader to upload a new binary to iTunes Connect.I updated my xcode to the latest 10.1 version and my Application Loader is Version 3.7.2. I developed a new build after updating but I am still getting the SDK Version Issue. Is anybody else having this problem and do you know how to resolve it?Kind RegardsDaniella

Hello, I'm getting the title's error for the first time. I'm using expo for my React Native build and I have only added these libraries to my build: react-native-md5: ^1.0.0, moment-timezone: ^0.5.43 How are these changes connected to the error? These are my system specs: XCode version 14.2 (14C18) MacOS version 12.6.7 (21G651)

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

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