blocks|key|336852|text|更新：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|336853|我最初回答中的技术说明现在已被弃用。苹果在一个新文档中发布了一系列代码签名问题(以及一些解决方案)：Technical+Note+TN2407+Code+Signing+Troubleshooting+Index|336854|检查生成设置中的CODE_SIGN_IDENTITY属性。是否在此处选择了您的配给配置文件？|336855|您还需要在应用程序.plist中输入有效的捆绑包标识符。|336856|标识符必须与您在生成配置文件时提供的标识符匹配。|336857|苹果对这款here有一个技术说明。|336858|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/library/mac/technotes/TN2407|1|http://developer.apple.com/iphone/library/technotes/tn2009/tn2242.html^0|0|3|0|1E|1K|0|0|0|0|0|5|4|1|0^^$0|@$1|2|3|4|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|12|8|@]|D|@$9|13|A|14|1|15]]|E|$]]|$1|H|3|I|5|6|7|16|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|17|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|18|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|19|8|@]|D|@$9|1A|A|1B|1|1C]]|E|$]]|$1|P|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]]|Q|$R|$5|S|T|U|E|$V|W]]|X|$5|S|T|U|E|$V|Y]]]]

Update: 
The Technical Note in my original answer is now deprecated. Apple posted a collection of code signing problems (and some solutions) in a new document: <a href="https://developer.apple.com/library/mac/technotes/TN2407" rel="noreferrer">Technical Note TN2407 Code Signing Troubleshooting Index</a>

Check the CODE_SIGN_IDENTITY property in your build settings. Is your provisioning profile selected there? 
You also need to enter a valid bundle identifier in your apps .plist. 
The identifier has to match the one you provided when generating the profile. 
Apple has a technote about that <a href="http://developer.apple.com/iphone/library/technotes/tn2009/tn2242.html" rel="noreferrer">here</a>.

blocks|key|3316494|text|我刚刚遇到了这个错误，下面是我所发现的，以防这对任何人都有帮助:我发现您可以在Xcode中右键单击错误消息，然后选择expand以获取更多详细信息，包括对问题的描述。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3316495|在我的例子中，我在不同的密钥链文件中有两份同名的开发人员证书副本，而Xcode不知道该使用哪一个。|3316496|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I just came across this error, and here's what I found out in case this helps anyone: I discovered that you can right click the error message in Xcode and choose expand to get more details, including a description of the problem.

In my case, I had two copies of my developer certificate with the same name in different keychain files, and Xcode couldn't figure out which one to use.

blocks|key|335739|text|对于Xcode9.0中codesign问题，这可能是一个奇怪的答案。我也收到了这个错误，不知道该怎么做，因为一切都是正确的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|335740|我去了钥匙链，我有登录选项“解锁”。我锁定了它并重新编译了我的构建。Xcode本身要求我打开访问密钥链。我给了它访问权，它起作用了。|335741|步骤包括：|335742|335743|转到keychain|ordered-list-item|335744|Lock+it|335745|归档代码，再次构建项目|335746|335747|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|U|8|@]|9|@]|A|$]]|$1|J|3|K|5|I|7|V|8|@]|9|@]|A|$]]|$1|L|3|M|5|I|7|W|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

It might be strange answer for codesign issue in Xcode 9.0. I was receiving this error too and did not know what to be done, because everything was correct.

I went to the keychain, I had the login option "unlocked". I locked it and compiled my build again. Xcode itself asked me to open access keychain. I gave access and it worked.

Steps were:

<ol>
<li>Go to keychain</li>
<li>Lock it</li>
<li>Archive the code, build the project again</li>
</ol>

blocks|key|338009|text|我犯了完全相同的错误，我尝试了所有的方法，包括本页其他地方的东西，但都没有成功。我遇到的问题是，在Keychain+Access中，实际的Apple+WWDR证书被标记为"Always+Trust“。它需要是"System+Defaults“。这也适用于您的开发和分发证书。如果它们中的任何一个被错误地设置为"Always+Trust"，显然会导致这个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|338010|因此，在Keychain+Access中，单击Apple+Worldwide+Developer+Relations+Authority证书，选择Get+Info。然后，展开信任设置，对于"When+using+this+certificate:“的组合框，选择"System+Defaults”。|338011|其他人评论说，对于这些错误，您可能必须在System和login+keychains中执行此操作。|338012|entityMap^0|2E|C|2X|F|4B|C|0|21|8|2N|S|3O|F|0|K|6|R|5|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|K|$]]

I had the exact same error, and tried everything under the sun, including what was elsewhere on this page, with no success. What the problem was for me was that in Keychain Access, the actual Apple WWDR certificate was marked as "Always Trust". It needed to be "System Defaults". That goes for your Development and Distribution certificates, too. If any of them are incorrectly set to "Always Trust", that can apparently cause this problem.

So, in Keychain Access, click on the Apple Worldwide Developer Relations Certificate Authority certificate, select Get Info. Then, expand the Trust settings, and for the combo box for "When using this certificate:", choose "System Defaults".

Others have commented that you may have to do this in System and login keychains for these errors.

blocks|key|337119|text|当你得到这样的错误时，可能有很多原因：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|337120|337121|检查您是否在设置中选择了包含有效的代码签名Identity和有效的包标识符的预配配置文件。(进入Build+Settings->Signing->Provisioning+Profile).|ordered-list-item|offset|length|style|BOLD|337122|打开Keychain+Access并点击左上角的锁形图标，这样它就会锁定登录钥匙链，然后再次点击解锁。|337123|337124|​|337125|📷|atomic|337126|337127|337128|转到“文件”->“项目设置”->“派生数据”并删除项目构建文件夹。然后清理并构建您的应用程序。|337129|337130|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/31eb2fcb5f05b10ff43baafe9f5c0025.png|imageAlt^0|0|0|H|C|X|4|0|2|F|0|0|0|0|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|17|8|@$F|18|G|19|H|I]|$F|1A|G|1B|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|1C|8|@$F|1D|G|1E|H|I]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1G|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|1H|8|@]|9|@$F|1I|G|1J|1|1K]]|A|$]]|$1|R|3|N|5|6|7|1L|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]|$1|T|3|U|5|E|7|1N|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13|14|-4]]]]

There could be a lot of reason when you get this kind of error:

<ol>
<li>Check whether you have selected a provisioning profile which includes the valid Code Signing Identity and a valid Bundle Identifier in Settings. (Goto Build Settings->Signing->Provisioning Profile).</li>
<li>Open Keychain Access and click on lock icon at top left, so it will lock the login keychain and then again click to unlock.</li>
</ol>

<a href="https://i.stack.imgur.com/sjdPk.png" rel="noreferrer"><img src="https://i.stack.imgur.com/sjdPk.png" alt="enter image description here"></a>

<ol start="3">
<li>Goto File->Project Settings->Derived Data and delete your project build folder. After that clean and build your app.</li>
</ol>

blocks|key|335481|text|我在构建发行版时也遇到了同样的问题。这一切都发生得很突然。事实上，几天前我没有这个问题，我有我的Ad-Hoc版本编译正确。出现这个问题是因为我的证书今天刚刚过期。因此，我按照苹果的指导创建了一个新的临时应用程序：(http://developer.apple.com/ios/manage/distribution/index.action)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|335482|在网上花了几个小时，并确保我没有陷入可能出错的境地。以下是Tobias和Dan+Ray提出的拯救我的建议：|335483|你可以右击Xcode中的错误消息查看details".|335484|"...the问题是我的系统密钥链上的过期证书。默认情况下，密钥链访问不显示过期证书“。|unordered-list-item|335485|335486|详细的信息告诉我关于模糊匹配两个证书。其中一个恰好是系统密钥链中过期的证书。所以我删除了过期的，然后它就起作用了！我还担心在使用keychain实用程序创建分发证书时，在“通用名称”中输入什么:我的名字或我的公司名称。在我的例子中，我输入了我的名字。我猜这和开发者的自动回复邮件中提到的标题是一样的。|335487|帮了大忙了。谢谢。|335488|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.apple.com/ios/manage/distribution/index.action^0|2Z|1R|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|12|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|13|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|14|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|15|8|@]|9|@]|C|$]]|$1|N|3|O|5|6|7|16|8|@]|9|@]|C|$]]|$1|P|3|-4|5|6|7|17|8|@]|9|@]|C|$]]]|Q|$R|$5|S|T|U|C|$V|W]]]]

I had the same problem the distribution build. It just happened all of sudden. In fact I did not have this problem a few days ago and I had my Ad-Hoc version compile right. This issue came up because my certificate just expired today. So I went create a new provisional following Apple's guidance: (http://developer.apple.com/ios/manage/distribution/index.action). 

After spending hours on the net and made sure I had not fallen for what could go wrong. Here is what save me as suggested by Tobias and Dan Ray:

<ol>
<li>"...discovered that you can right click the error message in Xcode to view details".</li>
<li>"...the issue was an expired certificate on my System keychain. Keychain Access doesn't, by default, show expired certs". </li>
</ol>

The detailed information told me about ambiguous matching two certificates. One of them happened to be an expired certificate in the System key chain. So I deleted the expired one then it worked! I also had a concern about what to enter in the "common name" when create the distribution certificate using the keychain utility: my name or my company name. In my case, I entered my name. I am guessing it is the same as the title that addressed by the developer's auto responder email. 

Great help. Thanks.

blocks|key|338081|text|如果紧接在codesign错误之前的错误表示“资源分支、查找器信息或类似的碎片不被允许”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|338082|然后导航到终端中的.app文件并键入：|338083|xattr+-cr+<+path_to_app_bundle+>|338084|参考：https://developer.apple.com/library/content/qa/qa1940/_index.html|offset|length|338085|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/library/content/qa/qa1940/_index.html^0|0|0|0|3|1T|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@$H|V|I|W|1|X]]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

If the error immediately preceding the codesign error says something like 'resource fork, Finder information, or similar detritus not allowed'

Then navigate to the .app file in Terminal and type:

xattr -cr &lt; path_to_app_bundle >

ref: <a href="https://developer.apple.com/library/content/qa/qa1940/_index.html" rel="nofollow noreferrer">https://developer.apple.com/library/content/qa/qa1940/_index.html</a>

blocks|key|3104063|text|对我起作用的是在构建设置中将--deep添加到其他代码签名标志。更多信息请点击此处：Codesign+of+Dropbox+API+fails+in+Xcode+4.6.3:+"code+object+is+not+signed+at+all"|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|BOLD|entityRanges|data|3104064|不幸的是，这个模棱两可的错误条件有400种不同的解决方案，但我离题了。|3104065|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/q/17263967/264970^0|E|6|N|8|16|28|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|D]]|E|@$9|V|A|W|1|X]]|F|$]]|$1|G|3|H|5|6|7|Y|8|@]|E|@]|F|$]]|$1|I|3|-4|5|6|7|Z|8|@]|E|@]|F|$]]]|J|$K|$5|L|M|N|F|$O|P]]]]

What worked for me was adding <code>--deep</code> to Other Code Signing Flags in Build Settings.
More information here: <a href="https://stackoverflow.com/q/17263967/264970">Codesign of Dropbox API fails in Xcode 4.6.3: &quot;code object is not signed at all&quot;</a>

Unfortunate that this ambiguous error condition has 400 different solutions, but I digress.

blocks|key|3316530|text|我也有同样的问题。最后，我的私钥不允许codesign访问它。可以在密钥链应用程序的信息对话框中看到这一点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3316531|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same problem. In the end it turned out that my private key did not allow codesign to access it. One can see this in the info dialog in keychain application.

blocks|key|3103686|text|我不得不同意托拜厄斯的观点。这个错误太普遍了。当同样的事情发生在我身上时，我深入研究了错误消息，并意识到我搞砸了构建属性中的某些东西，而不是代码签名。所以，是的，我会深入研究细节。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3103687|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I have to agree with Tobias. The error is too generic. When the same thing happened to me I dug into the error message and realized I'd screwed up something in the build properties, but not the code signing. So yeah, I'd dig in to the details.

blocks|key|337920|text|在我的例子中，错误是由于我在密钥链上有两个同名的密钥。我删除了旧的，这就解决了问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|337921|转到详细消息，向我展示真正的问题。|337922|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

In my case error was due to the fact that I had two keys on the keychain with the same name. I deleted the old one and that solved the issue.

Going to the detail message show the real problem to me.

blocks|key|3103823|text|经过几个小时的谷歌搜索和尝试不同的东西后，这就是我修复它的方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3103824|3103825|确保在Keychain+Access的系统>证书选项卡中没有证书。从那里删除所有重复的证书。|ordered-list-item|3103826|将WWDR中间证书安装在来自配给门户的证书下，以及开发人员证书，并确保您在Keychain+Access的登录>证书选项卡中看到它。|3103827|3103828|希望这对你们中的一些人有帮助！|3103829|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|N|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|P|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|L|$]]

after hours of googling and trying out different things, this is what fixed it for me:

<ol>
<li>Make sure there are no certificates in the System > Certificates tab on Keychain Access. Remove all duplicate certificates from there.</li>
<li>Install the WWDR intermediate certificate under certificates from the provisioning portal, in addition to the developers certificates and make sure you see it in the Login > Certificates tab on Keychain Access.</li>
</ol>

hope this helps some of you!

blocks|key|3103845|text|同样的问题与歧义(匹配"iPhone+Developer:+me“和/tweetdeck库privatedata文件。通过将文件移动到垃圾桶并重新登录到Tweetdeck，再次设置密码，修复了该问题。太痛苦了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3103846|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Same issue with ambiguous (matches "iPhone Developer: [me] " and /// tweetdeck's library privatedata file. Fixed it by moving file to the trash and re-logging into Tweetdeck, setting up passwords again. What a pain.

blocks|key|3103969|text|我也遇到了同样的问题，但错误日志中还列出了以下内容:+CSSMERR_TP_CERT_NOT_VALID_YET|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3103970|查看KeyChain中的证书也显示了类似的消息。这个问题是由于我的Mac的系统时钟设置不正确。一旦我设置了正确的区域/时间，证书就被标记为有效，我就可以在iPhone上构建和运行我的应用程序了|3103971|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had the same problem but also listed in the error log was this: CSSMERR_TP_CERT_NOT_VALID_YET

Looking at the certificate in KeyChain showed a similar message. The problem was due to my Mac's system clock being set incorrectly. As soon as I set the correct region/time, the certificate was marked as valid and I could build and run my app on the iPhone

blocks|key|3104051|text|我也收到了这个错误("/usr/bin/codesign失败，退出代码为1")，当我查看Keychain+Access时，我的开发人员证书被标记为“此证书由未知的授权机构签署”。我最近升级到了MacOS10.8，从那时起，我遇到了一些其他的XCode+(4.5.2)问题。原来我没有安装WWDR中间证书。我是从iOS+Provisioning+Portal下载的，安装在Keychain+Access中，然后我的项目再次构建！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3104052|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I was also getting this error ("/usr/bin/codesign failed with exit code 1"), and when I looked in Keychain Access my developer certificates were marked as "This certificate was signed by an unknown authority". I had recently upgraded to Mac OS 10.8 and have had a couple of other XCode (4.5.2) issues since then. It turns out I did not have the WWDR intermediate certificate installed. I downloaded that from the iOS Provisioning Portal, installed that in Keychain Access, and my project builds again!

blocks|key|3104099|text|当我收到这个错误的时候，我甚至没有尝试为应用程序签名。我正在写一个测试应用程序，并不关心签名。为了摆脱此消息，我必须从代码签名下的构建设置中选择“不要代码签名”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3104100|​|3104101|📷|atomic|offset|length|3104102|3104103|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/a9db4132d8cad7ff5f62692cd024e296.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

When I got this error I wasn't even trying to sign the app. I was writing a test app and didn't care about signing. 
In order to get rid of this message I had to select "Don't Code Sign" from Build Settings under Code Signing.

<img src="https://i.stack.imgur.com/LgWef.png" alt="enter image description here">

blocks|key|3316994|text|有时你的build文件夹只是需要清理一下--这对我来说肯定是有效的。感谢loafer-project提供的解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3316995|entityMap|0|LINK|mutability|MUTABLE|url|http://loafer-project.com/usrbincodesign-failed-with-exit-code-1/^0|10|E|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Sometimes your build folder simply needs cleaning - it certainly worked for me. Thanks to <a href="http://loafer-project.com/usrbincodesign-failed-with-exit-code-1/" rel="nofollow noreferrer">loafer-project</a> for the solution.

blocks|key|3103715|text|一个可能的原因是您没有对build目录的写权限。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3103716|解决方案：删除项目文件夹中的所有构建目录并重新构建应用程序。|offset|length|style|BOLD|3103717|entityMap^0|0|0|5|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

One possible cause is that you doesn't have permission to write on the build directory.

Solution: Delete all build directory on your project folder and rebuild your application.

blocks|key|3316603|text|我刚刚遇到这个错误，是因为我试图将构建文件写入一个无法工作的网络驱动器。在我的桌面上再试一次，它工作得很好。(您可能需要在移动构建后对其进行“清理”。只需从“构建”下拉菜单中选择“清理所有目标”即可。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3316604|Tobias是正确的，但是，通过右键单击代码来深入研究代码的细节，看看您的具体问题是什么。|3316605|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I just came across this error and it was because I was trying to write the build file to a network drive that was not working. Tried again from my desktop and it worked just fine. (You may have to "Clean" the build after you move it. Just choose "Clean all Targets" from the "Build" drop-down menu).

Tobias is correct though, dig into the details on the code by right-clicking it to see what your specific problem is.

blocks|key|340578|text|你需要注意的一件事是(我犯了一个愚蠢的错误，但它确实发生了)，企业社会责任附加的电子邮件地址需要与连接到你的Apple+Dev帐户的电子邮件地址相同。一旦我使用了新的CSR并重新构建了所有的证书和配置文件，在applesville中一切都很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|340579|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

One thing that you'll want to watch out for (it's a stupid mistake on my part, but it happens), is that the email address attached to the CSR needs to be the same as the email connected to your Apple Dev account. Once I used a new CSR and rebuilt all the certs and provisioning profiles, all was well in applesville.

blocks|key|3317021|text|另一个原因是，检查您的开发人员帐户是否已连接到xCode|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3317022|​|3317023|📷|atomic|offset|length|3317024|3317025|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/50894bcaf7dbeac2b06d380352c8e476.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

Another reason, 
Check your Developer account is connected with xCode

<a href="https://i.stack.imgur.com/WVT7F.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/WVT7F.png" alt="enter image description here"></a>

blocks|key|3104308|text|这是一个老问题，但似乎仍然会发生。另一种解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3104309|在git中恢复分支后发生的。尝试清理、清理构建、删除派生并重新启动Xcode，但没有成功。|3104310|尝试重新启动计算机。|3104311|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Kinda old question, but still happens it seems. Another solution: 

Occurred for me after reverting a branch in git. 
Tried cleaning, cleaning builds, deleting derived and restarting Xcode, but no luck.

Try rebooting the comp.

blocks|key|3317205|text|我在代码设计中遇到了与您提到的相同的未知错误。与提供的答案类似(但略有不同)，我只是锁定了我的钥匙链访问并将其解锁，然后我能够再次构建并运行我的设备。如果任何人有同样的问题，也许可以在经历修改密钥链密码的麻烦之前先尝试一下。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3317206|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same unknown error from codesigning that you mentioned. Similar to the answer provided (but a little different), I just locked my keychain access and unlocked it, and I was able to build and run to my device again. If anyone has the same issue, perhaps try that first before going through the trouble of modifying the keychain password.

blocks|key|337201|text|把我的评论扔进环里，我只是在尝试刷新我的开发环境后偶然发现了这一点，在一个应用程序请求上意外单击了拒绝，在搜索了周围后，我发现了一些似乎不起作用的东西。这是我尝试修复的完整顺序，以及是否成功：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|337202|1)尝试清除DerivedFiles并重新启动XCode+-没有骰子|337203|2)尝试记录并解锁钥匙链，然后重新启动XCode+-没有骰子|337204|3)尝试在XCode中刷新我的开发人员帐户-没有问题|337205|4)咬紧牙关，重置我的整个钥匙链，然后我的开发者账号被注销了(重新登录)，然后重启了XCode+--没有骰子|337206|5)在这里找到一篇文章，说我们需要将login%7Clocal%7CSystem/+Certificate+/Apple+Worldwide+Developer+Relations+Authority设置为"System+default“。但在我的例子中，它已经设置为系统默认值-没有骰子|337207|6)然后，我查看了我的实际开发人员证书登录/我的证书/Mac开发人员:当我查看那里时，它被正确地设置为在允许访问之前确认，但在较低的部分中没有条目。应该有Xcode，codesign，productbuild。我删除了证书条目并重新启动了XCode+-+bingo|337208|添加了证书，然后系统提示我。所以我做了什么，我按下了“总是允许”然后就把自己给撞了。|337209|我不得不再次返回并删除证书，然后在干净的构建过程中经历大约20个allow对话框。一旦完成，我就可以完全构建了。|337210|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Y|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|Z|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|10|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|11|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|S|$]]

Throwing my comments into the ring, I just came across this after attempting to refresh my development environment after clicking DENY accidentally on one of the application requests, after searching around I found a number of things that didn't seem to work. This is the full order in which I've attempted the fixes and whether there was a success:

1) Attempted to clear the DerivedFiles and restart XCode - no dice

2) Attempted to Log and Unlock the Keychain, then restart XCode - no dice

3) Attempted to refresh my developer account within XCode - no dice

4) Bit the bullet and just reset my entire keychain, after doing so my developer account was signed out (signed back in), then restarted XCode - no dice

5) Found an article on here that said that we needed to set the [login|local|System]/certificate/Apple Worldwide Developer Relations Certificate Authority to "System default". But in my case it was already set to system default - no dice

6) Then I looked at my actual developer certificate login/my certificates/Mac Developer: and when I looked in there it was correctly set to Confirm before allowing access BUT there was no entries in the lower section. There should be [Xcode, codesign, productbuild]. I deleted the certificate entry and restarted XCode - bingo

The certificate was added and I was then prompted. So what did I do, I pressed "always allow" and then just boned myself. 

I had to go back and delete the certificate again, then go through about 20 allow dialogs during a clean build. Once completed, I was able to build completely.

blocks|key|338256|text|对我来说，经过几天的研究，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|338257|我所做的旋转操作如下所示：|338258|338259|删除你的钥匙链上的所有证书。|ordered-list-item|338260|转到你的苹果帐户。a)下载您想要安装在您的密钥链上的指定证书。B)(可选)还要创建并下载require。在Xcode中使用|338261|，清理您的项目。这可能需要一些时间。|338262|生成您的项目。|338263|338264|这应该适用于类似的codesign问题。|338265|请注意，在此过程中，操作系统会要求您进行凭证验证。|338266|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|X|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|Y|8|@]|9|@]|A|$]]|$1|J|3|K|5|G|7|Z|8|@]|9|@]|A|$]]|$1|L|3|M|5|G|7|10|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

In My Case, after a fews days of research,

All I did to revolve is listed below:

<ol>
<li>delete all the certificate on your keychain.</li>
<li>goto your apple account. a) download the specify certificate your want to install on your keychain. b)(Optional) Also create and download the require profile.</li>
<li>in Xcode, clean your project. This may take some time.</li>
<li>Build your project.</li>
</ol>

This should work for similar codesign issues.

Note, during this process the OS would ask for your credential validation.

blocks|key|335897|text|我使用Xamarin，对我来说，这是在尝试其他方法之后有效的方法。在Visual+Studio+for+Mac中，我打开了一个.xib文件，这样它就可以在Xcode中打开项目。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|335898|转到项目设置>签名和功能，选择团队，然后修复签名证书。|335899|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I use Xamarin and for me this is what worked after trying everything else.
In Visual Studio for Mac I've opened a .xib file so it opens the project in Xcode.
Went to the project settings &gt; Signing and Capabilities, selected the team and then fixed the Signing Certificate.

blocks|key|3104115|text|在终端中打开工程路径，在终端中输入以下命令|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3104116|1)+find。%7C+xargs+-0+xattr+-c|offset|length|style|BOLD|3104117|2)+xattr+-rc+.|3104118|这对我很有效。|3104119|entityMap^0|0|3|O|0|3|B|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@$D|S|E|T|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|M|$]]

Open the project path in terminal and enter the below commands in terminal

1) find . | xargs -0 xattr -c

2) xattr -rc .

This works for me.

I am attempting to deploy my first development iPhone app, and am running into some problems. I have successfully went though the online Provisioning Assistant, but now I am stuck. No matter what I do, I always get the following error.

<blockquote>
 /usr/bin/codesign failed with exit code 1
</blockquote>

Anyone have any ideas why this is happening?

/usr/bin/codesign failed with exit code 1

Visual Studio

Xamarin

Xcode

我正在尝试部署我的第一个开发iPhone应用程序，但遇到了一些问题。我已经成功地通过了online Provisioning Assistant，但现在我卡住了。无论我做什么，我总是得到以下错误。 /usr/bin/codesign失败，退出代码为%1有人知道为什么会发生这种事吗？

问/usr/bin/codesign失败，退出代码为%1
EN

回答 27

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问/usr/bin/codesign失败，退出代码为%1EN

回答 27

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问/usr/bin/codesign失败，退出代码为%1
EN