We hit the same issue today (Xcode 26.6, Build 17F113), with one difference from the original report: our app variants are build configurations of a single target, not separate targets. Each configuration sets its own PRODUCT_BUNDLE_IDENTIFIER via xcconfig and has its own shared scheme. Setup: one Xcode project, three App Store Connect apps with distinct bundle IDs. Two of them were already onboarded as separate Xcode Cloud products, each with working TestFlight workflows. Steps: Launched Xcode fresh. Selected the new variant's scheme (Product > Scheme). Integrate > Create Workflow, then saved. Result: no new product was created. The new workflow was added to the existing product of a different variant, and that product's "View app" now points to the newly onboarded app. Its earlier TestFlight workflow now sits under the wrong app. The third product was not affected. Restarting Xcode beforehand (the suggested workaround) did not help in our case. Xcode had just been launched, although other windows of the same Xcode process had other checkouts of the same repository open. Since ciProducts cannot be created or re-linked through the App Store Connect API, we have no way to restore the original product-to-app relationship ourselves. Is there a supported way to fix this server-side, or a reliable onboarding procedure for a second bundle ID from a single target? Filed as FB25029029.