blocks|key|228481|text|我试着用iPhone5运行项目，但是应用程序扩展不支持32位architecture.So当我用iPhone5S构建项目时，我可以构建这个项目！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|228482|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 tried to run project in iPhone5,but App Extension does'nt support 32-bit architecture.So When I build project in iPhone5S,I can build the project !

blocks|key|178237|text|我必须在“目标”下选择我的应用程序，然后转到“功能”选项卡，然后在“应用程序组”部分下单击“修复问题”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|178238|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 to select my app under 'Targets', then go to the 'Capabilities' tab and click 'Fix Issues' under the 'App Groups' section

blocks|key|178454|text|我在代码签名中有不一致之处。我的扩展程序和主应用程序选择了不同的证书。一旦我将这两种方法都设置为使用发行版，它就能正常工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|178455|​|178456|📷|atomic|offset|length|178457|178458|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/3ff0e8babaa91ca802d6cf490e9d112b.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]]]]

I had discrepancies under Code Signing. My Extension and Main app had different certificates selected. Once I set both to use distribution it worked fine.

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

blocks|key|232422|text|在使用WatchKit的情况下，确保在Watch+App设置(+General+>+Signing+>+Team)中选择了正确的"Team“。我已经设置了手机应用程序的团队，而不是手表应用程序的团队。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|232423|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|$]]

In the case of using WatchKit, make sure that your Watch App has the correct "Team" selected in the Watch App Target settings (under General > Signing > Team). I had set the phone app's team, but not the watch app's team.

blocks|key|178390|text|如果您的Xcode运行良好，但在向项目中添加扩展目标后停止工作，那么大多数情况下，您的应用程序是使用一个旧的证书(仍然使用您的名称等)签名的，而您的扩展名是用一个新的证书签名的，证书上有扩展的权限。这就是错误的原因。在这种情况下，您很可能有两个同名的证书，您可以这样做：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|178391|1.Go+to+Xcode->Preference;+2.选择帐户选项卡；|offset|length|style|CODE|178392|选择您的苹果ID，然后单击查看详细信息；|ordered-list-item|178393|在“签名身份”列表窗口下，选择“IOS开发”，然后单击“小配置”图标，然后选择“撤消”；|178394|然后Xcode将尝试下载一个新的证书。
您可以在此之后进行干净的构建，以便您的应用程序和扩展都将使用新的证书进行签名。|178395|178396|178397|📷|atomic|178398|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/9fc127ae3dc664d32da11aa0ebe656bc.jpg|imageAlt^0|0|0|Q|0|0|0|0|0|0|0|1|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@$D|14|E|15|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|16|8|@]|9|@]|A|$]]|$1|K|3|L|5|J|7|17|8|@]|9|@]|A|$]]|$1|M|3|N|5|J|7|18|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|1B|8|@]|9|@$D|1C|E|1D|1|1E]]|A|$]]|$1|T|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10|11|-4]]]]

If your Xcode has been working fine but stopped working after you add an extension target to your project, most of the time is that your app was signed using a older certificate (still valid with your name etc.), while your extension is signed with a newer certificate with entitlement for the extension. This is why the error. In this case, you most likely have two certificates with the same name, and this what you can do: 
<code>1.Go to Xcode-&gt;Preference;
</code>2. Select Accounts Tab; 
3. Select your Apple ID then click on View Details; 
4. Under signing Identities List Window, select IOS Development, then click on the 
little Configuration icon, and select Revoke; 
5. Xcode will then try to download a new certificate. 
You can do a clean build after this so both your app and extension will be signed using the new certificate. 
<img src="https://i.stack.imgur.com/IVwad.jpg" alt="enter image description here">

blocks|key|228484|text|我通过删除我在|type|unstyled|depth|inlineStyleRanges|entityRanges|data|228485|Preferences+->+Accounts|code-block|syntax|javascript|228486|然后再用我的Apple登录|228487|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|$]]

I solved it by deleting my Apple ID account in

<pre><code>Preferences -&gt; Accounts
</code></pre>

and then logging back in again with my Apple ID

blocks|key|178324|text|我在Xcode+6中也有同样的问题，但在我的例子中，这是因为有两个active+developer证书。撤销一个已经解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|178325|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 issue in Xcode 6, but in my case it occured because of having two active developer certificates. Revoking one had fixed the issue.

blocks|key|5292024|text|这一问题可能会出现在这样的情况下，即嵌入的应用程序目标(如扩展或watchapp+)没有在General部分中选择匹配的iOS+team作为主iOS应用程序。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|5292025|为所有相关目标选择合适的团队，为我解决这个问题。|5292026|entityMap^0|19|7|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

This issue might arise in the case where the embedded app targets like extensions or watchapp does not have the matching team selected in the General section, as the main iOS app.

Selecting the right team for all relevant targets fixed the issue for me.

blocks|key|228750|text|我也有过类似的问题。对我来说，这是一张证书，上面写着“由身份不明的权威签署”。我遵循了以下步骤，解决了这一问题。问题是缺少苹果WWDR中间证书。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|228751|我们还必须安装由苹果公司全球开发者关系颁发的WWDR中间证书。它可以从门户网站下载，也可以直接在http://developer.apple.com/certificationauthority/AppleWWDRCA.cer下载，并确保将其添加到您的密钥链中。|offset|length|228752|要添加证书:在Mac计算机上打开密钥链实用软件，然后转到File→Import，然后选择→。|228753|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.apple.com/certificationauthority/AppleWWDRCA.cer^0|0|1C|1T|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

I had a similar issue. For me the issue was with the certificate showing, 'signed by unknown authority'. I had followed the below steps and it is resolved.
The problem was missing apple WWDR intermediate certificate.

We must also install the WWDR intermediate certificate issued by Apple’s worldwide developer relations. It can be downloaded from the portal or directly at <a href="http://developer.apple.com/certificationauthority/AppleWWDRCA.cer">http://developer.apple.com/certificationauthority/AppleWWDRCA.cer</a> Make sure you add this to your keychain as well.

To add the certificate: open your keychain utility software on your Mac computer, then go to File→Import items, then select AppleWWDRCA.cer.

blocks|key|5292476|text|这个问题可能有很多原因。如果其他的答案对你都没有用确保您正在签名的证书没有“始终信任”(如果设置是这样的，您将看到绿色的“%2B”标志)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5292477|进入密钥链访问，双击正在使用的证书。|ordered-list-item|5292478|从“始终信任”展开“信任”，并将其更改/设置为“使用系统默认值”。|5292479|5292480|5292481|如果您在项目中使用Swift作为“始终信任”设置中断了相关的Swift库，则尤其如此。|5292482|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|O|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|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|$]]

There are quite a few reasons the issue may emanate from. If none of the other answers are working for you - would like to add another plausible check that helped me. Ensure the certificate you are signing with doesn't have 'Always Trust' (you will see a green '+' sign if the setting is such).

<ol>
<li>Go to Key Chain access, double click on the certificate you are using.</li>
<li>Expand the 'Trust' drop down and change/set to 'Use System Defaults' from 'Always Trust'.</li>
</ol>

It's especially true if you are using Swift in your project as the 'Always Trust' setting breaks pertinent Swift libraries.

blocks|key|178240|text|您需要为该目标创建供应配置文件，并确保其中包含相同的证书。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|178241|目标有自己的捆绑id，您也需要创建一个AppId。这解决了和你一样的问题。|178242|最好的|178243|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|$]]

You need to create Provisioning Profile for that target and make sure to include the same certificate in it. 

Targets has their own bundle id se you will need to create an AppId also.
This solved the same problem that you are having

best

blocks|key|178259|text|只需让Xcode处理供应工作即可。这解决了我的案子中同样的问题。http://aplus.rs/2014/embedded-binary-is-not-signed-with-the-same-certificate-as-the-parent-app/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|178260|entityMap|0|LINK|mutability|MUTABLE|url|http://aplus.rs/2014/embedded-binary-is-not-signed-with-the-same-certificate-as-the-parent-app/^0|W|2N|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]]]]

Just let Xcode handle the provisioning work. This solved the same issue in my case. <a href="http://aplus.rs/2014/embedded-binary-is-not-signed-with-the-same-certificate-as-the-parent-app/" rel="nofollow">http://aplus.rs/2014/embedded-binary-is-not-signed-with-the-same-certificate-as-the-parent-app/</a>

blocks|key|232333|text|如果这对任何人都有帮助的话，我的解决办法是在提交到商店时更新我的存档方案，以供发布，但从未将其更改为adhoc进行测试。编辑我的档案计划来使用临时工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|232334|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|$]]

In case this helps anyone, my fix was that I had updated my archive scheme for release when submitting to the store, but never changed it back to adhoc for testing. Editing my archive scheme to use ad hoc worked.

blocks|key|232417|text|当我遇到这个问题时，我去了苹果成员中心，并意识到我创建的配置文件(用于扩展)被标记为“无效”。我只是用与应用程序签名相同的证书重新创建了供应配置文件，然后通过Xcode+>+Preferences+>+Account+>+refresh下载了它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|232418|一旦我有了新的配置文件，我就在构建设置中选择了它们。我选择了刚才创建的供应配置文件，并在构建设置中的代码签名实体中选择了相应的证书，并解决了问题。|232419|请注意，扩展有自己的应用程序id，因此也有自己的配置文件。|232420|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|$]]

When I had this issue I went to the Apple Member Center and realized that the Provisioning Profile (for the extension) that I had created was marked as 'Invalid'. I just re-created the Provisioning Profile with the same certificate that the app is signed with and then downloaded it via Xcode > Preferences > Account > refresh.

Once I had the new provisioning profiles I selected them in the build settings. I selected the provisioning profile that was just created and also selected the corresponding certificate in the Code signing entity in the build settings and that fixed the issue.

Note that the extension has its own app id and hence its own provisioning profile.

blocks|key|179012|text|对于Xcode+8+beta+3|type|unstyled|depth|inlineStyleRanges|entityRanges|data|179013|在我的Xcode项目文件中的不同目标上，我的版本号被关闭了。|179014|​|179015|📷|atomic|offset|length|179016|179017|我的iOS目标有一个构建版本3，但我的手表应用程序目标和共享扩展目标都有构建版本1。|179018|179019|179020|179021|我所做的就是匹配所有目标的构建号(将它们全部更改为3)，并解决了这个问题。|179022|希望这能有所帮助。|179023|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/801ed159d8be172b748bef9d19686338.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/a12accc5e9439c3239230fd7f31a8fe4.png^0|0|0|0|0|1|0|0|0|0|0|0|1|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|16|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|17|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|18|8|@]|9|@$I|19|J|1A|1|1B]]|A|$]]|$1|K|3|E|5|6|7|1C|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1D|8|@]|9|@]|A|$]]|$1|N|3|E|5|6|7|1E|8|@]|9|@]|A|$]]|$1|O|3|G|5|H|7|1F|8|@]|9|@$I|1G|J|1H|1|1I]]|A|$]]|$1|P|3|E|5|6|7|1J|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1K|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1L|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11|12|-4]]|13|$5|X|Y|Z|A|$10|14|12|-4]]]]

For Xcode 8 beta 3

My build numbers were off on my different Targets in my Xcode project file.

<a href="https://i.stack.imgur.com/FwhHr.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/FwhHr.png" alt="iOS Target showing &quot;Build 3&quot;"></a>

My iOS target had a build version 3, but my watch app target and my share extension target both had build version 1.

<a href="https://i.stack.imgur.com/kwLQJ.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/kwLQJ.png" alt="Thingy Watch target showing build number 1, does not match iOS target build number."></a>

All I did was match all the targets' build numbers (changed them all to 3) and it fixed the issue.

Hope this helps.

blocks|key|5292159|text|刷新我的配置文件，为我修复它(首选项->帐户->双击帐户->点击左下角的刷新按钮)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5292160|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|$]]

Refreshing my provisioning profiles fixed it for me (Preferences -> Accounts -> Double tap the account -> tap refresh button in lower left)

blocks|key|5292173|text|打开您的密钥链，它是苹果全球开发人员关系认证机构，如果我选择始终信任，则Xcode存档失败。当我更改为系统默认值时，Xcode归档成功。是的，你会喜欢的！！|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|5292174|entityMap^0|A|E|U|4|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|$]]

Open your key chain and It's the Apple Worldwide Developer Relations Certification Authority, if I choose always trust, Xcode archives failed. When I changed to system defaults, Xcode archives successfully. Yes you will enjoy!!

blocks|key|5292196|text|由于某种原因，我的开发人员证书两次存储在我的密钥链中。删除其中一个解决了问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5292197|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|$]]

For some reason, my developer certificate was stored in my keychain twice. Deleting one of them fixed the issue.

blocks|key|5292236|text|我也有同样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5292237|因此，我为WatchKit应用程序的每个包ID和配置做了准备工作：|5292238|手表应用程序开发|unordered-list-item|5292239|手表扩展开发|5292240|手表应用程序制作|5292241|表伸戳|5292242|5292243|5292244|/!\注意，因为开发人员门户中的监视应用程序的应用ID类似于：|5292245|com.example.projectname.watchkitapp.watchkitextension|5292246|当我创建watchkit应用程序时，Xcode中的包ID是：|5292247|com.example.projectname.watchkitapp|5292248|也许这是自WatchOS+2.0以来发生的一些变化。|5292249|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|12|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|13|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|14|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|15|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|18|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|19|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1A|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1B|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1C|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|Z|$]]

I had got the same issue.

So I did a provisioning profil for each bundle ID and configuration of the WatchKit App :

<ul>
<li>Watch App Development</li>
<li>Watch Extension Development</li>
<li>Watch App Production</li>
<li>Watch Extension Prod</li>
</ul>

/!\ Be careful because the app ID of the watch app in the developer portal is something like :

com.example.projectname.watchkitapp.watchkitextension

and when i created the watchkit app the bundle ID in Xcode was :

com.example.projectname.watchkitapp

maybe it something which changed since WatchOS 2.0.

blocks|key|178642|text|我不得不去：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|178643|Xcode->+preferences+->+preferences+->+Account+->+View+->选择所有供应配置文件->按下键盘上的DEL键，删除完成后按下下载所有按钮！|178644|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 to go to:

Xcode-> preferences -> Accounts -> View Details -> select all Provisioning Profiles -> press DEL-key on keyboard after deletion is completed press Download All button!

blocks|key|232538|text|我在Xcode+7.1中的一个应用程序也有同样的问题。该应用程序有一个手表扩展，因此是一个应用程序集团。对我有用的是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|232539|转到~/Library/MobileDevice/Provisioning+Profiles|ordered-list-item|offset|length|style|CODE|232540|删除其中列出的所有供应配置文件|232541|转到Safari中的iOS开发中心并重新生成所有供应配置文件|232542|返回到Xcode+=>+Preferences+=>+Apple，并选择与应用程序关联的Apple|232543|点击“查看细节.”(右下角)|232544|下载刚创建的配置文件|232545|再清洁再建|232546|232547|232548|我相信我的配置文件被混淆了，因为我使用了Xcode的“自动修复”功能来解决我与=>相关域的另一个问题。|232549|entityMap^0|0|2|18|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@$E|12|F|13|G|H]]|9|@]|A|$]]|$1|I|3|J|5|D|7|14|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|15|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|16|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|17|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|18|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|19|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1C|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|Z|$]]

I had the same issue with an app in Xcode 7.1. The app had a Watch extension and therefore an App Group. What worked for me was to:

<ol>
<li>Go to <code>~/Library/MobileDevice/Provisioning Profiles</code></li>
<li>Delete all provisioning profiles listed there</li>
<li>Go to the iOS Dev Center in Safari and regenerate all provisioning profiles</li>
<li>Go back to Xcode => Preferences => Apple IDs and choose the Apple ID associated with the app</li>
<li>Click "View Details..." (lower right)</li>
<li>Download the provisioning profiles that were just created</li>
<li>Clean and build again</li>
</ol>

I believe my provisioning profiles got mixed up because I was using Xcode's "fix automatically" feature for another issue I had with Capabilities => Associated Domains.

blocks|key|5292310|text|打开mac上的KeyChain访问，删除另一个证书，该证书与您自己的certificate.This问题不同，通常是在您在Xcode中的另一个帐户中登录后出现的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5292311|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|$]]

Open KeyChain Access on your mac, delete the other one certificate that is diff from your own certificate.This issue was general appeared after you loged in another account in your Xcode.

blocks|key|178745|text|我也面临同样的问题，我通过以下程序解决了这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|178746|首先，我要创建我的团队开发证书(因为我们更新了根证书)|178747|2、编辑Iphone开发证书，确保包含您刚刚创建的证书。|178748|3、对watchkit扩展和观看工具包应用程序做了相同的操作|178749|4转到Xocde“、"，双击”、名称“，删除Iphone、监视应用程序、、的旧证书。|178750|5、下载您的新证书并安装。|178751|那就成功了。|178752|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

I faced the same issue too, I solved it by the procedure as follows:

First, I re Create my team develop certificate(Because we renewed our root certificate) 

2、 edit the Iphone Apps develop certificate ,be sure include your certificate you just create.

3、doing same to the watchkit extension And watch kit App

4、go to Your Xocde "Preference ", double click your "Team Name",delete the old Certificate of Iphone 、watchApps、 watchExtention

5、download your new certificate and install.

Then it works.

blocks|key|5292359|text|在我的例子中，我的应用程序和我的Widget配置文件是用不同的证书签名的。因此，我不得不转到iOS开发者站点，选择父应用程序提供配置文件->Edit，并选择与小部件相同的证书。然后单击“生成”和“下载”。您已经下载了它，双击它可以安装在XCode中。然后在Build+>Provisionig配置文件中为父应用程序选择新的配置文件。最后重建你的项目！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5292360|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|$]]

In my case my App and my Widget profile were signed with different certificate. 
So I had to go to to iOS Developer site, select parent app provisioning profile->Edit and choose the same certificate as the widget. 
Then click "generate" and "download". Onece you have download it, double click on it to install in XCode.
Then select the new provisioning profile for your parent app in Build Settings->Provisionig Profile.
Finally Rebuild your project!

blocks|key|178774|text|对我来说，这是因为我的一些配置文件过期了。在developer.apple.com上创建新的配置文件，删除旧的配置文件，将它们设置为Xcode中的自动配置文件，然后错误就消失了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|178775|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|$]]

For me this was happening because some of my provisioning profiles were expired. Created new profiles on developer.apple.com, removed the old ones, set them to Automatic in Xcode, and the error went away.

blocks|key|228791|text|在我的例子中，我的扩展目标使用的概要文件包含的证书与父目标所包含的配置文件不同。这正是抱怨的错误信息！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|228792|原因是我为扩展配置文件生成了一个新的证书。|228793|因此，登录到developer.apple.com，看看这些配置文件是否包含不同的证书。|228794|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|$]]

In my case the profile my extension target uses contains different certificates than the profile the parent target uses contains. This was exactly the error messages complained about!

The reason was I generated a new certificate for the extension profile. 

So log in to developer.apple.com to see if these profiles contains different certificate.

blocks|key|232710|text|整整一天之后，“苹果全球开发者关系认证机构”在“根证书”中被删除了。我从另一台机器导出一台并安装，一切正常。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|232711|entityMap^0|8|D|U|3|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|$]]

After a whole day it turns out "Apple Worldwide Developer Relations Certification Authority" in the Root Certs had been deleted. I export one from another machine and installed, everything works fine.

blocks|key|179073|text|如果您正在使用任何扩展(在我的例子中，我使用的是OneSignal扩展)，在这种情况下，您的父应用程序包将是com.app.xyz，但是对于扩展/小部件，您的包id将是com.app.xyz.extension。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|179074|因此，我们将创建一个带有包标识符com.app.xyz.extension的应用程序id，并为该应用程序id创建配置文件。|179075|我们将使用与父应用程序相同的开发和生产证书。|179076|下面是链接，它可以帮助provisioning+profile+for+a+widget|offset|length|179077|最后，我不使用自动设置。因此，我手动设置了配置配置文件和证书。|179078|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/25837722/provisioning-profile-for-today-widget-extension^0|0|0|0|B|X|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|@$H|X|I|Y|1|Z]]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

If you are using any extension (in my case I was using OneSignal Extension) in that case your parent app bundle will be com.app.xyz but for extension/widget your bundle id would be com.app.xyz.extension

So we will create an app id with the bundle identifier com.app.xyz.extension and we will create provisioning profiles for this app id.

We would use same development and production certificates which we used for parent app.

Here is link which can be helpful <a href="https://stackoverflow.com/questions/25837722/provisioning-profile-for-today-widget-extension">provisioning profile for a widget</a>

Finally I am not using automatic settings. So I set my provisioning profiles and certificates manually

blocks|key|232743|text|检查所有目标，逐个选择并单击签名和功能->选择小组，然后按照配置配置文件进行构建设置->签名设置，然后//:+PROVISIONING_PROFILE+=+Debug|type|unstyled|depth|inlineStyleRanges|entityRanges|data|232744|//:配置=发布PROVISIONING_PROFILE+=|232745|//:完全设置=一些PROVISIONING_PROFILE|232746|📷|atomic|offset|length|232747|​|232748|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/c977afe2c24388b19a4cd6531d897403.png|imageAlt^0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|Y|8|@]|9|@$I|Z|J|10|1|11]]|A|$]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T|U|-4]]]]

Check All targets select one by one and click signing &amp; capabilities -&gt; Select team
Then go for
Build settings-&gt;Signing Set all as per provisioning profile
Then
//:configuration = Debug
PROVISIONING_PROFILE =
//:configuration = Release
PROVISIONING_PROFILE =
//:completeSettings = some
PROVISIONING_PROFILE
<a href="https://i.stack.imgur.com/4JR4i.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/4JR4i.png" alt="enter image description here" /></a>

After I add Today App Extension Target,I become impossible to compile project.
below is error:

<blockquote>
<pre><code>error: Embedded binary is not signed with the same certificate as the parent app. Verify the embedded binary target's code sign settings match the parent app's.
</code></pre>
 
 Embedded Binary Signing Certificate: iPhone Developer: (Developer name) (number)
 
 Parent App Signing Certificate: iPhone Developer: (Developer name) (number)
</blockquote>

but Embedded binary certificate and parent app's cerificate are the same.
So I'm confusing now...

Xcode6:Embedded binary is not signed with the same certificate as the parent app

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

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

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

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

社区新版编辑器体验调研

添加“今日应用程序扩展目标”之后，我就不可能编译项目了。以下是错误：错误:嵌入式二进制文件没有与父应用程序使用相同的证书签名。验证嵌入式二进制目标的代码符号设置与父应用程序的匹配。嵌入式二进制签名证书: iPhone Developer：(开发人员名称)(编号)父应用程序签名证书: iPhone Developer：(开发人员名称)(编号)但是嵌入式二进制证书和父应用程序的证书是相同的。所以我现在

问Xcode6:嵌入式二进制文件不使用与父应用程序相同的证书签名。
EN

回答 29

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Xcode6:嵌入式二进制文件不使用与父应用程序相同的证书签名。EN

回答 29

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Xcode6:嵌入式二进制文件不使用与父应用程序相同的证书签名。
EN