WWDR Intermediate Certificate Expiration Update
On February 14th, the Apple Worldwide Developer Relations Certification Intermediate Certificate expired. Since then we have seen a few issues, and would like to share some additional details and steps for resolution. We apologize for any inconvenience.
Xcode unable to create distribution builds for App Store Submissions or Enterprise apps.
This issue occurs when the expired WWDR Intermediate certificate is present in both the System keychain and Login keychain within the Keychain Access application. To resolve the issue, first download and install the renewed WWDR Intermediate certificate. Next, in the Keychain Access application, select the System keychain. Select 'Show Expired Certificates' in the View menu and then delete the expired version of the Apple Worldwide Developer Relations Certificate Authority Intermediate certificate. Your certificates should now appear as valid in Keychain Access and be available to Xcode. This issue is resolved in OS X El Capitan 10.11.4 beta.
Mac App Store purchases failing to launch.
In some scenarios, an app purchased from the Mac App Store that utilizes receipt validation may fail to launch (exiting with a 173 error code) since it considers a local receipt that includes the expired WWDR Intermediate certificate invalid. OS X regards the receipt as valid when the updated WWDR Intermediate is present on your system and therefore does not request an updated receipt for the application.
To resolve this issue, delete the renewed, non-expired WWDR Intermediate certificate from your System and/or Login keychain within the Keychain Access application. After re-launching the application, you will be prompted for your Mac App Store login credentials in order to obtain a new receipt for the application. After you have launched your application and obtained a valid receipt, you can re-install the updated WWDR Intermediate certificate to continue your development. This issue will be fixed in a forthcoming update to OS X El Capitan.
Safari Extension Builder unable to locate Safari Extension signing certificate.
When building updates to your extension with Safari Extension Builder in Safari 9.0.3 or earlier, you will encounter an issue where Safari Extension Builder fails to recognize your Safari Extension signing certificate. If your certificate is not available in Safari Extension Builder, update your signing system to OS X El Capitan v10.11.4 beta or install Safari 9.1 for OS X Yosemite and Mavericks beta in order to build updates to your extension.