iOS 7.0 코드 서명 ID가 없습니다.

iOS 7.0 코드 서명 ID가 없습니다.

---

• 인증서가 유효합니다
• xcode 5
• IOS 7

코드 서명 오류 : 공동 디자인 ID가 없음 : 빌드 설정에 지정된 프로비저닝 프로파일 (“iOS 팀 프로비저닝 프로파일 : *”)과 일치하는 공동 디자인 ID (예 : 인증서 및 개인 키 쌍)가 없습니다. CodeSign 오류 : SDK 'iOS 7.0'의 제품 유형 'Application'에 코드 서명이 필요합니다.

---

인증서

1. 이전 인증서를 해지하십시오.
2. 새로운 개발 인증서를 생성하십시오.
3. 인증서를 다운로드하십시오.
4. KeyChain에 두 번 클릭하십시오.

프로비저닝 프로파일

1. 신규 또는 기존 프로비저닝 프로파일 편집을 작성하십시오.
2. 다운로드하여 설치하십시오.

BundleIdentifier의 경우.

1. com.yourcompanyName.Something (AppId와 동일)

CodeSigningIdentity.

1. 작성한 프로비저닝 프로파일을 선택하십시오.

---

이 문제에 대한 나의 해결책은 다음과 같다.

Xcode> 환경 설정. 계정에서 Apple ID를 클릭하십시오. 세부 사항보기를 클릭하고 프로젝트 프로비저닝 프로파일 (이것이 도움이된다고 생각 함)을 클릭 한 다음 왼쪽 아래에있는 새로 고침 단추를 클릭하십시오.

---

이것에 대한 개인적인 경험으로 다른 답변을 보충 할 것이라고 생각했습니다.

최근에 두 개의 대상이 빌드되는 문제가 있었고 두 개가 다음 오류로 인해 실패했습니다.

코드 서명 오류 : 코드 서명 ID가 없습니다. 팀 ID "XXXXXXXXXX"와 일치하는 유효한 서명 ID (예 : 인증서 및 개인 키 쌍)가 없습니다. CodeSign 오류 : SDK 'iOS 7.1'의 제품 유형 'Application'에 코드 서명이 필요합니다.

이것은 Xcode와 iOS 개발자 센터 의 모든 내용을 업데이트 했음에도 불구하고있었습니다 .

힌트는 빌드 실패 메시지에 표시된 팀 ID가 오래되었다는 것입니다.

project.pbxproj텍스트 편집기에서 Xcode의 파일을 열면 이전 팀 ID가 발견되었습니다.

D29A93A318AB96440099C177 = {
        DevelopmentTeam = XXXXXXXXXX;
};

또한 project.pbxproj파일 을 얻으려면 파일을 선택 .xcodeproj하고 다음과 같이 내용을 표시하십시오.

대상 ID를 검색 D29A93A318AB96440099C177하면 실패한 대상 중 하나와 일치 함을 알 수 있습니다.

targets = (
    F5E8B19A16E64505006F22D4 /* MyTarget1 */,
    93DB2342183F737100BEA69F /* MyTarget2 */,
    D29A93A318AB96440099C177 /* MyTarget3 */,
    D200F4B518AB968A00F58C21 /* MyTarget4 */,
    F5E8B1C016E64505006F22D4 /* MyTarget5 */,
    589FB35119114DED003D9350 /* MyTarget6 */,
);

이 경우, MyTarget3. 이를 해결하기 위해 간단한 텍스트 검색으로 기존 팀 ID를 새로운 올바른 ID로 대체했습니다. 문제 해결됨.

요약하자면 Xcode의 프로젝트 파일의 복잡성을 탐구하는 대신 위의 답변을 사용하여 상황이 해결되기를 바랍니다. 그러나 그렇지 않은 경우 오류에 잘못된 팀 ID가 표시되면 해당 팀 ID가 여전히 주변에 있는지 확인할 가치가 있습니다.

---

개발에서 똑같은 문제가있었습니다. 나는 그것을 해결했다.

1. Go to XCode preferences, view details of the Apple ID, and delete the provisioning file that's complaining.
2. Go to the Keychain Access, and delete the development certificate that's related to the provisioning file you just deleted.
3. In Apple Member Center, download the development provisioning file you just deleted locally, double click the file to make sure it's appearing in XCode.
4. Download the development certificate you just deleted locally, and double click to make sure it appears in the Keychain Access.
5. It should be good to go now.

---

I just had this problem with Jenkins.

The solution was to copy the certificate and paste it into the system keychain otherwise Jenkins couldn't read the certificate.

---

You should not have to delete all profiles to fix this issue,

When looking at my device profiles in the Organizer I saw one of my profiles was not valid. I then went to the Developer Certificates, Identifiers & Profiles page and all profiles were active, green and looked good but when clicking edit on the one that showed as invalid on my device, I saw that the check box in the associated account was not checked even though Select All was checked. I checked the box to associate the profile with my certificate, downloaded the Profile and everything was fixed.

On your Profiles web page click "Edit"

You might see that there is no associated certificate even though "Select All" is checked.

---

For me, setting Project → Targets/[Your project] → General → Team to "None" solved the issue.

---

Having gone through a ridiculous amount of time trying to solve one of these, and I definitely can see where most of these answers could be correct in some cases, my situation was not all that uncommon.

I was trying to deploy to the app store to test with TestFlight. A previous developer, no longer part of the project or company, had created the IOS Distribution Certificate. What xcode was trying to tell me was that yes, the certificate was in the member center, but dude you totally can't use it because it's not yours. I didn't have the private key needed to sign with it and no amount of refreshes, restarts, revokes were going to help me. You need a developer and distribution certificate to upload to the app store.

The solution was to create a new production distribution certificate in the member center, using a new signing request from my keychain. This process is documented well and described while you create the cert online. Once done, refresh your account in xcode to download to your keychain and you will be golden. I hope this helps somebody!

---

it might sound strange but for me worked restarting my mac..i cant explain why and what happened but it works now. hope it will helps someone

---

I reached this thread when I am using pure command line/jenkins build script and I don't want any single UI/RDP manually setup for the integration environment.

After a few hours try to solve exactly the same issue using jenkins.
The key is "security list-keychains -s <your_keychain_name>"

--- Long story ---
I use a script in jenkins to override per-project settings (provisioning profile and signing identities)
After upgrade to Xcode 7, I have to change the script add above "list-keychains" after "create-keychains"

Updated script here.

---

you need not to delete all your profiles.I had same issue and fixed it by installing the missing certificates. You might forgot to install the required certificate for the provisioning profile you are using for code signing.

• make sure that you installed desired certificates(development/distribution) into keychain for the code-signing provision profile(development/distribution).

---

Try to change Bundle Identifier: Project -> Targets/[Your project] -> General -> Bundle Identifier

If app was published at AppStore XCode doesn't allow create the application with the same bundle identifier.

---

Targeting iOS 8 and 9 on Xcode 7. My development profile is fine, I got this error while archiving the app for uploading to the app store. Here's what I did:

Xcode > Preferences > Accounts > View Details. Beside iOS Distribution, click the "Reset" button. This will invalidate the distribution provisioning profile that you are using (because you reset the distribution certificate), so edit the profile to include the newly reset certificate.

Make sure to download both the new distribution certificate and the newly edited distribution provisioning profile. Restart Xcode.

---

Make sure that your certificate is connected with your private key:

Open Keychain access, login, Certificates. Find the certificate inside the list and see if it is properly paired with your private key.

If certificate is not signed with private key, delete it, go to apple developer page and create new certificate. Sometimes it will be needed to revoke old. This new certificate will be now properly signed with your private key.

Now, when you have new certificate, recreate needed provisioning profiles that will include new certificate in creation process.

Note, when somebody from your team reset this certificate with his private key, this same problem can appear again during the refresh process. I am not sure, but it seems that every developer in team must have own certificate for distribution.

---

Obviously this issue has different causes. :)

For my case, my account log in expired... I solved it by simply:

XCode -> Preferences -> Account -> Apple IDs -> Select the related ID and renew the log in...

Hope this helps!

---

Go to the Issue navigator and check if Signing Identity: is present in your Keychain Access. If no, download .cer file and append it to the keychain.

---

After Pulling hair for a long time,I finally found an issue.I've selected wrong certificate while creating Provisioning Profile,By selecting right one,It helped for me.In your case,If it is multiple then You have to try and select one by one to get this issue solved.

---

I had this ambiguous error, "Command /usr/bin/codesign failed with exit code 1", when I was setting up new Jenkins boxes for iOS builds with Xcode 7.3, OSX 10.11.4.

In my case I had several things right: 1.Yes I had added my certificates to the keychain, both Apple's root and the team's cert. 2.Yes I downloaded the correct provisioning profile via xcode preferences. 3.Yes it even built manually in xcode.

However, for jenkins, there was perhaps a caching issue on xcode. What worked was: 1.Exit the Xcode GUI. 2.Get back in, and run the build manually once. 3.Only then will Xcode prompt to allow keychain access authorization. 4.Jenkins has some settings that might be able to fix this, but my machines are secure, so I click 'always allow xcode to access the keychain'.

---

With fastlane installed, you can create and install an Development Certificate by

cert --development
sigh --development

참고URL : https://stackoverflow.com/questions/19197497/ios-7-0-no-code-signing-identities-found