But this one doesn't specify where the problem is, such as the use of a private api or if it's using a key that shouldn't be used, or anything else. Now we need to find out what's causing this problem, can you give us some direction or ideas?
ITMS-90714: Invalid binary - The app contains one or more corrupted binaries. Please rebuild the app and resubmit.“
Do any of your targets or Xcode projects declare extra linker flags in the Other Linker Flag build setting? An example might be -Xlinker -interposable. If so, I’d love for you to remove those flags (regardless of what they are), and try the build upload to see if that makes a difference.
— Ed Ford, DTS Engineer
I think it may be related to IPHONEOS-DEPLOYMENT_TARGET
What's in your Xcode build log? For example, consider this message from an example build log:
Build target MyTarget of project MyProject with configuration Release
MyProject.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 5.0, but the range of supported deployment target versions is 12.0 to 17.0.99. (in target 'MyTarget' from project 'MyProject')
This warning from Xcode indicates that the target's deployment target is way out of date, and that the version of Xcode 15 that compiled this target no longer supports deployment targets less than iOS 12.
Don't get too hung up on the exact set of version numbers in this example, but if you're getting a message like that, then you really need to resolve that warning and upgrade your project to use a deployment target that is within the range supported by the current Xcode version. This goes hand-in-hand with best practice advice of always resolving every build warning — if you're getting the above warning, you're also likely receiving many other warnings that you should be researching and addressing as well to maintain your overall project health.
—Ed Ford, DTS Engineer