409 ENTITY_ERROR.RELATIONSHIP.INVALID — Cannot attach build or create version, affecting 2 separate accounts for 1 week

App Store Distribution & Marketing App Store Connect
natselayron OP
Created 3w
Replies 8
Boosts 2
Views 412
Participants 5

I am unable to submit any app for review. Every attempt to add a build to an App Store version results in a 409 error, both through the App Store Connect website and directly through the App Store Connect REST API.

Affected accounts:

Account 1: My personal Apple Developer account Account 2: A company-owned Apple Developer account where I have Admin access Both accounts are completely separate — different legal entities, different enrollments — but exhibit the exact same behavior simultaneously.

API errors observed

When calling PATCH /v1/appStoreVersions/{id}/relationships/build:

409 ENTITY_ERROR.RELATIONSHIP.INVALID "The specified pre-release build could not be added." When calling POST /v1/appStoreVersions to create a new version:

409 ENTITY_ERROR.RELATIONSHIP.INVALID "You cannot create a new version of the App in the current state."

What I have verified

All builds are processingState: VALID and not expired usesNonExemptEncryption: false is set on all builds No build is already attached to another version Build version string matches the App Store version (1.1.0) App bundle ID matches the build bundle ID Localization, review contact details, and keywords are all filled in Banking info in Agreements, Tax, and Banking was recently updated on both accounts Issue persists on both the website and via the REST API, ruling out a browser/cache issue

Question

Has anyone seen 409 errors affecting two completely separate developer accounts simultaneously? Could there be a platform-level issue with App Store Connect that is not reflected on the System Status page?

I opened a support ticket 1 week ago but I only got a reply today and it's just asking for more details.

Replies  8
Boosts  2
Views  412
Participants  5
marianakodama OP
3w

I have the same issue

2
amerluzz OP
2w

Did you ever get a more detailed response to this? I am also having the same issue.

0
natselayron OP
2w

Are there no people from Apple support in this Forums? I even renewed my developer account to submit apps but can't do so because of this bug.

1
DaDalus OP
2w

same issue

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

1
App Store Connect Engineer OP
Apple
2w

Hi there, thank you reporting this issue. Can you please post your ticket number here so we can take a look?

1
App Store Connect Engineer OP
Apple
2w

Hi there, thank you all for the reports! Can you please verify that the builds you're attempting to attach to your version aren't internal only builds. Internal only builds can't be attached to app versions.

https://developer.apple.com/help/app-store-connect/manage-builds/choose-a-build-to-submit/

https://developer.apple.com/documentation/xcode/distributing-your-app-for-beta-testing-and-releases

0
DaDalus OP
1w

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

1
App Store Connect Engineer OP
Apple
1w

Awesome, glad it worked! Thank you for that feedback. We are tracking an enhancement to this so it's clearer.

Thanks again.

0
409 ENTITY_ERROR.RELATIONSHIP.INVALID — Cannot attach build or create version, affecting 2 separate accounts for 1 week
First post date Last post date
 
 
Q