In our case we only had one of the issues mentioned in the original post: Invalid Bundle. The bundle {MyAppName}.app/Frameworks/{FrameworkName}.framework does not support the minimum OS Version specified in the Info.plist.. The framework in question is an Kotlin Multiplatform library (which we fortunately have in our own hands). The previous way to specify the minimum iOS/tvOS versions was like this: targetPlatforms { iOS { v("16") } tvOS { v("16") } } That no longer seems to be sufficient. Now we had to add Kotlin Native Compiler arguments like this: targets.withType<org.jetbrains.kotlin.gradle.plugin.mpp.KotlinNativeTarget> { compilations["main"].compilerOptions.options.freeCompilerArgs.addAll( "-Xsome", "-Xother", "-Xarguments", "-Xoverride-konan-properties=osVersionMin.ios_arm64=16.0;osVersionMin.ios_simulator_arm64=16.0;osVersionMin.tvos_arm64=16.0;osVersionMin.tvos_simulator_arm64=16.0" // <-- Specify versions here ) } That fixed the Xcode Cloud build for us. (Funnily enough, this never was a problem with local Xcode 15.3 builds)

As I wrote in my comment, we ran into the same problem. After looking in the more detailed logs which are provided in AppstoreConnect/XCodeCloud, especially XYZBuild123/app-store-export-archive-logs/xcodebuil-export-archive.log (download "XCResult for..." from Build 123 -> Artefacts), we found that it said: error: exportArchive: Provisioning profile "iOS Team Store Provisioning Profile: xxxxxxxx" doesn't include the com.apple.smoot.subscriptionservice entitlement. We need this entitlement and included it in our provisioning profiles. But it seems that Xcode doesn't use our own profiles, but a team profile created during build. After deleting entitlement entries from the configurations and (just to be sure) deleting the .entitlements files completely the build ran. However this is no solution, because we need those entitlement entries if we want to distribute our app, but at least we seem to have found the bug.

Same here. In my case it's 6 (nearly) identical error message, two of which always report exactly the same error and this happens three times, one time for each configuration I use for different purposes (development/adhoc/appstore). The fact, that there are errors for development and adhoc as well, is actually also confusing, because the scheme I use for the only action within the workflow is for AppStore/TestFlight and by that, the workflow shouldn't know about development and adhoc at all. And one more thing: We have another similar project, which has different code, but nearly the same setup in matters of distribution/configurations/schemes/profiles which works fine. The difference between these two is, that the non-working one has two targets/artefacts, while its sister has only one (but the not-running workflow is setup to only produces one of the artefacts, of course).