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 🙏🏽

Hi, I do set the build number based on a git pre-commit hook for every commit. Using tools like autohook you should be quite fast in fitting this to your own processes. As an example the script I use: #!/usr/bin/env bash git=$(which git) PlistBuddy="/usr/libexec/PlistBuddy" REPO_ROOT_PATH=$("$git" rev-parse --show-toplevel) GIT_BRANCH_NAME=$("$git" -C "$REPO_ROOT_PATH" branch --show-current) GIT_HASH=$("$git" -C "$REPO_ROOT_PATH" show -s --format=%H) GIT_NUMBER_OF_COMMITS=$("$git" -C "$REPO_ROOT_PATH" rev-list HEAD --count) GIT_RELEASE_VERSION=$("$git" -C "$REPO_ROOT_PATH" describe --tags --always --abbrev=0) IOS_PLIST_PATH="$REPO_ROOT_PATH/iOS/Info.plist" MACOS_PLIST_PATH="$REPO_ROOT_PATH/macOS/Info.plist" TVOS_PLIST_PATH="$REPO_ROOT_PATH/tvOS/Info.plist" echo "GIT: $git" echo "NUMBER_OF_COMMITS: $GIT_NUMBER_OF_COMMITS" echo "RELEASE_VERSION: $GIT_RELEASE_VERSION" for plist in "$IOS_PLIST_PATH" "$MACOS_PLIST_PATH" "$TVOS_PLIST_PATH"; do   if [ -f "$plist" ]; then     echo "PATCH: $plist"     "$PlistBuddy" -c "Set :CFBundleVersion $GIT_NUMBER_OF_COMMITS" "$plist"     "$PlistBuddy" -c "Set :GitBranchName $GIT_BRANCH_NAME" "$plist"     "$PlistBuddy" -c "Set :GitHash $GIT_HASH" "$plist"     "$git" add "$plist"   fi done Kind regards, Sascha

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