Xcode6:嵌入的二进制文件与父应用程序没有签署相同的证书。

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

在我添加了今天的App扩展目标之后，我就不可能编译项目了。下面是错误:

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.

Embedded Binary Signing Certificate: iPhone Developer: (Developer name) (number)

嵌入式二进制签名证书:iPhone开发人员:(开发人员姓名)(编号)

Parent App Signing Certificate: iPhone Developer: (Developer name) (number)

父应用程序签名证书:iPhone开发者:(开发者姓名)(编号)

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

但是嵌入式二进制证书和父应用程序的cerificate是相同的。所以我现在困惑…

28 个解决方案

#1

I had to select my app under 'Targets', then go to the 'Capabilities' tab and click 'Fix Issues' under the 'App Groups' section

我必须在“目标”下选择我的应用程序，然后点击“功能”选项卡，点击“应用程序组”部分的“修复问题”。

#2

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.

在使用WatchKit的情况下，请确保您的手表应用程序有正确的“团队”选择在Watch App的目标设置中(在>通用的>团队中)。我设置了手机应用的团队，但不是手表应用的团队。

#3

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.

我在代码签名时有差异。我的扩展和主应用程序选择了不同的证书。一旦我设置了两者的分配，它就会运行良好。

#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:
1.Go to Xcode->Preference; 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.

如果你的Xcode一直不错,但停止工作后你添加一个扩展目标项目,大部分时间是使用旧的证书签署应用程序(和你的名字仍然有效等),而您的扩展与更新的证书签署的权利扩展。这就是错误的原因。在这种情况下，您很可能有两个具有相同名称的证书，您可以这样做:1。去Xcode - >首选项;2。选择帐户选项卡;3所示。选择你的苹果ID然后点击查看详情;4所示。在签名标识列表窗口下，选择IOS开发，然后单击小配置图标，并选择Revoke;5。然后Xcode将尝试下载新的证书。您可以在这之后进行一个干净的构建，因此您的应用程序和扩展都将使用新的证书来签署。

#5

I solved it by deleting my Apple ID account in

我通过删除我的Apple ID帐户来解决它。

Preferences -> Accounts

and then logging back in again with my Apple ID

然后用我的苹果ID再次登录。

#6

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.

我在Xcode 6中也有同样的问题，但在我的情况下，它发生的原因是有两个活跃的开发人员证书。撤销一个已解决的问题。

#7

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.

这个问题可能会出现在像扩展或watchapp这样的嵌入式应用程序目标没有在通用部分中选择的匹配团队作为主要的iOS应用程序的情况下。

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

为所有相关目标选择合适的团队为我解决问题。

#8

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 http://developer.apple.com/certificationauthority/AppleWWDRCA.cer Make sure you add this to your keychain as well.

我们还必须安装由苹果的全球开发者关系发布的WWDR中级证书。它可以从门户下载，也可以直接从http://developer.apple.com/certificationauthority/AppleWWDRCA.cer下载，并确保将其添加到您的密钥链中。

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

添加证书:打开你的钥匙链实用工具在你的Mac电脑,然后去文件→导入项目,然后选择AppleWWDRCA.cer。

#9

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).

这个问题有很多原因。如果其他的答案都不适合你的话，那么你还想再做一个看似合理的检查来帮助我。确保您签署的证书没有“始终信任”(如果设置是这样的话，您将看到一个绿色的“+”符号)。

1. Go to Key Chain access, double click on the certificate you are using.
2. 转到关键链访问，双击您正在使用的证书。
3. Expand the 'Trust' drop down and change/set to 'Use System Defaults' from 'Always Trust'.
4. 扩展“信任”下拉，并从“始终信任”中更改/设置为“使用系统默认值”。

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

如果你在你的项目中使用Swift，因为“总是信任”设置会破坏相关的Swift代码库，这一点尤其正确。

#10

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

目标有自己的bundle id，你也需要创建一个AppId。这解决了你所面临的同样的问题。

best

最好的

#11

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

只需让Xcode处理配给工作。这也解决了我的问题。http://aplus.rs/2014/embedded-binary-is-not-signed-with-the-same-certificate-as-the-parent-app/

#12

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.

如果这对任何人都有帮助，我的解决方案是，在提交到商店时，我已经更新了我的存档计划，但从未将其更改为临时测试。编辑我的档案计划使用专案工作。

#13

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.

当我有这个问题的时候，我去了苹果的会员中心，发现我创建的扩展配置文件被标记为“无效”。我只是重新创建了配置文件，并使用与应用程序签署的相同的证书，然后通过Xcode >首选>帐号>刷新来下载它。

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.

注意，扩展有它自己的应用程序id，因此有它自己的配置文件。

#14

For Xcode 8 beta 3

对于Xcode 8 beta 3。

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

在我的Xcode项目文件中，我的构建编号在我的不同目标上消失了。

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

我的iOS目标有一个构建版本3，但是我的手表应用程序目标和我的共享扩展目标都构建了版本1。

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

我所做的就是匹配所有目标的构建数字(将它们全部更改为3)，并解决了这个问题。

Hope this helps.

希望这个有帮助。

#15

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 !

我尝试在iPhone5上运行项目，但是App扩展不支持32位的架构。因此，当我在iPhone5S中构建项目时，我可以构建项目!

#16

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

刷新我的配置文件为我修复(首选项->帐户->双击帐户->点击刷新按钮在左下)

#17

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!!

打开你的钥匙链，它是苹果全球开发者关系认证机构，如果我选择一直信任，Xcode档案失败。当我更改为系统默认值时，Xcode归档成功。是的,你会喜欢! !

#18

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

出于某种原因，我的开发人员证书存储在我的钥匙链中两次。删除其中一个修正了这个问题。

#19

I had got the same issue.

我也有同样的问题。

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

所以我为每个bundle ID和WatchKit应用的配置做了一个准备profil:

• Watch App Development
• 看应用程序开发

• Watch Extension Development

  看扩展开发

• Watch App Production

  观察应用生产

• Watch Extension Prod
• 看扩展刺激

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

/ !要小心，因为开发者门户网站的应用程序ID是这样的:

com.example.projectname.watchkitapp.watchkitextension

com.example.projectname.watchkitapp.watchkitextension

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

当我创建watchkit app时Xcode中的bundle ID是:

com.example.projectname.watchkitapp

com.example.projectname.watchkitapp

maybe it something which changed since WatchOS 2.0.

也许这是自从WatchOS 2.0之后发生的变化。

#20

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!

Xcode->偏好->账户->视图细节->选择所有配置文件->按下键在键盘上删除完成按下下载全部按钮!

#21

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:

我在Xcode 7.1中也遇到过同样的问题。该应用有一个手表扩展，因此是一个应用程序组。对我起作用的是:

1. Go to ~/Library/MobileDevice/Provisioning Profiles
2. 去图书馆~ / / MobileDevice /配置概要文件
3. Delete all provisioning profiles listed there
4. 删除列出的所有配置文件。
5. Go to the iOS Dev Center in Safari and regenerate all provisioning profiles
6. 进入Safari的iOS开发中心，重新生成所有配置文件。
7. Go back to Xcode => Preferences => Apple IDs and choose the Apple ID associated with the app
8. 返回Xcode =>首选项=>苹果ID，并选择与app关联的苹果ID。
9. Click "View Details..." (lower right)
10. 点击“视图细节……”(右下)
11. Download the provisioning profiles that were just created
12. 下载刚刚创建的配置文件。
13. Clean and build again
14. 再次清洁和构建

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.

我认为我的配置文件被混淆了，因为我使用Xcode的“修复自动”特性来处理另一个我拥有的功能=>关联的域。

#22

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.

在你的mac上打开钥匙链，删除你自己证书上的另一个证书。这个问题在你在Xcode中的另一个帐户中被删除后出现了。

#23

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.

2、编辑Iphone应用程序开发证书，确保包括你刚刚创建的证书。

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

3、对watchkit扩展和watchkit应用做同样的操作。

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

4、去你的Xocde“偏好”，双击你的“团队名称”，删除旧的Iphone、watchApps、watchExtention证书。

5、download your new certificate and install.

下载您的新证书并安装。

Then it works.

它的工作原理。

#24

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!

在我的例子中，我的应用程序和我的小部件配置文件是用不同的证书签名的。所以我必须去iOS开发者站点，选择父应用程序配置文件->编辑，并选择与小部件相同的证书。然后点击“生成”和“下载”。您已经下载了它，双击它来安装XCode。然后在构建设置中为您的父应用程序选择新的配置文件->配置文件。最后重建你的项目!

#25

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.

对我来说，这是因为我的一些配置文件已经过期。在developer.apple.com上创建了新的配置文件，删除了旧的文件，将它们设置为Xcode中的自动文件，错误就消失了。

#26

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.

所以登录developer.apple.com查看这些概要文件是否包含不同的证书。

#27

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.

经过一整天的努力，“苹果全球开发者关系认证权威”在根证书中被删除。我从另一台机器上导出一个，安装好了，一切正常。

#28

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

如果您正在使用任何扩展(在我的情况下，我使用的是OneSignal扩展)，在这种情况下，您的父应用程序包将是com.app。但是对于扩展/小部件，您的bundle id将是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.

因此，我们将使用bundle identifier com.app.xyz创建一个app id。我们将为这个应用程序id创建配置文件。

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

我们将使用与父应用程序相同的开发和生产证书。

Here is link which can be helpful provisioning profile for a widget

这里有一个链接，可以为小部件提供有用的配置文件。

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

最后，我没有使用自动设置。因此，我手动设置了配置文件和证书。