Post not yet marked as solved
I've been trying to upload a test build using Xcode 13 to TestFlight but keep getting the following error after build is uploaded successfully:
ITMS-90755: Invalid Binary - The following binaries in your app contains prohibited instructions: /Volumes/data01/app_data/awf/SWImportWorker-pv50p00ce-swpr152.cse.apple.com-400203/ff08-SoftwareImportWorker-PV_.0/VWBGHTOVAUPPUUZ65REE64UUN4/eqbyjijjamvooymq/exddmvmbsqjsrxwj/Payload/[App Name].app/[App Name]. Remove the instructions from the binaries, rebuild and resubmit.
What does this error mean? What are those prohibited instructions? Where to fine them in the app binary?
Any guidance is appreciated.
Thanks.
We're having some strange issue with our app and/or Testflight since a few days ago: our app runs fine on simulator and devices (iOS 12, iOS 14 & iOS 15) when run from Xcode, but it crashed at launch when we archive and distribute it via Testflight for iOS 14 and below, but NOT for iOS 15 (we haven't tried to actually release to the AppStore). The app was working perfectly fine on iOS 12+ until then, on Testflight or otherwise. No crash log is ever generated by these crashes (either on Crashlytics, or Organizer, or even in the device crash logs), and what's more mysterious is that when re-archiving past versions of the code that had no issues 3 weeks ago and are live on the app store, we are now getting the crashes. We've dug into the device logs to try and get some more info, and we could find
com.apple.stability.crash {"appVersion":"3.3.1","bundleID":"com.cobble.ios","exceptionCodes":"0x0000000000000000, 0x0000000000000000","incidentID":"B47DF725-343B-4D8E-A1C4-8F52EB5766C1","logwritten":1,"process":"Cobble Production","terminationReasonExceptionCode":"0x1","terminationReasonNamespace":"DYLD"}
for iOS 14, and
Process exited: <FBApplicationProcess: 0x10a2dd110; Cobble Producti (com.cobble.ios); pid: -1> -> <FBApplicationProcessExitContext: 0x28331a100; exitReason: (none); terminationReason: (none)> {
stateAtExit = <FBProcessState: 0x283cd8cc0; pid: 4156; taskState: Not Running; visibility: Unknown>;
}
for iOS 12.
We haven't had any luck so far figuring out what the issue(s) can be, but we've tried a lot of things from building on different computers, playing around in the build settings, updating our pods, to fully uninstalling/reinstalling Xcode and the project from Github..
It might be worth noting that we're using automatic signing from Xcode (changing that is our next test)
Any help would be greatly appreciated!!
We've also posted this question on StackOverflow (https://stackoverflow.com/questions/70316323/ios-app-crashes-at-launch-on-testflight-for-ios-14-and-below-but-not-ios-15)
Post marked as Apple Recommended
Hi,
I created an application for a client.
The client put me as a developer in his team on AppStore Connect. For that I use Xcode 13.2.1. It's a UIKit application in Swift with Storyboards.
I built the app => no problem
I tested it on my iPhone => no problem
From Xcode I made an archive and uploaded it to TestFlight => no problem
The archive has been received by Apple. It was then processed by Apple => no problem
And finally I received a notification that it was available on TestFlight => no problem
TestFlight offers me to install it but when I try it does not install it. If I try to click on the icon of the application it shows me the message
"This app cannot be installed because its integrity could not be verified."
I have tried installing other apps from TestFlight and have no issues.
I checked on my mac for the various certificates for this client and they are all good and valid.
I don't understand why for this application I have this behavior.
Someone would have any idea ?
Regards
Tof
Post not yet marked as solved
Receiving this error when trying to upload the app to Testflight. I've been able to successfully upload a few days ago, but it just started happening.
Post not yet marked as solved
Hi. I’m developing an application for a client and I’m in his team in the AppStore.
Since October 5, 2022, we have encountered such a problem in TestFlight, for all versions of applications the testing period has expired, although some were uploaded only that day. On October 6, I uploaded a new build of the application to TestFlight in hope that the whole will be available for downloading. But that did not happen. It is visible in TestFlight and it has not expired for testing, but when I try to download it on a mobile device through the TestFlight application, I get error that “Could not install App - The request app is not available or doesn’t exist”.
Is there a solution to this problem?
Post not yet marked as solved
Getting issue in. uploading build from Xcode 14.1. My OS is Ventura 13.0.
I am getting following error wile uploading app.
Metadata/Info.plist Mismatch. The value for bundle_version in the metadata.xml file does not match the value for CFBundleVersion in Corey Health [Payload/Corey.app]. (ID: 9726552c-a8a0-4e23-aec7-a5e20ac2ce1f).
Please help
Post not yet marked as solved
Initially I removed the macOS support for my iPhone app. Now I want to enable it, so I enabled macOS Designed for iPad in Xcode, and also enabled macOS in App Store Connect for the app.
In TestFlight on macOS it shows "Requires macOS and a Mac with Apple Silicon chip" but still lists it under IOS only Apps. (My Mac is Mac Book Air M1, macOS 13.1).
I have another simple app which I created and it works just fine and I can't find any difference in the build setup between the two.
I have verified the App works well with Mac (Designed for iPad) simulator so the App do work on macOS that much is certain.
So my question is how can I enable macOS for an IOS app that previously was only built for iPhone/iPad. Either I'm missing a step or there is a bug lurking here.
As it is now I am not able to install the app on macOS from TestFlight.
Thanks,
Marcus
Post not yet marked as solved
Hello, we are having this response when submitting our application, but in the return email from the Apple Store Connect it does not show what would be the point to correct.
Is anyone else having this too? any idea what to do?
Thanks in advance..
Dear 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 contains one or more corrupted binaries. Rebuild the app and resubmit.. 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 in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/
Best regards,
The App Store Team
Hi,
Since yesterday (May 11, 2023) I can no longer send an update on TestFlight for the Apple Developer account of a client on which I am admin. It gives me the following error:
The last time I sent a version to TestFlight was May 4, 2023 and I had no problem.
With other client applications I have no problem sending my updates to TestFlight.
I have no problem connecting to Apple Connect with my Apple ID, I can see that I am an admin on the Apple Developer account.
My config:
macOS 13.3.1 (a)
Xcode Version 14.3 (14E222b)
Regards
Tof
Post not yet marked as solved
When I tried to upload the app previously its was working fine I uploaded around 17 builds to testflight but recently we converted to Organization account and I was assigned the admin role and since then I am unable to upload.
I have tried removing and adding the app store id. I ahve also tried changing name and bundle identifier.
Xcode version 14.2
Post not yet marked as solved
I tried to upload a version of my app through XCode 15. All the process went well, but when the app reaches the test flight app on my iPhone 13 mini with iOS 16.5, it downloads the packet but then it goes back to the "Update" button. Seems that it doesn't like the package.
Am I the only one with this issue?
Post not yet marked as solved
Hello everyone! There was a problem with Test Flight , the application is sent to Test Flight, and when installed by testers on different iphones, it does not launch. At the same time, the project is built in Visual Studio 2022 without errors and successfully works on devices and simulators (debug and release mode). It was noticed that builds released before 22.06 work successfully on devices, all further builds stopped working.
What could be the problem?
Visual Studio 2022 version 17.6
Xcode version 14.3.1
macOS Ventura 13.4.1
Xamarin.iOS version 16.4.0.6 Visual Studio Community
Post not yet marked as solved
Hi everyone
I 'm trying to distribute my app with Testflight. When trying to submit a new build, I get the following errors:
I 'm using Xcode 15 beta 2.
Can anyone help me?
Xcode: Version 15.0 beta 2 (15A5161b)
iPhone: iOS 17.0 (21A5268h)
Run from Xcode to Simulator or my iPhone, build successfully, install failed with the same error:
My widget extension target info.plist file looks like the image below, and it worked find with all the previous Xcode version.
After adding the key NSExtensionPrincipalClass like this:
I can install my app to simaltor and my device, however, when archive and upload to the App Store (for TestFlight testing), i got another error (the first one is related to this issue, the second i could not figure out what it is):
Post not yet marked as solved
We are facing the below mentioned error frequently while submitting the different apps in the App Store. When we are uploading the first build, we are receiving the below mentioned error and if we increment the build version, and on re submitting we are not facing the same issue again. Could you please guide us on what caused this issue?
Xcode Version: 14.2
Error : ITMS-90338: Non-public API usage - The app contains one or more corrupted binaries. Rebuild the app and resubmit.. 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 in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed.
Post not yet marked as solved
The swiftui codes and designs I wrote in the Xcode simulator work flawlessly and the design is as I want, but in testFlight the terrible design and notification settings do not work as I want.
why ???
We have recently released an app on TestFlight, and TestFlight includes a useful feature for automatically capturing crash reports. Whenever a user encounters a crash, TestFlight usually displays a dialogue prompting them to share the crash details with the developer or Apple portal. However, one of our users reported that they did not receive this dialogue, despite having the "Share iPhone & Watch Analytics" option enabled. As a result, we are unable to access the crash logs for further investigation.
It seems that no other users are currently experiencing the crash, or they may not be encountering the specific circumstances that prevent the crash dialogue from appearing. Moreover he tried to find that crash log .ips file in "Analytics Data" but its not visible.
Post not yet marked as solved
I started building a new app with Xcode 15, and I uploaded a few builds to TestFlight with it. Now I'm trying with 15b4, and I'm getting:
Invalid Toolchain. Your app was built with an unsupported SDK or version of Xcode. If you plan to submit this build to the App Store, make sure you are using the versions listed in https://help.apple.com/xcode/mac/current/#/devf16aefe3b or later. (ID: 0c544ce8-53ee-4122-b4a9-467a3d766349)
Is this a bug? They've always allowed TestFlight builds with pre-release toolchans, havn't they? How else can you ensure your app is ready for the new OS version if you can't test changes to it?
Post not yet marked as solved
Even when I export IPA file from exactly the same archive that is uploaded to TestFlight, with or without thinning, it behaves a bit differently.
Specifically, the exception with 0xdead10cc exit code ("dead lock") that happens in TestFlight and App Store versions, never happens with IPA version.
Post not yet marked as solved
I got this error when I try to push my app into testflight: Unsupported Xcode or SDK Version. Your app was built with a version of Xcode or SDK that is not yet supported for upload to App Store Connect.
