Every recent attempt to create a Installer certificate has failed, and now we've hit the maximum. We can't revoke them either — the portal only shows "Download," not "Revoke." Xcode also fails with:
"Signing Certificates Error: There is a problem with the request entity. You already have a current Developer certificate or pending certificate request."
This is completely blocking notarization and distribution of our macOS app. Has anyone resolved this, or does it require Apple to intervene on the backend?
(This is a relatively new issue, we have successfully done this in the past hundreds of times over the years.)
Every recent attempt to create a Installer certificate has failed
Clearly it hasn’t failed completely, in that you’ve hit the limit so you must’ve actually created the certificates. So, it’s not a failure to create the certificates, but rather that something has gone wrong after you’ve created them. It’s hard to say what that is without more info.
In general, Developer ID signing identities are precious and you have to manage them carefully. I have a lot to say about this in The Care and Feeding of Developer ID.
As explained in that post, the best way to resolve this is to recover the private key associated with your existing certificates and thus recover your ability to sign your installer. The post has a lot of suggestions for how you might do this.
Once you’re able to form a signing identity by pairing up the private key and its certificate, if you’re still having problems signing then post back here with the details and I should be able to set you on the right path.
does it require Apple to intervene on the backend?
The above-mentioned post explains your option for that, but it’s not a path you want to head down until you’ve exhausted all your other options.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"