Already Enrolled, but Now Asked to Re-Enroll – Certificates Revoked, No Response

Our company enrolled in the Apple Developer Program as an organization in July 2024. Everything was fine for several months, but in early January 2025, our developer noticed that the certificates were missing. When we logged into our developer account, we were shocked to see a page prompting us to “Enroll Today”—as if we had never joined in the first place.

Clicking the enrollment button led us to an error page stating we cannot enroll.

We immediately reached out to Apple Developer Support via email, but despite multiple attempts, we received no response. Strangely, our apps remain live on the App Store, App Store Connect functions as usual, and we continue receiving payments every month. However, we are completely blocked from developing and releasing updates.

Today, I managed to reach Apple by phone. After being transferred to a senior representative, I was told they couldn’t tell me why this was happening. They only confirmed that a request had been made and that I should “wait.” That’s it—no explanation, no timeline, nothing. While it’s somewhat reassuring that they acknowledge the issue, I’ve already seen other developers with the same problem go unanswered for months.

My suspicion? This account might be linked to an individual developer account from way back in 2015 when Apple’s registration process was far less strict. Could that be the issue? No idea—because Apple won’t say a word.

Meanwhile, both of our apps have been exposed to several bugs, and customers are waiting for updates. If there’s still no response from Apple, I have no choice but to register a new account—purely to continue supporting our users.

CASE ID: 102508598957

"Your Apple Account is already associated with the Account Holder of a membership."

I’ve sent several emails to some key contacts; hopefully, that helps. It frustrates me that Apple’s support doesn’t respond to developers, almost as if we’re their enemies.

I found the reasons.

I experienced conflicting Team IDs (63J9U6XXXX and C69G7WXXXX) that blocked access to certificates and profiles for my active organizational account. The inactive C69G7WXXXX Team ID caused errors in Apple’s developer portal, while my valid organizational Team ID (63J9U6XXXX) remained inaccessible for resource management.

Root Cause This conflict originated from two key factors: 1. Legacy Individual Membership: I likely enrolled in a pre-2019 individual Apple Developer Program, which created the deprecated C69G7WXXXX Team ID. Apple’s 2019 system overhaul orphaned such accounts but retained their visibility. 2. Post-2019 Organizational Account: My current organizational membership (63J9U6XXXX) operates under Apple’s modern framework, but residual permissions from the old individual account caused system conflicts.

Technical Impact • Certificate Errors: Development tools rejected the legacy Team ID, preventing app updates. • Portal Mismatches: Apple’s interface displayed the inactive C69G7WXXXX ID when accessing certificates, despite my active organizational membership. • Permission Conflicts: My Apple ID retained ties to both teams, creating credential mismatches.

Already Enrolled, but Now Asked to Re-Enroll – Certificates Revoked, No Response
 
 
Q