Hi App Store Connect Engineer, Thanks for the help! You were right — once I changed my Xcode Cloud workflow so it wasn't internal-only, the build attached to 1.0.4 on the first try and the version is now waiting for review. Two things I wanted to share while I'm here: The error I was getting really didn't help me figure out what was wrong. It just said something like "invalid relationship" with no real details. I spent a few days thinking the version record itself was somehow broken before I realized it was actually about the build's audience type. Even a short hint like "this build can't be attached because it's internal-only" would have saved a lot of time. It would also be great if this was visible somewhere in App Store Connect — right now you can only see it through the API. The other thing is the support ticket. I opened Case #102865399563 on April 10 — the auto-reply said someone would get back within 2 business days. As of today that's 13 business days, with two follow-ups from me, and still no response. I get that things get busy, but for something that's blocking a release, even an automated update with a rough estimate would help a lot. Right now the silence is hard to plan around. Anyway, thanks again for the reply. Best, DaDalus

same issue waited very long about 12 days and not yet been acknowledged in the support ticket.