Xcode Cloud export fails with exit code 70: "Developer ID Application Managed" certificate exists but Xcode Cloud reports no cert/private key found

I recently saw an Xcode Cloud thread [edit: fixed the URL] that looks very like this one.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Hey Quinn-

I also saw a thread with an issue similar to this, but am looking for confirmation from DTS about the steps to take, and that this will not break currently signed and shipped versions of the app.

Cheers!

Same failure here, Team 4G35KLFD64, macOS app Kaleidoscope, Xcode Cloud builds 11017, 11020 and 11021 (Nov 3–4). App Store and Development exports in the same builds succeed; only the Developer ID export fails.

From the export logs:

• The certificate query for DEVELOPER_ID_APPLICATION_MANAGED returns "total" : 0.
• The create request returns HTTP 409, ENTITY_ERROR, resultCode 7460: "You already have a current Developer ID Application Managed certificate or a pending certificate request."
• The export then fails with No "Developer ID Application" signing certificate matching team ID "4G35KLFD64" with a private key was found.

A few data points that might help narrow this down:

1. Timing. Build 11016 on Oct 15 still signed with the managed certificate (ID PXZ54PQ6QZ, serial 02D86889999D3EA2). That certificate was issued Aug 18, 2026 by the previous Developer ID Sub-CA and expires Feb 1, 2027. Nov 3, the first failing build, is exactly 90 days before that expiry, which is when the automatic rotation is documented to start. The certificates in the other reports here expire Feb 1–2, 2027 as well, so this looks like the automatic rotation to the G2 Sub-CA stalling, not a per-team misconfiguration.

2. Portal vs. API. The managed certificate is still listed in Certificates, Identifiers & Profiles for our Account Holder, while the Xcode Cloud certificate API returns an empty list for the type. Admins on the team do not see it in their list at all.

3. Manual rotation does not help. Our Account Holder clicked Rotate on the certificate; the dialog states manual rotation is available from six months after creation until 90 days before expiry, which this certificate is outside of. The next build failed identically.

4. Revoking is not an option for us. The managed certificate has signed every build we shipped since August. Per the Developer ID support page, apps signed with a revoked Developer ID certificate can no longer launch. We would appreciate confirmation from DTS whether that applies to cloud-managed certificates as well, since the accepted answer in thread 853905 recommends revoking.

Error ID from build 11020, in case it helps whoever looks at the server side: 0ae275a5-d31e-4822-b2ac-8763c13e2162. A Developer Support case is being opened by our Account Holder.

D’oh! I posted the wrong URL. I’ve gone back and fixed that.

As should be clear by now, this is affecting a number of developers. We’re tracking it as FB25329877 [1].

You definitely don’t want to be revoking any Developer ID certificates. As explained on Account > Certificates > Certificates overview, that’s has a significant impact and it only makes sense if it was compromised. That’s why revocation is a manual operation for Developer ID [2].

As to what you should do right now, I don’t have good answer for you. I’m off to do more research and I’ll get back to you.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] This is a developer-filed bug. I don’t think it’s from anyone on this thread but, if I’m wrong and this is your bug, thanks for filing it.

[2] I suspect there’s a terminology mixup with the accepted answer on that other thread.

Michael Coding Monkey wrote:

I filled FB25447492

Thanks for that.

We’ve put a temporary workaround in place that we hope will get folks unblocked (i. 104121520). If you’re having this problem, please retry and then reply here with the results.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

The temporary workaround has not fixed it for me. I still get the same archive error.

2026-11-06T13:41:24.372900741Z	error: exportArchive Automatic signing cannot update bundle identifier "com.xxx".
2026-11-06T13:41:24.372907533Z	  Automatic signing cannot update your registered bundle identifier to enable Font Enumeration. Update your bundle identifier on https://developer.apple.com/account and then try again.
2026-11-06T13:41:24.372911304Z	
2026-11-06T13:41:24.372913767Z	error: exportArchive No profiles for 'com.xxx' were found
2026-11-06T13:41:24.372918258Z	  Xcode couldn't find any iOS App Store provisioning profiles matching 'com.xxx'.

I've tried a new build (1273), and am seeing the same error as before:

2026-11-06 13:55:42 +0000  2026-11-06 13:55:42 +0000 IDEProvisioningLedgerEntry: 2026-11-06 13:55:42 +0000 IDEProvisioningLedgerEntry: Response payload: {
  "errors" : [ {
    "id" : "2281c16d-7358-4a63-bd51-5103bd969713",
    "status" : "409",
    "code" : "ENTITY_ERROR",
    "title" : "There is a problem with the request entity",
    "resultCode" : 7460,
    "detail" : "You already have a current Developer ID Application Managed certificate or a pending certificate request."
  } ]
}

The only difference on our end was changing the Xcode version from Xcode 27.2 RC (27B48) to Xcode 27.2 (27B52)

Retried after the workaround was announced: build 11022 today (Nov 9, 10:37 UTC) fails identically. The query for DEVELOPER_ID_APPLICATION_MANAGED still returns "total" : 0, and the create request still returns 409 ENTITY_ERROR resultCode 7460, 32 times, once per bundle in the archive. App Store and Development exports succeed as before.

Team 4G35KLFD64, Xcode 27.2 (27B52). Nothing changed on our side since build 11021. FB25447492 has the logs; I will attach the build 11022 logs there as well.

I appreciate you all testing this out. I’ve passed these (sadly negative) results on to the folks investigating this.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Same issue for team TNVENL2JX3, feedback FB25504259 (related to FB25329877). The symptoms match the original post: only the Developer ID export fails, DEVELOPER_ID_APPLICATION_MANAGED always returns "total" : 0, then creation fails with 409 / 7460. We haven't created or revoked any certificate.

One thing that may help: the same archive exports fine locally with cloud-managed signing in Xcode 27.2, with no local Developer ID identity available. It's signed with a managed certificate issued on 7 Nov 2026 (serial 5FB3C714E33951E2). Our shipped builds use the previous one (serial 21A601CF9AB7DAC0, issued Feb 2024). Both expire at exactly 1 Feb 2027 22:12:15 GMT, because both were issued by the original Developer ID Certification Authority, not G2, and that CA expires at the same second.

So it looks like the rotation issued a new certificate from the expiring CA two days before our first failure. Local cloud signing can use it, but Xcode Cloud's lookup can't see it. Logs are attached to the feedback.

Same fault on our team (Individual membership). Xcode Cloud, macOS Archive, Xcode 27.2 (27B52): 'Export archive for developer-id distribution' fails with exit code 70. The distribution log shows HTTP 409, 'You already have a current Developer ID Application Managed certificate or a pending certificate request', then 'No signing certificate "Developer ID Application" found'. Our Certificates page lists two Developer ID Application Managed (Xcode Cloud) certificates, both expiring 2027/02/01. The App Store and Development exports in the same build succeed. It has failed on every Mac build since late October, the latest today. We have not revoked anything and will retry when a fix is in place.

Hello!

Same failure here. Same symptoms. Same error messages for HTTP requests in the logs. I have contacted phone support and they were unable to revoke the managed certificate Xcode Cloud had created and suggested that I open a Technical Support request. I have done so but recevied no reply in a few days since then.

Since Support is unable to revoke managed certificate Xcode Cloud has created, this thread are unhelful in our case.

We're resorting to performing manual releases right now and Xcode Cloud is completely unusable for our app.

Tony.

We've tried a new build (1286), and are seeing the same error as before:

2026-11-11 04:06:19 +0000  2026-11-11 04:06:19 +0000 IDEProvisioningLedgerEntry: 2026-11-11 04:06:19 +0000 IDEProvisioningLedgerEntry: Response payload: {
  "errors" : [ {
    "id" : "16079629-132f-48a0-bed6-7ef7fa8481a8",
    "status" : "409",
    "code" : "ENTITY_ERROR",
    "title" : "There is a problem with the request entity",
    "resultCode" : 7460,
    "detail" : "You already have a current Developer ID Application Managed certificate or a pending certificate request."
  } ]
}