blocks|key|1407309|text|嵌入式二进制文件指的是与应用程序一起部署的小部件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1407310|在您的示例中，您没有使用任何签名标识对您的小部件进行签名(因为您的错误是“”)。|1407311|要解决这个问题，请转到您的Project文件，找到您的小部件的目标，然后在Build设置选项卡下找到代码签名标识值。选择用于主应用程序目标的相同的代码签名标识。|1407312|您还需要在想要发布配置文件专门用于您的小部件时创建和配置它。|1407313|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/25837722/provisioning-profile-for-today-widget-extension^0|L|3|0|0|0|D|9|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|X|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|Y|8|@]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|L|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]]]

The embedded binary is referring to a widget that you are deploying alongside with your app. 

In your case, you are not signing your widget with any Signing Identity (since your error says "Not Code Signed"). 

To resolve this, go to your Project file, find your widget's target, and under the Build Setting tab, find the Code Signing Identity value. Choose the same code signing identity that you are using for your main app's target.

You will also need to create and configure a provisioning profile <a href="https://stackoverflow.com/questions/25837722/provisioning-profile-for-today-widget-extension">specifically for your widget</a> when you want to release it.

blocks|key|1910748|text|当应用程序组在开发人员门户中的所有应用程序ID上都没有正确设置时，我得到了这个错误。因此，应用程序中的应用程序组不能正常工作，扩展程序或Watchkit应用程序的二进制文件无法签名。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1910749|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 got this error when the App Groups weren't set up correctly on all my App IDs in the Developer Portal. Therefor the App Groups in the app didn't work correctly and the Binary for the extension or the Watchkit app couldn't be signed.

blocks|key|1910864|text|有时，Stackoverflow上的解决方案都不起作用。在这种情况下，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1910865|解决方案|1910866|确保在MainApp和EmbeddedApp中的签名(调试)、签名(发布)和启用功能的任何一节中都没有红色标记/问题。|ordered-list-item|1910867|确保证书和供应配置文件都安装在登录/系统密钥链下。|1910868|​|1910869|📷|atomic|offset|length|1910870|1910871|确保您的证书是，永远不要将设置为始终信任。访问必须保留为使用系统默认|style|BOLD|1910872|1910873|1910874|1910875|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/4e01a5bf74385fe8017fcd0c3d89c0f5.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/a41e57173638ac0204e8dff463e51d95.png^0|0|0|0|0|0|0|1|0|0|0|7|6|G|4|S|6|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1A|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|1B|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1C|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|1D|8|@]|9|@$N|1E|O|1F|1|1G]]|A|$]]|$1|P|3|J|5|6|7|1H|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|1I|8|@$N|1J|O|1K|S|T]|$N|1L|O|1M|S|T]|$N|1N|O|1O|S|T]]|9|@]|A|$]]|$1|U|3|J|5|6|7|1P|8|@]|9|@]|A|$]]|$1|V|3|L|5|M|7|1Q|8|@]|9|@$N|1R|O|1S|1|1T]]|A|$]]|$1|W|3|J|5|6|7|1U|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]]|Y|$Z|$5|10|11|12|A|$13|14|15|-4]]|16|$5|10|11|12|A|$13|17|15|-4]]]]

Sometimes none of the solution on Stackoverflow works. In that case,
<h2>Solution</h2>
<ol>
<li>Make sure that there is no red mark/issue in any of the sections of Signing(Debug), Signing(Release) and Enabled capabilities in both of MainApp and EmbeddedApp</li>
<li>Make sure that both certificates and provisioning profiles are installed under login/system keychain.</li>
</ol>
<a href="https://i.stack.imgur.com/UPNXD.png" rel="noreferrer"><img src="https://i.stack.imgur.com/UPNXD.png" alt="enter image description here" /></a>
<ol start="3">
<li>Make sure that your certificate is never ever set as Always Trust. Access must be kept as Use System Default</li>
</ol>
<a href="https://i.stack.imgur.com/FCcHv.png" rel="noreferrer"><img src="https://i.stack.imgur.com/FCcHv.png" alt="enter image description here" /></a>

blocks|key|1407401|text|奇怪的是，为了修复这个错误，我不得不从我的项目中删除products文件夹。Xcode崩溃后，重新打开，工作起来像一个魅力！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1407402|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|$]]

Oddly enough, I had to remove the products folder from my project in order to fix this error. Xcode crashed then, after reopening, worked like a charm!

blocks|key|95398|text|当今日扩展的部署目标比父应用程序更新时，也会显示此错误。他们一定是一样的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|95399|我已经将iOS应用程序设置为10.0，并添加了“今日扩展”，最新版本自动设置为11.4。这会导致出现错误。只需将扩展目标的部署目标更改为10.0即可解决此问题。|95400|entityMap^0|6|4|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 error is also shown when deployment target of your Today extension is newer than the parent app. They must be the same.

I have iOS app set to 10.0 and added Today extension which was automatically set to 11.4 as the latest. This caused the error to appear. Simply changing the Deployment target of the extension target to 10.0 resolved the issue.

blocks|key|1910947|text|在将Copy+Files构建阶段添加到主应用程序目标后，我得到了这个错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1910948|复制文件
目的地：Absolute+Path
路径：/Applications
文件：MyApp.app|blockquote|BOLD|1910949|这是我第一次运行这个应用程序的时候。|1910950|在随后的运行中，Xcode开始抱怨证书不匹配。|1910951|删除复制文件生成阶段修复证书不匹配。我仍然在寻找一种没有错误的复制文件的方法。|1910952|同一问题链接：|1910953|https://stackoverflow.com/a/32802258/1265393|unordered-list-item|1910954|https://forums.developer.apple.com/thread/102707|1910955|https://github.com/Bouke/SwiftInitializerGenerator/issues/6|1910956|entityMap|0|LINK|mutability|MUTABLE|url|1|2^0|2|A|0|0|4|9|D|Q|D|17|9|0|0|0|0|0|0|18|0|0|0|1C|1|0|0|1N|2|0^^$0|@$1|2|3|4|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1A|8|@$9|1B|A|1C|B|I]|$9|1D|A|1E|B|C]|$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1J|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1K|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1L|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1M|8|@]|D|@]|E|$]]|$1|R|3|S|5|T|7|1N|8|@]|D|@$9|1O|A|1P|1|1Q]]|E|$]]|$1|U|3|V|5|T|7|1R|8|@]|D|@$9|1S|A|1T|1|1U]]|E|$]]|$1|W|3|X|5|T|7|1V|8|@]|D|@$9|1W|A|1X|1|1Y]]|E|$]]|$1|Y|3|-4|5|6|7|1Z|8|@]|D|@]|E|$]]]|Z|$10|$5|11|12|13|E|$14|S]]|15|$5|11|12|13|E|$14|V]]|16|$5|11|12|13|E|$14|X]]]]

I got this error after adding a <code>Copy Files</code> Build Phase to the main app Target.

<blockquote>
 Copy Files 
 Destination: <code>Absolute Path</code> 
 Path: <code>/Applications</code> 
 File: <code>MyApp.app</code>
</blockquote>

This worked the first time I ran the app.

On subsequent runs, Xcode began complaining about the certificate mismatch.

Removing the Copy Files build phase fixes the certificate mismatch. I'm still searching for a way to Copy Files without the error.

Same issue links: 

<ul>
<li><a href="https://stackoverflow.com/a/32802258/1265393">https://stackoverflow.com/a/32802258/1265393</a></li>
<li><a href="https://forums.developer.apple.com/thread/102707" rel="nofollow noreferrer">https://forums.developer.apple.com/thread/102707</a></li>
<li><a href="https://github.com/Bouke/SwiftInitializerGenerator/issues/6" rel="nofollow noreferrer">https://github.com/Bouke/SwiftInitializerGenerator/issues/6</a></li>
</ul>

blocks|key|1910982|text|这个问题似乎出现在xcode+10中，并且解决方案与前面提到的不同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1910983|通过将构建系统设置为Legacy+(通过文件>工作区设置)，我能够修复(或者更确切地说是绕过)错误。
另一件有趣的事情是，如果我正在构建一个实际的设备(即在将构建系统更改为Legacy之前)，则不会出现签名错误。只有在使用模拟器构建时，并且仅在Xcode+10+beta+3、4和5上才会出现这种情况。|blockquote|1910984|链接到原始线程：https://forums.developer.apple.com/thread/105537|offset|length|1910985|entityMap|0|LINK|mutability|MUTABLE|url|https://forums.developer.apple.com/thread/105537^0|0|0|8|1C|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|$]]|$1|E|3|F|5|6|7|S|8|@]|9|@$G|T|H|U|1|V]]|A|$]]|$1|I|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P]]]]

It seems this issues appears in xcode 10 and the resolution is different from the aforementioned. 

<blockquote>
 I was able to fix (or rather bypass) the error by setting the Build
 System to Legacy (via File > Workspace Settings)
 
 Another interesting thing to note is that the signing error would not
 occurr if I was building to an actual device (i.e. before changing the
 Build System to Legacy). It would only occurr when building using the
 simulator and only on Xcode 10 beta 3, 4 and 5.
</blockquote>

Link to the original thread: <a href="https://forums.developer.apple.com/thread/105537" rel="noreferrer">https://forums.developer.apple.com/thread/105537</a>

blocks|key|95496|text|当我迁移到Xcode+10并通过更新Watch目标中的"Build“>”有效体系结构“中的体系结构时，我遇到了这个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|95497|$(ARCHS_STANDARD)|blockquote|95498|这条线帮了我很多忙：https://forums.developer.apple.com/thread/107563|95499|entityMap|0|LINK|mutability|MUTABLE|url|https://forums.developer.apple.com/thread/107563^0|I|7|0|0|A|1C|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$]]|$1|I|3|J|5|6|7|W|8|@]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|K|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|L|$M|$5|N|O|P|E|$Q|R]]]]

I was having this issue when I migrated to Xcode 10 and managed to fix it by updating the architectures in "Build Settings"> "Valid Architectures" for the Watch target to 

<blockquote>
 $(ARCHS_STANDARD)
</blockquote>

This thread helped me out a lot: <a href="https://forums.developer.apple.com/thread/107563" rel="noreferrer">https://forums.developer.apple.com/thread/107563</a>

blocks|key|95516|text|我在我的代码中有另一个编译时错误时得到了这个错误.|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|95517|我的新目标从来没有建立过。|95518|所以我想我应该先纠正这个错误。但是事实证明，修复其他错误使Xcode能够构建目标并修复其他错误本身。|95519|entityMap^0|0|P|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|P|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|K|$]]

I got this error while having another compile time error in my code.

My new target has never been built before.

So I thought I'll fix this error first. But it turned out, that fixing the other error enabled Xcode to build the target and fix the other error itself.

blocks|key|1414173|text|检查您是否有更多的目标，如oneSignal或其他目标，并检查您是否有相同的团队的主要目标。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1414174|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|$]]

Check if you have more targets like oneSignal or other else and check if you have the same team of the main target.

blocks|key|95561|text|我在Xcode+11中构建一个WatchOS应用程序时遇到了这个错误--我尝试了这篇文章和其他文章中的各种建议，但是最终起作用的是将Xcode转换成使用遗留构建系统。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|95562|转到:+File+@+Project+(或Workspace)+Settings+\+Build+System|95563|并选择遗产建设系统|95564|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|$]]

I was getting this error trying to build a WatchOS app in Xcode 11 - I tried all the various suggestions in this and other SO posts but the thing that finally worked was switching Xcode to use the legacy build system.

Go to: File | Project (or Workspace) Settings | Build System

And select Legacy Build System

blocks|key|1911194|text|假设|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1911195|我正在使用的应用程序名为TestApp+(为了隐私)。|unordered-list-item|offset|length|style|BOLD|1911196|下面的步骤是在Xcode+11.1中测试的|1911197|我用来编译的方案是AdHoc。|1911198|该应用程序具有推送通知功能|1911199|问题|1911200|就我而言，这一问题是由于签署两个目标之间的差异造成的。问题是：|1911201|TestApp目标(即错误中的什么称为父应用程序签名证书)|1911202|notificationServiceExtension目标(即错误中的内容称为嵌入式二进制签名证书)。|1911203|​|1911204|📷|atomic|1911205|1911206|分辨率|1911207|在我的AdHoc+中，在TestApp目标下，我禁用了自动签名，因为我想指定供应配置文件和证书。|1911208|我遵循的步骤是：|1911209|来自Signing+&+Capabilities+->+AdHoc+->+Signing+(section)+|ordered-list-item|CODE|1911210|删除选中的“自动管理签名”中的滴答。|1911211|选择了我想使用的配置配置文件|1911212|1911213|1911214|1911215|1911216|1911217|来自Build+Settings+->+Signing+(section)+|1911218|在Code+Signing+Identity下，为AdHoc和Any+SDK选择我想要使用的证书|1911219|在Code+Signing+Style+->+AdHoc下，选择了手册|1911220|在Provisioning+Profile+->+AdHoc下，选择我想要使用的配置配置文件(即与步骤1.2相同)|1911221|1911222|1911223|1911224|1911225|1911226|引发此错误是因为我没有将相同的设置应用于notificationServiceExtension目标(该目标仍在使用自动签名，因此使用另一个证书)。一旦我对这个目标重复了上面的步骤，错误就消失了。|1911227|我希望它能帮助别人，因为这个错误把我逼疯了！|1911228|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/594899c059be5f505c21c43b96088d9a.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/7773da453fdf8df40d7fbbd0fd3cafe7.png|2|https://developer.qcloudimg.com/http-save/yehe-900000/6b74d384c6932b34edc0a32ba3055ec8.png^0|0|C|7|0|7|A|0|9|5|0|7|6|0|0|0|0|7|0|0|S|0|0|0|1|0|0|0|0|3|6|0|0|2|1G|1|1|1|0|0|0|0|1|1|0|0|2|Z|1|1|L|P|5|V|7|1|1|R|X|2|1|1|T|1|0|0|0|0|1|2|0|0|K|U|0|0^^$0|@$1|2|3|4|5|6|7|2F|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|2G|8|@$E|2H|F|2I|G|H]]|9|@]|A|$]]|$1|I|3|J|5|D|7|2J|8|@$E|2K|F|2L|G|H]]|9|@]|A|$]]|$1|K|3|L|5|D|7|2M|8|@$E|2N|F|2O|G|H]]|9|@]|A|$]]|$1|M|3|N|5|D|7|2P|8|@$E|2Q|F|2R|G|H]]|9|@]|A|$]]|$1|O|3|P|5|6|7|2S|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|2T|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|2U|8|@$E|2V|F|2W|G|H]]|9|@]|A|$]]|$1|U|3|V|5|D|7|2X|8|@$E|2Y|F|2Z|G|H]]|9|@]|A|$]]|$1|W|3|X|5|6|7|30|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|10|7|31|8|@]|9|@$E|32|F|33|1|34]]|A|$]]|$1|11|3|X|5|6|7|35|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|36|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|37|8|@$E|38|F|39|G|H]]|9|@]|A|$]]|$1|16|3|17|5|6|7|3A|8|@]|9|@]|A|$]]|$1|18|3|19|5|1A|7|3B|8|@$E|3C|F|3D|G|1B]]|9|@]|A|$]]|$1|1C|3|1D|5|1A|7|3E|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|1A|7|3F|8|@]|9|@]|A|$]]|$1|1G|3|-4|5|6|7|3G|8|@]|9|@]|A|$]]|$1|1H|3|X|5|6|7|3H|8|@]|9|@]|A|$]]|$1|1I|3|X|5|6|7|3I|8|@]|9|@]|A|$]]|$1|1J|3|Z|5|10|7|3J|8|@]|9|@$E|3K|F|3L|1|3M]]|A|$]]|$1|1K|3|X|5|6|7|3N|8|@]|9|@]|A|$]]|$1|1L|3|1M|5|1A|7|3O|8|@$E|3P|F|3Q|G|1B]]|9|@]|A|$]]|$1|1N|3|1O|5|1A|7|3R|8|@$E|3S|F|3T|G|1B]|$E|3U|F|3V|G|1B]|$E|3W|F|3X|G|1B]]|9|@]|A|$]]|$1|1P|3|1Q|5|1A|7|3Y|8|@$E|3Z|F|40|G|1B]|$E|41|F|42|G|H]]|9|@]|A|$]]|$1|1R|3|1S|5|1A|7|43|8|@$E|44|F|45|G|1B]]|9|@]|A|$]]|$1|1T|3|-4|5|6|7|46|8|@]|9|@]|A|$]]|$1|1U|3|X|5|6|7|47|8|@]|9|@]|A|$]]|$1|1V|3|X|5|6|7|48|8|@]|9|@]|A|$]]|$1|1W|3|Z|5|10|7|49|8|@]|9|@$E|4A|F|4B|1|4C]]|A|$]]|$1|1X|3|X|5|6|7|4D|8|@]|9|@]|A|$]]|$1|1Y|3|1Z|5|6|7|4E|8|@$E|4F|F|4G|G|H]]|9|@]|A|$]]|$1|20|3|21|5|6|7|4H|8|@]|9|@]|A|$]]|$1|22|3|-4|5|6|7|4I|8|@]|9|@]|A|$]]]|23|$24|$5|25|26|27|A|$28|29|2A|-4]]|2B|$5|25|26|27|A|$28|2C|2A|-4]]|2D|$5|25|26|27|A|$28|2E|2A|-4]]]]

<h2>Assumptions</h2>

<ul>
<li>the app I am working is called TestApp (for the sake of privacy)</li>
<li>the steps below are tested in Xcode 11.1</li>
<li>the scheme I was using to compile is AdHoc</li>
<li>the app has the Push Notification capability</li>
</ul>

<h2>Issue</h2>

In my case the issue was caused by a discrepancy between the signing of two targets. The issue was between:

<ul>
<li>the TestApp target (i.e. what in the error is referred to as Parent App Signing Certificate)</li>
<li>the notificationServiceExtension target (i.e. what in the error is referred to as Embedded Binary Signing Certificate).</li>
</ul>

<a href="https://i.stack.imgur.com/3Xe4G.png" rel="noreferrer"><img src="https://i.stack.imgur.com/3Xe4G.png" alt="targets"></a>

<h2>Resolution</h2>

In my AdHoc scheme, under the TestApp target, I disabled the automatic signing because I wanted to specify the provisioning profile and the certificate. 

The steps I followed were:

<ol>
<li>from <code>Signing &amp; Capabilities -&gt; AdHoc -&gt; Signing (section)</code>

<ol>
<li>removed the tick from Automatically manage signing under selected</li>
<li>selected the provisioning profile I wanted to use</li>
</ol></li>
</ol>

<a href="https://i.stack.imgur.com/viaqG.png" rel="noreferrer"><img src="https://i.stack.imgur.com/viaqG.png" alt="signing&amp;capabilities"></a>

<ol start="2">
<li>from <code>Build Settings -&gt; Signing (section)</code>

<ol>
<li>under <code>Code Signing Identity</code>, choose for both <code>AdHoc</code> and <code>Any SDK</code> the certificate I wanted to use</li>
<li>under <code>Code Signing Style -&gt; AdHoc</code>, chose Manual</li>
<li>under <code>Provisioning Profile -&gt; AdHoc</code>, chose the provisioning profile I wanted to use (i.e. the same as step 1.2)</li>
</ol></li>
</ol>

<a href="https://i.stack.imgur.com/UmVXD.png" rel="noreferrer"><img src="https://i.stack.imgur.com/UmVXD.png" alt="build settings"></a>

The error was thrown because I didn't apply the same settings to the notificationServiceExtension target (which was still using the automatic signing and therefore another certificate). As soon as I have repeated the steps above also for this target, the error was gone.

I hope it can helps someone, because this error drove me crazy!

blocks|key|95704|text|检查您的密钥链访问到期证书，而不是删除，这就是为什么它显示错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|95705|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|$]]

Check your keychain access expire certificate not deleted that's why its showing a error.

blocks|key|1414263|text|XCode+12.5|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1414264|就我而言，我听从了沙基尔·艾哈迈德的回答。但是我也需要在Pod文件上做这个更改。|1414265|📷|atomic|offset|length|1414266|​|1414267|您可以在这里找到更多的https://github.com/facebook/react-native/issues/31480#issue-876308920|1414268|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/b5ed02db91edbf7d99da2562594c4e27.png|imageAlt|1|LINK|MUTABLE|url|https://github.com/facebook/react-native/issues/31480#issue-876308920^0|0|0|0|1|0|0|0|B|1X|1|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|@$G|13|H|14|1|15]]|A|$]]|$1|I|3|J|5|6|7|16|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|17|8|@]|9|@$G|18|H|19|1|1A]]|A|$]]|$1|M|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T|U|-4]]|V|$5|W|Q|X|A|$Y|Z]]]]

XCode 12.5
In my case, I followed Shakeel Ahmed's answer. But I also needed to do this change on the Pod file.<a href="https://i.stack.imgur.com/SPSHg.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/SPSHg.png" alt="enter image description here" /></a>
You can find more here <a href="https://github.com/facebook/react-native/issues/31480#issue-876308920" rel="nofollow noreferrer">https://github.com/facebook/react-native/issues/31480#issue-876308920</a>

blocks|key|95824|text|​|type|unstyled|depth|inlineStyleRanges|entityRanges|data|95825|📷|atomic|offset|length|95826|95827|检查您排除的架构|95828|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/efb4b5dd475631f82c59de48b2e07417.png|imageAlt^0|0|0|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@$E|U|F|V|1|W]]|A|$]]|$1|G|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|H|3|I|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]]]]

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

blocks|key|1911406|text|我在一个Unity.iPhone项目中也经历过同样的问题。我们嵌入了一个目标的贴纸扩展，我们附带的应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1911407|粘贴扩展目标是抱怨代码符号设置与父应用程序不匹配的对象。|1911408|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:++++Software+Signing
++++++++Parent+App+Signing+Certificate:+++++Apple+Distribution|code-block|syntax|javascript|1911409|当粘贴扩展目标生成设置设置为ARCHS_STANDARD+(arm7，arm64)，而父应用程序设置为arm64时，就会发生这种情况。|1911410|我通过将扩展的ARCHS属性设置为arm64来修正这个问题。|1911411|Go数字，我怀疑这个输出捕捉到了一系列不同的问题，只是没有在日志消息中指定任何细节。|1911412|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|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$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|$]]

I have experienced this same issue in a Unity.iPhone project.
We embed a target for a Stickers extension that we ship with the app.
The Stickers extension target is the one complaining about the code sign settings not matching the parent apps.
<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.

 Embedded Binary Signing Certificate: Software Signing
 Parent App Signing Certificate: Apple Distribution
</code></pre>
This occurred when the Stickers Extension target build settings were set to ARCHS_STANDARD (arm7, arm64), while the parent app was set to arm64.
I fixed this by setting the Extension's ARCHS build property to arm64.
Go figure, I suspect this output catches a bunch of different issues and just doesn't specify any details in the log message.

blocks|key|1407686|text|在我的例子中，关键是删除“产品”文件夹。然后建造就成功了。此外，在那之后，我做了git+reset+--hard，并再次尝试，取得了同样的成功结果。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1407687|entityMap^0|14|G|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|$]]

In my case the key was to delete 'Products' folder. Then the build was successful. Moreover, after that I made <code>git reset --hard</code> and tried again with the same successful result.

blocks|key|1414329|text|在跟踪SwiftUI文档时，我遇到了一个关于将iOS应用程序与watchOS集成的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1414330|问题是扩展不属于同一个开发团队，所以当我们试图编译它时，它会失败。|1414331|与建筑无关，与信任无关。|1414332|解决方案：xcode的ScreenShot|1414333|转到项目一般文件|ordered-list-item|1414334|检查侧边栏上的扩展文件夹(查看屏幕截图2)|1414335|切换到签名和功能选项卡|1414336|选择您的团队(需要匹配主项目的开发团队)|1414337|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/tutorials/swiftui/creating-a-watchos-app|1|https://i.stack.imgur.com/dGz8F.png^0|3|9|0|0|0|0|5|G|1|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|D|3|E|5|6|7|16|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|17|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|18|8|@]|9|@$A|19|B|1A|1|1B]]|C|$]]|$1|J|3|K|5|L|7|1C|8|@]|9|@]|C|$]]|$1|M|3|N|5|L|7|1D|8|@]|9|@]|C|$]]|$1|O|3|P|5|L|7|1E|8|@]|9|@]|C|$]]|$1|Q|3|R|5|L|7|1F|8|@]|9|@]|C|$]]|$1|S|3|-4|5|6|7|1G|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]|10|$5|V|W|X|C|$Y|11]]]]

I had the issue when following the <a href="https://developer.apple.com/tutorials/swiftui/creating-a-watchos-app" rel="nofollow noreferrer">SwiftUI documentation</a> about integrating an iOS app with watchOS.
The issue is that the extension is not under the same development team, so it will fail when we try to compile it.
Nothing about architecture and nothing about trust.
SOLUTION:
<a href="https://i.stack.imgur.com/dGz8F.png" rel="nofollow noreferrer">ScreenShot for xcode</a> 
<ol>
<li>Go to the project general file</li>
<li>Check on the extension folder on the sidebar (check the screenshot number 2)</li>
<li>Switch to the Signing &amp; Capabilities tab</li>
<li>Choose your team (need to match the master project's development team)</li>
</ol>

blocks|key|1414375|text|我的照片编辑扩展遇到了这个问题。我最终发现，这是由于我的不寻常的项目结构。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1414376|包含所有源代码和资源的我的项目包括一个本地Swift软件包+(app扩展)。|unordered-list-item|1414377|Swift链接了Swift包创建的库。|1414378|开胃没有自己的源文件。“编译源代码”构建阶段没有文件，也没有“复制捆绑资源”构建阶段。|1414379|在一个干净的构建中，Xcode成功地构建了它并将其嵌入到应用程序中。|1414380|在增量构建中，即使没有对任何文件进行任何更改，Xcode也会在“验证MyEx.appex”步骤中失败。|1414381|问题是，Xcode在每次构建的时候都会重新链接appex可执行文件，即使没有什么改变。Xcode做而不是，然后签署新的appex可执行文件，除非是在一个干净的构建过程中。|style|BOLD|1414382|这意味着在增量构建之后，可执行文件始终是未签名的，因此它从未使用与父应用程序相同的证书进行签名(因为它根本没有签名)。|1414383|我的解决方案是将一个空文件dummy.swift添加到appex目标中。这就足以使Xcode在需要时只重新链接Xcode，并且在增量构建过程中始终在链接之后签名Xcode。|CODE|1414384|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/documentation/photokit/creating_photo_editing_extensions/|1|https://developer.apple.com/documentation/xcode/organizing-your-code-with-local-packages^0|2|6|0|0|B|I|1|0|0|0|0|0|1D|3|0|0|D|B|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@$A|18|B|19|1|1A]]|C|$]]|$1|D|3|E|5|F|7|1B|8|@]|9|@$A|1C|B|1D|1|1E]]|C|$]]|$1|G|3|H|5|F|7|1F|8|@]|9|@]|C|$]]|$1|I|3|J|5|F|7|1G|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|1H|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|1I|8|@]|9|@]|C|$]]|$1|O|3|P|5|6|7|1J|8|@$A|1K|B|1L|Q|R]]|9|@]|C|$]]|$1|S|3|T|5|6|7|1M|8|@]|9|@]|C|$]]|$1|U|3|V|5|6|7|1N|8|@$A|1O|B|1P|Q|W]]|9|@]|C|$]]|$1|X|3|-4|5|6|7|1Q|8|@]|9|@]|C|$]]]|Y|$Z|$5|10|11|12|C|$13|14]]|15|$5|10|11|12|C|$13|16]]]]

I had this problem with a <a href="https://developer.apple.com/documentation/photokit/creating_photo_editing_extensions/" rel="nofollow noreferrer">Photo Editing Extension</a>. I eventually discovered that it was due to my unusual project structure.
<ul>
<li><a href="https://developer.apple.com/documentation/xcode/organizing-your-code-with-local-packages" rel="nofollow noreferrer">My project includes a local Swift package</a> containing all the source code and resources for the appex (app extension).</li>
<li>The appex links the library created by the Swift package.</li>
<li>The appex has no source files of its own. The “Compile Sources” build phase has no files, and it has no “Copy Bundle Resources” build phase.</li>
</ul>
On a clean build, Xcode builds the appex and embeds it in the app successfully.
On an incremental build, even with no changes to any file, Xcode fails during the “Validate MyEx.appex” step.
The problem, it turns out, is that Xcode re-links the appex executable every time it builds, even if nothing has changed. And Xcode does not then sign the new appex executable, except during a clean build.
This means that the appex executable is always unsigned after an incremental build, so it is never signed with the same certificate as the parent app (because the appex isn't signed at all).
My solution was to add an empty file, <code>dummy.swift</code>, to the appex target. That is sufficient to make Xcode only re-link the appex when needed, and to always sign the appex after linking during an incremental build.

Those are my first steps in IOS applications development and I'm facing some problem that I can't figure out.
<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.

 Embedded Binary Signing Certificate: Not Code Signed
 Parent App Signing Certificate: iPhone Developer: Emil Adz (9QNEF95395)
</code></pre>
I can't understand, what is a Embedded Binary Signing Certificate?
I went over the questions with the same error here, but none of them were related to the problem presented here (Not Code Signed).
I tried to revoke my certificate from the Apple Developer Member Center and request another certificate, but the issue persists.
Does some know how it could be fixed?

iOS error "Embedded binary is not signed with the same certificate as the parent app"

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

这是我在IOS应用程序开发中的第一步，我面临着一些我无法解决的问题。error: Embedded binary is not signed with the same certificate as the parent app. Verify the embedded binary target's code sig...

问iOS错误“嵌入二进制文件没有与父应用程序相同的证书签名”
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问iOS错误“嵌入二进制文件没有与父应用程序相同的证书签名”EN