Hi, That was the magic touch! We re-checked the portal following your instructions: Verified that each certificateId in the URL was unique for all 4 certificates. Re-downloaded all 4 certificate files from the portal. This time, the downloaded .cer files were indeed distinct and matched the newly generated serial numbers! We were able to successfully import the new certificate into Keychain and pair it with our private key for signing. The issue is now completely resolved. Thank you so much for your invaluable assistance and guidance in isolating this! Thanks again for your support!

Hi, Thank you so much for stepping in! Yes, I am working for Team ID M________9. Here are the details to your questions: High-Level Goal: Our current Developer ID Application certificate has already expired, so we urgently need to issue a new signing identity to build and sign our macOS software releases. However, across all 4 attempts with distinct CSRs, the newly downloaded certificate files consistently carry the exact same expired expiration date as our old certificate, rather than issuing a fresh one. Certificates Listed in Portal: Currently, we see 4 Developer ID Application certificates listed under our Team ID in the portal. Because we are aware of the strict limit on Developer ID certificates, we halted further attempts as soon as we noticed that the portal was repeatedly returning the same expired certificate file. We would greatly appreciate your guidance on how to safely clear this stuck state or reset the identity for our team so we can obtain a functional certificate. Thanks again for your support!