blocks|key|340417|text|打开密钥链访问，然后在文件菜单中选择锁定所有密钥链。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|340418|​|340419|📷|atomic|340420|340421|然后返回到Xcode并进行清理和重建。它将提示您再次输入密码以解锁密钥链。|340422|340423|340424|340425|在此之后，假设您没有其他编译问题，它将成功！|340426|340427|340428|340429|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/9d645bd07716dcb6454d9b2c58bb2388.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/13cf6930c47fb98cdb2295f7c906420c.png|2|https://developer.qcloudimg.com/http-save/yehe-900000/bba8b762810257e040445ddbb9f85d24.png^0|2|5|B|2|I|7|0|0|0|1|0|0|0|0|0|0|1|1|0|0|0|0|0|1|2|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@$9|19|A|1A|B|C]|$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1F|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|1G|8|@]|D|@$9|1H|A|1I|1|1J]]|E|$]]|$1|K|3|G|5|6|7|1K|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1L|8|@]|D|@]|E|$]]|$1|N|3|G|5|6|7|1M|8|@]|D|@]|E|$]]|$1|O|3|I|5|J|7|1N|8|@]|D|@$9|1O|A|1P|1|1Q]]|E|$]]|$1|P|3|G|5|6|7|1R|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1S|8|@]|D|@]|E|$]]|$1|S|3|G|5|6|7|1T|8|@]|D|@]|E|$]]|$1|T|3|I|5|J|7|1U|8|@]|D|@$9|1V|A|1W|1|1X]]|E|$]]|$1|U|3|G|5|6|7|1Y|8|@]|D|@]|E|$]]|$1|V|3|-4|5|6|7|1Z|8|@]|D|@]|E|$]]]|W|$X|$5|Y|Z|10|E|$11|12|13|-4]]|14|$5|Y|Z|10|E|$11|15|13|-4]]|16|$5|Y|Z|10|E|$11|17|13|-4]]]]

Open Keychain Access, then in the File menu select Lock All Keychains.

<img src="https://i.stack.imgur.com/dFPSl.png" width="399" />

Then go back to Xcode and clean and rebuild. It will prompt you for your password again to unlock the keychain.

<img src="https://i.stack.imgur.com/s4czg.png" width="529" />

After this, assuming you have no other compile issues, it will succeed!

<img src="https://i.stack.imgur.com/NOlbD.png" width="301" />

blocks|key|5363|text|当登录密钥链被锁定时就会发生这种情况。若要解锁登录密钥链，请运行：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5364|security+unlock-keychain+login.keychain|code-block|syntax|javascript|5365|如果您的密钥链受到密码保护，请使用-p选项指定密码：|offset|length|style|CODE|5366|security+unlock-keychain+-p+PASSWORD+login.keychain|5367|如果您使用的是连续集成系统，您可能希望通过环境变量/令牌注入密码，而大多数CI系统在其设置中都提供了该环境变量/令牌。|5368|所讨论的错误代码是苹果文档中的描述作为内部错误，因此在其他情况下也完全有可能发生这种情况。|5369|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/documentation/security/1542001-security_framework_result_codes/errsecinternalcomponent?language=objc^0|0|0|H|2|0|0|0|9|8|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|12|8|@$I|13|J|14|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|16|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|17|8|@]|9|@$I|18|J|19|1|1A]]|A|$]]|$1|S|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

This occurs when the login keychain is locked. To unlock the login keychain, run:
<pre><code>security unlock-keychain login.keychain
</code></pre>
If your keychain is password-protected, specify the password using the <code>-p</code> option:
<pre><code>security unlock-keychain -p PASSWORD login.keychain
</code></pre>
If you're using a continuous integration system, you'll likely want to inject the password via an environment variable/token, which most CI systems offer in their settings.
The error code in question is <a href="https://developer.apple.com/documentation/security/1542001-security_framework_result_codes/errsecinternalcomponent?language=objc" rel="noreferrer">described in Apple's docs</a> as an internal error, so it's entirely possible this occurs in other cases too.

blocks|key|340171|text|这似乎是代码签名机制中的一个错误，重新启动mac应该可以解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|340172|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|$]]

It seems like a bug in the code signing mechanism, restarting your mac should solve the problem

blocks|key|5498|text|在High+Sierra/Xcode+9.4.1上有相同的问题，所有签署的尝试都以errSecInternalComponent结尾|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5499|​|ordered-list-item|5500|进入密钥链访问|unordered-list-item|5501|转到登录密钥链|5502|选择“我的证书”类别|5503|找到您要签名的证书，并将其展开以查看密钥。|5504|双击键|5505|转到“访问控制”选项卡。|5506|更新密钥访问控制以“允许所有应用程序访问此项”|5507|5508|5509|另一种选择是：|5510|在mac终端上运行codesign命令，并“始终允许”/usr/bin/codesign访问密钥|5511|如果尝试从ssh/CI签名，您还需要运行
安全解锁-密钥链login.keychain
在尝试签署app包之前|5512|entityMap^0|1|B|D|B|15|N|0|1|1|1|1|1|1|1|1|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@$9|18|A|19|B|C]|$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1E|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|1F|8|@]|D|@]|E|$]]|$1|L|3|M|5|K|7|1G|8|@]|D|@]|E|$]]|$1|N|3|O|5|K|7|1H|8|@]|D|@]|E|$]]|$1|P|3|Q|5|K|7|1I|8|@]|D|@]|E|$]]|$1|R|3|S|5|K|7|1J|8|@]|D|@]|E|$]]|$1|T|3|U|5|K|7|1K|8|@]|D|@]|E|$]]|$1|V|3|W|5|K|7|1L|8|@]|D|@]|E|$]]|$1|X|3|-4|5|6|7|1M|8|@]|D|@]|E|$]]|$1|Y|3|G|5|6|7|1N|8|@]|D|@]|E|$]]|$1|Z|3|10|5|6|7|1O|8|@]|D|@]|E|$]]|$1|11|3|12|5|6|7|1P|8|@]|D|@]|E|$]]|$1|13|3|14|5|H|7|1Q|8|@]|D|@]|E|$]]|$1|15|3|-4|5|6|7|1R|8|@]|D|@]|E|$]]]|16|$]]

Had the same issue on <code>High Sierra</code>/<code>Xcode 9.4.1</code>, all attempts to sign ended in <code>errSecInternalComponent</code>

<ol>
<li><ul>
<li>Go to Keychain Access</li>
<li>Go to the login keychain </li>
<li>Select the category "My Certificates"</li>
<li>Find the certificate you're signing with and expand it to see the key. </li>
<li>Double click the key </li>
<li>Go to the "Access control" tab. </li>
<li>Update key access control to "Allow all applications to access this item"</li>
</ul></li>
</ol>

Alternatively:

run codesign command on mac terminal and "Always allow" /usr/bin/codesign access to key

<ol start="2">
<li>If trying to sign from ssh/CI you also need to run 

<pre><code>security unlock-keychain login.keychain
</code></pre>

before trying to sign app bundle</li>
</ol>

blocks|key|5166|text|我遇到了同样的问题，我重新启动了我的macOS，它可以工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5167|在中国一书中，我们在开发商之间有句话：|5168|一些小问题，仅仅是restart.Big问题，应该重新安装。|blockquote|5169|有时，上面的话会对你有很大的帮助！|offset|length|style|BOLD|5170|entityMap^0|0|0|0|0|H|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|R|8|@$I|S|J|T|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|N|$]]

I have met the same problem, I restart my macOS,and it works.

In China,we have a saying between developers:

<blockquote>
 Little problems,just restart.Big problems,should reinstall.
</blockquote>

Sometimes,the above saying will greatly help you!

blocks|key|5305|text|为了帮助其他人，我在codesign中遇到了一个codesign错误，因为我是通过ssh会话来运行macOS机器的。从macOS机器上的终端窗口运行相同的命令是有效的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5306|这大概是因为codesign需要从登录密钥链访问私钥。|5307|从同一会话运行security+unlock-keychain+login.keychain+(如克拉肯的回答所解释的)也应该有效。|5308|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/50538785/179715^0|A|8|O|8|0|6|8|0|7|13|1D|6|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@$9|12|A|13|1|14]]|E|$]]|$1|J|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

In case it helps someone else, I encountered an <code>errSecInternalComponent</code> error with <code>codesign</code> because I was running it over an ssh session to my macOS machine. Running the same command from a terminal window on the macOS machine itself worked.

Presumably this is because <code>codesign</code> needs access to the private key from the login keychain.

Running <code>security unlock-keychain login.keychain</code> (as explained by <a href="https://stackoverflow.com/a/50538785/179715">cbracken's answer</a>) from the same session also should work.

blocks|key|340611|text|正如@+command在其中一个注释中指出的，如果您在命令行env中。与Jenkins(我的例子)一样，您可能需要将密码传递给解决方案中提到的security-unlock命令。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|340612|所以不是用，|340613|security+unlock-keychain+login.keychain|code-block|syntax|javascript|340614|用途：|340615|security+unlock-keychain+-p+<login-keychain-password>+<path-to-login-keychain>|340616|其中路径到登录的密钥链可以是$HOME/Library/Keychains/login.keychain(my情况)或简单的login.keychain。|340617|entityMap^0|1Z|F|0|0|0|0|0|E|12|1Q|E|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|10|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|11|8|@$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@]|E|$]]|$1|S|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|T|$]]

As pointed out by @Equilibrium in one of the comments, if you are in command line env. like Jenkins(my case), you might need to pass the password to the security-unlock command mentioned in the solutions.

So instead of using,

<pre><code>security unlock-keychain login.keychain
</code></pre>

use:

<pre><code>security unlock-keychain -p &lt;login-keychain-password&gt; &lt;path-to-login-keychain&gt;
</code></pre>

where path-to-login keychain can be $HOME/Library/Keychains/login.keychain(my case) or simply login.keychain

blocks|key|1947036|text|对于任何从jenkins和ssh那里遇到这个问题的人来说：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1947037|很可能您还没有授权访问密钥链中的私钥，我试过了，但不确定为什么所有这些都不起作用：|1947038|使用-A或-T+/usr/bin/codesign安全导入-A文件|ordered-list-item|1947039|安全设置-密钥-分区-列表-S苹果-工具：，苹果：，协同设计：-s+-k+#{密码}+#{keychainPath}|1947040|将所有配置配置文件更改为UUID.mobileprovision，并将它们复制到jenkins服务器上的“~/Library/MobileDevice/+provisioning”|1947041|清理派生数据并重新启动jenkins服务器|1947042|确保默认的密钥链是登录密钥链，并解锁它。|1947043|最后以下列方式解决：|1947044|1.ssh+user@jenkinsServerIP+-L+5900:localhost:5900，登录到jenkins服务器|1947045|2.打开“vnc://localhost”|1947046|这将启动一个远程屏幕，如果你的詹金斯服务器允许.|1947047|然后打开keychain.app，将/usr/bin/codesign的访问权限授予私钥。|1947048|祝好运|1947049|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|14|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|15|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|16|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|17|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|18|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|19|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1A|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1B|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1C|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1D|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1E|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|11|$]]

for anyone that encountered this issue from jenkins and ssh:

high possibility that you have not granted access to the private key in keychain, i tried but not sure why all of these are not working:

<ol>
<li>security import .p12 file with -A or -T /usr/bin/codesign </li>
<li>security set-key-partition-list -S apple-tool:,apple:,codesign: -s -k #{password} #{keychainPath} </li>
<li>change all provisioning profile to [UUID].mobileprovision and copy them to '~/Library/MobileDevice/Provisioning\ Profiles' on jenkins server</li>
<li>clean derived data and reboot jenkins server</li>
<li>make sure default keychain is login keychain and unlocked it. </li>
</ol>

finally resolved by:

1.ssh [user]@[jenkinsServerIP] -L 5900:localhost:5900, log into jenkins server 

2.open 'vnc://localhost'

this will launch a remote screen, if your jenkins server allow this...

then open keychain.app to grant access of /usr/bin/codesign to the private key 

good luck

blocks|key|1947205|text|上面的解决方案对我没有任何作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1947206|为我解决问题.|1947207|第一次开放密钥链访问|ordered-list-item|1947208|然后选择登录并单击证书。|1947209|双击打开信任部分，并将“使用系统默认值”设置为“始终信任”|1947210|清除build文件夹并运行|1947211|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|R|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|S|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|T|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|N|$]]

Nothing work for me from the above Solution.
Fallowing Solution Work for me...
<ol>
<li>First Open Keychain Access</li>
<li>Then Select Login And click Certificates</li>
<li>Double click Apple Worldwide Developer Relations Certificate Authority
Open trust section, and set to &quot;Use System Defaults&quot; from &quot;Always Trust&quot;</li>
<li>Clean the build folder and run</li>
</ol>

blocks|key|1946959|text|我运行了security+unlock-keychain+login.keychain，我的登录密码不起作用。所以我重新启动了，然后又运行了Xcode，它成功了。运行该命令也同样有效。奇怪的问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1946960|entityMap^0|4|13|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I ran <code>security unlock-keychain login.keychain</code> and my login password didn't work. So I rebooted, and then just ran Xcode again and it worked. Running the command works as well. Strange issue.

blocks|key|5524|text|如果尝试从ssh签名，请运行命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5525|security+unlock-keychain+login.keychain|code-block|syntax|javascript|5526|在尝试签署app包之前|5527|或来自UI|5528|更新密钥访问控制以“允许所有应用程序访问此项”|5529|Thx到“平衡”和“Jon+McClung”|5530|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

If trying to sign from ssh run command:

<pre><code>security unlock-keychain login.keychain
</code></pre>

before trying to sign app bundle

or from UI

Update key access control to "Allow all applications to access this item"

Thx to @Equilibrium and @Jon McClung

blocks|key|1946932|text|我也有过同样的问题，发现问题是代码签名应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1946933|Opened+the+developer+account+and+accepted+the+updated+agreement+and+it+worked.++|code-block|syntax|javascript|1946934|​|1946935|📷|atomic|offset|length|1946936|1946937|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/395adb7608580f64e5e3d62c87d23093.png|imageAlt^0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Y|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Z|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|10|8|@]|9|@$L|11|M|12|1|13]]|A|$]]|$1|N|3|H|5|6|7|14|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V|W|-4]]]]

I had the same issue Found out the problem is with code signing the app. 

<pre><code>Opened the developer account and accepted the updated agreement and it worked. 
</code></pre>

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

blocks|key|5417|text|右键单击键链中与协同设计证书相关的私钥，然后单击“允许所有应用程序”，而不是依赖提示符为我修复它，因为构建是通过ssh进行的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5418|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|$]]

Right clicking on the private key associated with the codesigning cert in the keychain, and then clicking on 'allow all applications' instead of relying on a prompt fixed it for me, since the build was happening via ssh.

blocks|key|340772|text|我不得不：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|340773|1)删除与项目关联的证书|340774|2)返回到Xcode并撤消应用程序证书|340775|3)+Xcode需要一个新的证书|340776|4)锁定所有KeyChain|340777|5)清洁项目|340778|6)重建|340779|就这样。希望这对任何人都有帮助。|340780|entityMap^0|0|0|0|0|0|0|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|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

I had to:

1) delete the certificate associated to the project

2) Back to the Xcode and revoke the app certificate

3) The Xcode require a new certificate

4) Lock all KeyChain

5) Clean the project

6) Rebuild

That's it. Hope it helps to anyone.

blocks|key|340894|text|如果你得到了errSecInternalComponent之后|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|340895|Warning:+unable+to+build+chain+to+self-signed+root+for+signer+…|code-block|syntax|javascript|340896|，您可能在密钥链中有错误的证书。在这种情况下，请确保导入与开发人员证书签名的WWDR证书。我导入了在2023年到期的WWDR证书，两个小时后我终于意识到它不起作用，因为我的开发人员证书已经与2030年到期的WWDR证书签署了(AppleWWDRCAG3.cer)。下载网页：https://www.apple.com/certificateauthority/|340897|entityMap|0|LINK|mutability|MUTABLE|url|https://www.apple.com/certificateauthority/^0|6|N|0|0|3T|17|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|M|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

If you get <code>errSecInternalComponent</code> after
<pre><code>Warning: unable to build chain to self-signed root for signer …
</code></pre>
, you might have the wrong Apple World Wide Developer Relations root certificate in your keychain. In this case, make sure that you import the WWDR certificate with which your developer certificate was signed. I imported the WWDR certificate expiring in 2023 and two hours later finally realized that it didn't work because my developer certificate had been signed with the WWDR certificate expiring in 2030 (AppleWWDRCAG3.cer). Download page: <a href="https://www.apple.com/certificateauthority/" rel="nofollow noreferrer">https://www.apple.com/certificateauthority/</a>

blocks|key|1947335|text|发布一个我们最终不得不求助的解决方案，以防其他人没有东西去尝试……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1947336|在我们的“登录”密钥链中安装了一个新的Apple分发证书之后，我们的Jenkins工作突然开始失败，iOS应用程序也出现了相同的errSecInternalComponent错误：|1947337|Command+/usr/bin/codesign+failed+with+exit+code+1|offset|length|style|CODE|1947338|我们的构建管道调用security+unlock-keychain，我们的EnterpriseDistributioncert(就在几周前碰巧更新并安装在同一个密钥链中)没有问题，解锁就像预期的那样工作。|BOLD|1947339|在尝试了这个线程和其他地方提到的所有常规操作之后，我们在一个新的终端窗口中以Jenkins用户的身份手动运行codesign，使用与Jenkins日志中的相同的命令：/usr/bin/codesign+--force+--sign...|1947340|这促使输入密码来解锁密钥链，我们这样做了，然后选择“始终允许”。|1947341|在那之后，詹金斯如愿以偿地签了名。|1947342|这显然有点麻烦，因为我们可能不得不在证书过期时再次执行此操作，而且非常奇怪的是，企业证书的解锁工作，而不是用于通过App分发的证书.他们实际上是共用同一条管道。|1947343|entityMap^0|0|0|0|1D|0|9|O|2F|F|0|0|3A|2B|Z|0|0|W|0|0|H|0|0|28|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@$F|Z|G|10|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@$F|12|G|13|H|I]|$F|14|G|15|H|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|16|8|@$F|17|G|18|H|L]|$F|19|G|1A|H|I]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1B|8|@$F|1C|G|1D|H|L]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1E|8|@$F|1F|G|1G|H|L]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1H|8|@$F|1I|G|1J|H|L]]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|V|$]]

Posting a work-around that we finally had to resort to, in case someone else is running out of things to try...
After installing a new Apple Distribution certificate in our &quot;login&quot; keychain, our Jenkins job suddenly started to fail singning iOS apps with the same errSecInternalComponent error:
<code>Command /usr/bin/codesign failed with exit code 1</code>
Our build pipeline calls <code>security unlock-keychain</code>, and we have no problems with our Enterprise Distribution cert (which was coincidentally updated and installed in the same Keychain just a few weeks prior), where the unlocking works as expected.
After trying all the usual things mentioned in this thread and elsewhere, we ended up running codesign manually as the Jenkins user in a new Terminal window, taking the exact same command as found in the Jenkins log: <code>/usr/bin/codesign --force --sign...</code>
This prompted entering the password to unlock the Keychain, which we did, and then selected &quot;Always Allow&quot;.
After that Jenkins manages to sign (as expected).
This is obviously a bit of a work-around since we might have to do this again when the cert has expired, and it's really strange that unlocking works for Enterprise certs, but not the cert used for distributing through App Store... They literally share the same pipeline.

blocks|key|1946910|text|只需使用mac终端尝试一次，而不是使用ssh会话。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1946911|security+unlock-keychain+login.keychain|code-block|syntax|javascript|1946912|并在提示对话框中选择“始终允许”。然后，您可以在远程会话中构建xcodebuild。|1946913|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Just try it once using mac terminal but not from ssh session

<pre><code>security unlock-keychain login.keychain
</code></pre>

And choose always allow in the prompted dialog.
And then you could xcodebuild in the remote session.

blocks|key|340818|text|以上的方法对我来说是无用的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|340819|我通过以下方式解决了这一问题：|340820|打开钥匙链访问。|ordered-list-item|340821|单击“登录”菜单。|340822|删除所有个人证书。|340823|清理这个项目。|340824|重建。|340825|就这样。希望这对任何人都有帮助。|340826|entityMap^0|0|0|0|0|0|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|@]|A|$]]|$1|G|3|H|5|F|7|V|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|W|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|X|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|Y|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Z|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|R|$]]

The above methods are useless to me.

I resoled it by:

<ol>
<li>Open keychain access.</li>
<li>Click Login Menu.</li>
<li>Remove all personal certificates.</li>
<li>Clean the project.</li>
<li>Rebuild.</li>
</ol>

That's it. Hope it helps to anyone.

blocks|key|5681|text|在我的案子中，这个问题解决了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5682|xcode+->+preferences+->+accounts+->+select+the+account+->+manage+certificate+->+(%2B)+in+bottom+left+->+Apple+development|offset|length|style|CODE|5683|参考文献：https://stackoverflow.com/a/62646138/234110|5684|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/62646138/234110^0|0|0|3B|0|5|17|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

In my case, this solved.
<code>xcode -&gt; preferences -&gt; accounts -&gt; select the account -&gt; manage certificate -&gt; (+) in bottom left -&gt; Apple development</code>
Ref: <a href="https://stackoverflow.com/a/62646138/234110">https://stackoverflow.com/a/62646138/234110</a>

blocks|key|5665|text|在我的例子中，BUCK试图为development签署IPA，但是没有安装任何开发证书。将构建配置更改为release+(这是我所需要的--为iTunes构建)，为我修复了它。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5666|entityMap^0|E|B|1G|7|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

In my case BUCK was trying to sign the IPA for <code>development</code>, but there were not any development certificates installed. Changing the build config to <code>release</code> (this is what I needed - to build for iTunes) fixed it for me.

blocks|key|1947234|text|只是想提醒一下，如果有人面临类似的问题，我所做的。在我的例子中，我的apple+dev和分发证书、密钥和配置配置文件都是最新的。我的iOS代码构建在用户模式下工作，没有任何问题，但是当代码构建以根权限运行时(即%25+sudo或通过命令行使用sudo调用Xcode+)，由于代码符号问题，它无法工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1947235|因此，我复制了相应的工作证书，并将登录密钥输入到密钥链工具中的系统位置。然后，它开始工作，没有任何代码签名问题。|1947236|同样，我们可以导出所需的证书，从工作机器生成的密钥，并将这些密钥导入非工作机器的密钥链工具可以解决这个问题。|1947237|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|$]]

Just wanted to callout if someone face similar issue what I did. In my case my apple dev and distribution certificates, keys and provisioning profiles where upto date. My iOS code build was working in user mode without any issue however it does not work due to code sign issue when the code build runs with root privileges i.e. % sudo or invoking the Xcode using sudo through command line.
So, I copied the corresponding working certificates and keys the login to the system location in the keychain tool. Then it started working without any code sign issue.
Similarly, we can export the required certificates, keys for build from the working machine and import those into non working machine's keychain tool may solve the issue.

blocks|key|1947364|text|对我来说，在直接使用Mac或VNC时，我可以对文件进行签名，但不能通过ssh签名。我想这一定与访问密钥链中的证书有关。我已经在做security+unlock-keychain+[keychain+name]了，但这看起来还不够好。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1947365|最后为我修复的是(在直接/VNC连接中，而不是ssh)：|1947366|确保您的证书所在的密钥链已锁定。关闭密钥链访问。|ordered-list-item|1947367|开放终端|1947368|不要运行security+unlock-keychain+[keychain+name]。|1947369|使用codesign工具运行签名过程。您将被问到密钥链的密码。|1947370|输入密码并单击“始终允许”|1947371|从现在开始，我可以通过ssh使用codesign，只要我在命令之前包含了security+unlock-keychain+[keychain+name]。|1947372|entityMap^0|1S|14|0|0|0|0|4|14|0|2|8|0|0|G|8|10|14|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|10|8|@]|D|@]|E|$]]|$1|K|3|L|5|J|7|11|8|@]|D|@]|E|$]]|$1|M|3|N|5|J|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|O|3|P|5|J|7|15|8|@$9|16|A|17|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|J|7|18|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|19|8|@$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|V|$]]

For me, I was able to sign files when using the Mac directly or via VNC, but not via ssh. I figured it must be something to do with access to the certificate within the keychain. I was already doing a <code>security unlock-keychain [keychain name]</code> but this didn't appear good enough.
What finally fixed it for me was (within a direct/VNC connection, not ssh):
<ol>
<li>Make sure the keychain in which your certificate resides is locked. Close Keychain Access.</li>
<li>Open Terminal</li>
<li>Do not run <code>security unlock-keychain [keychain name]</code>.</li>
<li>Run a signing process using <code>codesign</code> tool. You will be challenged for a password to the keychain.</li>
<li>Enter the password and click &quot;Always allow&quot;</li>
</ol>
From now on I was able to use <code>codesign</code> via ssh, so long as I included <code>security unlock-keychain [keychain name]</code> before the command.

blocks|key|341013|text|如果您的密钥链中有一个具有相同名称的代码签名证书，请确保删除它。我有一个XCode报告说的“丢失私钥”。在codesign使用正确的证书之前，我必须通过密钥链访问来删除它。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|341014|entityMap^0|1H|8|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

If you have a code signing certificate with the same name in the keychain, make sure you remove it. I had one which XCode reported as &quot;Missing private key&quot;. I had to remove it via Keychain Access before the correct certificate was used by <code>codesign</code>.

I am trying to add new provisioning profile to my Xcode, to test an app on the device. Here are the steps I followed:

<ol>
<li>Deleted all certificates and provisioning profiles</li>
<li>Create/Add IOS Dev Certificate </li>
<li>Add My IOS Device Online</li>
<li>Create IOS Provisioning Profile </li>
<li>Add IOS Provisioning Profile </li>
<li>Clean App</li>
<li>Build Then Run App</li>
<li>Set Codesigning nd Provisioning Profile In Build Settings</li>
<li>Lots of Googling > to no successes </li>
</ol>

Here is the error I get:

<pre><code>CSSM_SignData returned: 800108E6
/Users/alexpelletier/Library/Developer/Xcode/DerivedData/MyExpense-efnqzvoqwngzcmazaotyalepiice/Build/Products/Debug-iphoneos/MyExpense.app: errSecInternalComponent
Command /usr/bin/codesign failed with exit code 1
</code></pre>

Xcode Command /usr/bin/codesign failed with exit code 1 : errSecInternalComponent

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我试图在我的Xcode中添加新的配置文件，以便在设备上测试一个应用程序。以下是我遵循的步骤：删除所有证书和配置配置文件创建/添加IOS开发证书在线添加我的IOS设备创建IOS配置配置文件添加IOS配置配置文件清洁应用程序构建然后运行应用程序在生成设置中设置协同设计和供应配置文件很多谷歌搜索>没有成功下面是我遇到的错误：CSSM_SignData returned: 800108E6/Users/a

问Xcode命令/usr/bin/codesign失败，退出代码1: errSecInternalComponent
EN

回答 23

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Xcode命令/usr/bin/codesign失败，退出代码1: errSecInternalComponentEN

回答 23

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Xcode命令/usr/bin/codesign失败，退出代码1: errSecInternalComponent
EN