I thought that if xcode cloud workflow fails on stage "Preparing build for App Store Connect failed" then build is not uploaded at all. But turns out that app store connect has all the details about the error for each such failed build in TestFlight builds section. So just go and check in App Store Connect, when you see this mysterious ibtool crash in xcode cloud.

We had one dynamic xcode target framework embedded both into app target and widget target. When I removed embedding from widget, ibtool stopped crashing for some reason.

We also have a similar repeated issue. Everything is archiving in xcode cloud but then on step "Preparing build for App Store Connect failed" action fails and in logs there is ibtool crash ExcUserFault_ibtoold-2025-10-16-082310.ips. The feedback request number is FB20699169

Open manifest and save it.

Deleted

I would add my 2 cents to that article: If you distribute builds via Xcode Cloud be aware that different artefacts use different aps-environments: Ad-Hoc and Appstore: Production Development: Development (aka Sandbox) You can check aps-environment for artefact from xcode cloud build by inspecting aps-environment key inside DistributionSummary.plist located next to .ipa. It's also possible to get this value in runtime like FirebaseSDK does (see SO research) (Using embedded.provisionprofile or embedded.mobileprovision)

Please update this documentation because it mentions that profile. https://developer.apple.com/documentation/foundation/url_loading_system/downloading_files_in_the_background (My previous post has wrong link)

Please update this documentation because it mentions that profile. https://developer.apple.com/documentation/foundation/urlsessionconfiguration/1411552-isdiscretionary