This certificate has an invalid issuer

This certificate has an invalid issuer 

up vote 353 down vote favorite 75

I have created a certificate to enable Push Services in my app, but every time I try to add certificate to my Keychain, after adding certificate it shows me following error: This certificate has an invalid issuer Any help will be appreciated. Thanks. ios  xcode  apple-push-notifications  ssl-certificate  keychain share improve this question edited Feb 18 at 17:24 asked  Feb 14 at 9:05 Aamir 2,127 2 8 19

3   developer.apple.com/support/certificates/expiration –  matt  Feb 15 at 1:29 3   check this one stackoverflow.com/a/35406327/5512225 –  Avaan  Feb 15 at 10:46 32   Note to people voting to close: This is on-tropic because it is about a TOOL that PROGRAMMERS use. –  Ian Ringrose  Feb 16 at 11:29 add a comment

10 Answers

active oldest votes

up vote 517 down vote

I think I've figured this one out. I imported the new WWDR Certificate that expires in 2023, but I was still getting problems building and my developer certificates were still showing the invalid issuer error. In keychain access, go to View -> Show Expired Certificates. Then in your login keychain highlight the expired WWDR Certificate and delete it. I also had the same expired certificate in my System keychain, so I deleted it from there too (important). After deleting the expired certificate from the login and System keychains, I was able to build for Distribution again. share improve this answer edited Feb 17 at 23:25 Peter Mortensen 9,422 11 67 98 answered  Feb 15 at 0:12 AcidicSkittles 3,410 1 2 11

4   Thank you very much. This worked for me as well. It is important to remove the expired certificate from both the login and System keychains. –  dfmuir  Feb 15 at 1:07 33   Had followed previous advise to delete based on 'Show Expired Certificates', but had only done Login. Also deleting from System did the trick. –  markdwhite  Feb 15 at 3:08 8   please note, that you need to remove it also from System as well –  Soufiane.ess  Feb 15 at 20:01 3   For me, I already had the new certificate (that expires in 2023), but I also had the old one that had expired. Both were in my System keychain. Once I removed the old certificate, I was able to build using my Distribution cert. –  CoBrA2168  Feb 15 at 21:58 5   Deleting expired certificate from System is rather most important. –  Nitish  Feb 16 at 5:49 show 10 more comments

up vote 217 down vote

Download https://developer.apple.com/certificationauthority/AppleWWDRCA.cer and double-click to install to Keychain. Select "View" -> "Show Expired Certificates" in Keychain app. Confirm "Certificates" category is selected. Remove expired Apple Worldwide Developer Relations Certificate Authority certificates from "login" tab and "System" tab. Here's Apple's answer. Thanks for bringing this to the attention of the community and apologies for the issues you’ve been having. This issue stems from having a copy of the expired WWDR Intermediate certificate in both your System and Login keychains. To resolve the issue, you should first download and install the new WWDR intermediate certificate (by double-clicking on the file). Next, in the Keychain Access application, select the System keychain. Make sure to select “Show Expired Certificates” in the View menu and then delete the expired version of the Apple Worldwide Developer Relations Certificate Authority Intermediate certificate (expired on February 14, 2016). Your certificates should now appear as valid in Keychain Access and be available to Xcode for submissions to the App Store. https://forums.developer.apple.com/thread/37208 share improve this answer edited Feb 15 at 12:40 answered  Feb 15 at 2:40 mishimay 2,563 1 12 15

Deleting expired Apple Worldwide Developer cert from key chain only helps but some times keychain does not show up you have quit and open key chain then search again Apple Worldwide Developer and make sure you should be selecting Allkeys. It took hell lot of time to fix this because expired Apple Worldwide Developer cert was still appearing after many deletions. –  ashish  Feb 16 at 12:24  Do I need to export the apple push service certificate newly after doing these above steps and upload them in my server? suddenly push notifications are not working. –  NAZIK  Feb 17 at 5:02 I got stuck in the part where I should have removed the old certificate - couldn't do it due to UNIX permissions error - and this thread just saved my life: stackoverflow.com/questions/35511314/… –  Or Shanoon  Feb 25 at 9:32 add a comment

up vote 125 down vote

This is not actually a development issue. It happens due to expiration of the Apple Worldwide Developer Relations Intermediate Certificate issued by Apple Worldwide Developer Relations Certificate Authority. WWDRCA issues the certificate to sign your software for Apple devices, allowing our systems to confirm that your software is delivered to users as intended and has not been modified. To resolve this issue, you have to follow the below steps: Open Keychain Access Go to View -> Show Expired Certificates Go to System in Keychain  Here you find that "Apple Worldwide Developer Relations Certificate Authority" is marked as expired. So delete it. Also check under Login Tab and delete expired WWDRCA. Download new WWDR Intermediate Certificate from here. Install it by double clicking on it. It's done!!! If you still face any issue with your iOS apps, Mac apps, Safari extensions, Apple Wallet and Safari push notifications, then please follow this link of expiration. The Apple Worldwide Developer Relations Certification Intermediate Certificate expires soon and we've issued a renewed certificate that must be included when signing all new Apple Wallet Passes, push packages for Safari Push Notifications, and Safari Extensions starting February 14, 2016. While most developers and users will not be affected by the certificate change, we recommend that all developers download and install the renewed certificate on their development systems and servers as a best practice. All apps will remain available on the App Store for iOS, Mac, and Apple TV. share improve this answer edited Feb 18 at 14:14 David Cheung 564 1 6 26 answered  Feb 15 at 12:49 technerd 3,411 4 7 20

need to ensure that its really get deleted..now worked. Thanks. –  preetam  Feb 17 at 6:03 That's funny. I had problems with that certificate too, but in a other way –  CocoaBean  Feb 18 at 15:09 2   I got stuck trying to remove the old certificate - couldn't do it due to UNIX permissions error - and this thread just saved my life: stackoverflow.com/questions/35511314/… –  Or Shanoon  Feb 25 at 9:33 add a comment

up vote 88 down vote

Here is how we fixed this. Step 1: Open Keychain access, delete "Apple world wide Developer relations certification authority" (which expires on 14th Feb 2016) from both "Login" and "System" sections. If you can't find it, use “Show Expired Certificates” in the View menu. Step 2: Download this and add it to Keychain access -> Certificates (which expires on 8th Feb 2023). Step 3: Everything should be back to normal and working now. Reference: Apple Worldwide Developer Relations Intermediate Certificate Expiration share improve this answer edited Feb 26 at 13:19 Ashish Ahuja ツ 1,914 1 8 34 answered  Feb 15 at 1:56 Mohith Km 1,858 11 15

1   I got stuck where I should have removed the old certificate - couldn't do it due to UNIX permissions error - and this thread just saved my life: stackoverflow.com/questions/35511314/… –  Or Shanoon  Feb 25 at 9:33 add a comment

up vote 31 down vote

In Apple's Developer's portal, add a new certificate, and when asked "What type of certificate do you need?" choose "WorldWide developer relations certificate". Generate the new certificate, download and install. The moment you do that, you will no longer see the message you have described. Edit: The certificate can be downloaded from the following page:https://www.apple.com/certificateauthority/ You can choose one of the following two certificates: "WWDR Certificate (Expiring 02/07/23)" or "WWDR Certificate (Expiring 02/14/16)" share improve this answer edited Feb 14 at 9:41 answered  Feb 14 at 9:19 Arik Segal 436 1 9

there is no such option appears when we add new certificate –  Aamir  Feb 14 at 9:23 8   downloaded and installed the new cert but still having the same issue - anything else have to do? –  Mr Zorn Feb 14 at 21:22 @MrZorn I'm having the same problem, but just FYI I tried to export the p12 and it worked anyway. –  superarts.org  Feb 14 at 23:06 4   @MrZorn U need to go View -> show expried -> del the old WWDR cert –  Tj3n  Feb 15 at 4:47  add a comment

up vote 24 down vote

If you are facing the "This certificate has an invalid issuer" error for all your certificates then do the following steps. Steps: Open Keychain and Click on Login -> All Items from the left panel. Now, Click on View -> Show Expired Certificates from the top navigation menu. Now search for "Apple Worldwide Developer Relations Certification Authority" and delete expired certificates.  After deleting expired certificates, visit the following URL and download the new certificate,https://developer.apple.com/certificationauthority/AppleWWDRCA.cer. Double click on the newly downloaded certificate, and install it in your keychain. Double check: List expired certificates by following step number 3. Now you have a valid "Apple Worldwide Developer Relations Certification Authority" having expiry date 2023-02-07. Reference: Apple Worldwide Developer Relations Intermediate Certificate Expiration share improve this answer edited Feb 17 at 23:33 Peter Mortensen 9,422 11 67 98 answered  Feb 15 at 12:03 milanpanchal 1,735 7 21

add a comment

up vote 22 down vote

As described in the Apple Worldwide Developer Relations Intermediate Certificate Expiration: The previous Apple Worldwide Developer Relations Certification Intermediate Certificate expired on February 14, 2016 and the renewed certificate must now be used when signing Apple Wallet Passes, push packages for Safari Push Notifications, Safari Extensions, and submissions to the App Store, Mac App Store, and App Store for Apple TV. All developers should download and install the renewed certificate on their development systems and servers. All apps will remain available on the App Store for iOS, Mac, and Apple TV. The new valid certificate will look like the following: It will display (this certificate is valid) with a green mark. So, go to your Key Chain Access. Just delete the old certificate and replace it with the new one (renewed certificate) as Apple described in the document. Mainly the problem is only with the Apple push notification service and extensions as described in the Apple document. You can also check the listing of certificates in https://www.apple.com/certificateauthority/ Certificate Revocation List: Now this updated certificate will expire on 2023-02-08. If you could not see the old certificate then go to the System Keychains and from edit menu and select the option Show Expired Certificates. Now you can see the following certificate that you have to delete: share improve this answer edited Feb 17 at 23:42 Peter Mortensen 9,422 11 67 98 answered  Feb 16 at 4:24 Ashish Kakkad 9,604 5 21 54

add a comment

up vote 22 down vote

As mentioned by mishimay, follow the below steps: Download and install from here. Double click and install it. Select "View" -> "Show Expired Certificates" in Keychain app. Remove Apple Worldwide Developer Relations Certificate Authority certificates from "login" tab and "System" tab in Keychain app. If you don't find your WWDR certificate in login or system tab, then select category "All items" on the left side. Most probably you will get to see an expired WWDR certificate here, and you can remove it. An expired certificate is always shown with a red asterisk. share improve this answer edited Mar 8 at 20:26 M-T-A 3,005 3 16 32 answered  Feb 15 at 6:54 Kondal Kolipaka 759 5 9

add a comment

up vote 17 down vote	You need to search the "World" from the top right search bar and delete the expired certificate. Make sure you selected "Login" and "All items". share improve this answer edited Feb 17 at 23:43 Peter Mortensen 9,422 11 67 98 answered  Feb 16 at 5:58 Ahsan 614 4 8
	add a comment

up vote 16 down vote

Just try to set local date earlier than Feb 14. Works for me! Not a complete solution but temporary solve the problem. share improve this answer