Objective
Ah, every time after the festival to have a pit for their own jump. Can't escape the claws.
This is not, after the Spring Festival, came back to find the company certificate appears "invalid issuer of this certificate".
Cause of the problem
After some search, Apple officially gave an answer.
Thanks for bringing the attention of the community and apologies for the issues you ' ve been have. This issue stems from have a copy of the expired WWDR Intermediate certificate in both your System and Login keychains. To resolve the issue, your should first download and install the new WWDR Intermediate certificate (by double-clicking on T He 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 Worldwid E Developer Relations Certificate Authority intermediate Certificate (expired on February 14, 2016). Your certificates should now appear as valid in Keychain Access and being available to Xcode for submissions to the APP Store .
It appears to be due to an Apple system security certificate expiration issue.
Apple reminded developers to use the new certificate one months ago. If the developer does not update in time, it will not only affect their own development work, but also may cause problems for users. This notification is for developers who develop apps that are related to the Apple Wallet, Safari Push Center, or safari plugin. Apple also said in a notice that developers need to update their security credentials before the end of February 14, 2016. After the update, the next expiration period for the security certificate is February 2023.
Solutions
Now that you know the reason, you can get the right remedy. We download the latest security certificate provided by Apple and double-click Install.
- Then open the keychain, on the navigation bar, select
显示
- 显示已过期的证书
- Select
登录
-所有项目
- Enter Apple W under the search bar
- Delete the corresponding expired security certificate
iOS Development certificate "Invalid issuer of this certificate" workaround