All seem to be good until that final step of the "Archiving" step. Intending to send it to TestFlight as the Post-Action. After all success it failed with this:
It keeps failing regardless of how many times I run the build.
XCode Cloud is failing with "Failed to prepare build for App Store Connect"
Can you please open a bug report about this, and include the log files, as well as the build link in Xcode Cloud? Once you've done so, please post the FB number here so I can cross-reference it.
FB9751401 sir...
I see the same issues with my Xcode Cloud build. The generated XCArchive can be imported locally and then uploaded with Transporter or Xcode to AppStore Connect without any errors. Additionally to fixing the issue, more log output for the code signing and deployment steps would be really nice.
Thanks in advance.
Sascha
I saw the same exact error message when I was starting to use XCode Cloud this weekend to do testflight builds for an app that was already being distributed via testflight. When the XCode Cloud creates builds, it starts off with build #1, but I had already done builds 1 through 5 in testflight. I'm glad it was a relatively new app because when I finally got up to build 6 in XCode Cloud, testflight started accepting my builds.
I wrote up a bug/suggestion to ask Apple to allow us to start off the builds at some number other than 1 so that XCode Cloud would be compatible with apps that were already being used with Testflight.
It's entirely possible that your issue was caused by something completely different, but I wanted to let you know of this one possible cause of the issue.
Thanks a lot Brian,
interestingly I did not find that in the documentation, but for me the issue can be closed. I did set my current build number from the latest build released in TestFlight increasing it by 1 in the Xcode cloud build settings and voilà my build passed and deployed successfully.
Thanks 🙏🏽
Same exact issue here -- everything succeeded but was getting that error message at the end. I can confirm it was indeed the build number mismatch. Our app had 6 existing Testflight builds when we started using Xcode Cloud, e.g. "1.0.0 (6)". The workflow finally succeeded on the 7th run. As @smuellner found, it automatically sets the build number equal to the workflow run number.
Why does it ignore the build number that I set in Xcode (CURRENT_PROJECT_VERSION)? That's silly that it ignore that and uses its own incremental build number as the actual build number. Apple should fix this.