Xcode7项目中的签名无效

功能介绍

签名的原始信息来源于钥匙串，钥匙串里的信息上传到网站上，再生成签名。在mac os里xcode如果变混乱，可能会导致签名无效。如果不对应，也会导致签名无效。

提问

Since upgrading to XCode 7 I don't seem to be able to submit a testflight binary to the Appstore anymore. I get this:

Invalid Signature - The binary with bundle identifier 'ch.abacus.RMFoundation6' at path [RMFoundation6.framework] contains an invalid signature. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target.

for one of my dynamic (iOS8) frameworks. I had to change Bitcode flag on all frameworks and the binary since at least one of my third party frameworks is not enabled for Bitcode, but that's all I had to change when upgrading. I didn't get this message when submitting from XCode 6.4 last week though.When I verify the app using codesign -vvvv myapp.app I don't get *any* errors at all, so how can I find this?

自从升级到XCode 7后，我似乎无法再向Appstore提交testflight二进制文件。我遇到的问题是：

无效签名 - 路径[RMFoundation6.framework]中包含标识符“ch.abacus.RMFoundation6”的二进制文件包含无效签名。确保您已使用分发证书（而非临时证书或开发证书）对您的应用程序进行了签名。验证Xcode中的代码签名设置在目标级别是否正确（覆盖项目级别的任何值）。如果您确定您的代码签名设置正确，请在Xcode中选择“全部清除”，删除Finder中的“构建”目录，然后重建您的发布目标。

对于我的一个动态（iOS8）项目。我不得不在所有项目和二进制文件上更改Bitcode标志，因为至少有一个第三方项目没有为Bitcode启用，但这是我在升级时必须改变的全部内容。上周我从XCode 6.4提交时没有收到此消息。当我使用codesign -vvvv myapp.app验证应用程序时，我根本没有得到任何*错误，所以我怎么能找到这个问题的解决方法？

回答1

Apparently this is not just something that was integrated into XCode 7, but seems to be something on Apple's Servers that has changed. When I build and upload the same binary from XCode 6.4 I get exactly the same error now. Does anyone know how to resolve this cause I have no **** clue显然，这不仅仅是集成到XCode 7中的东西，而且似乎是苹果公司的服务器上发生了变化。当我从XCode 6.4构建并上传相同的二进制文件时，我现在得到完全相同的错误。有谁知道如何解决这个原因我没有****的线索

回答2

We have the same problem on our side since we wanted to submit our application + the WatchKit 1 extension:

We have discovered one or more issues with your recent delivery for "iCoyote10 Test". To process your delivery, the following issues must be corrected:

Invalid Signature - The binary with bundle identifier 'com.moncoyote.icoyote10test.watchkitextension' at path [iCoyote10 WatchKit 1 Extension.appex] contains an invalid signature. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target.

Once these issues have been corrected, you can then redeliver the corrected binary.

Our understanding is that iTunesconnect looks to sign the application again, leading to this invalid signature situation.

We're trying to clean everything on our build machine to see if it changes anything.

我们有同样的问题，因为我们想提交我们的应用程序和WatchKit 1扩展：

我们发现您最近交付的“iCoyote10 Test”存在一个或多个问题。要处理您的交付，必须纠正以下问题：

无效签名 - 路径[iCoyote10 WatchKit 1 Extension.appex]中包含标识符“com.moncoyote.icoyote10test.watchkitextension”的二进制文件包含无效签名。确保您已使用分发证书（而非临时证书或开发证书）对您的应用程序进行了签名。验证Xcode中的代码签名设置在目标级别是否正确（覆盖项目级别的任何值）。如果您确定您的代码签名设置正确，请在Xcode中选择“全部清除”，删除Finder中的“构建”目录，然后重建您的发布目标。

一旦纠正了这些问题，您就可以重新更新已更正的二进制文件。

我们的理解是iTunesconnect会再次签署应用程序，导致这种无效的签名情况。

我们正在尝试清理构建计算机上的所有内容，以查看它是否发生了任何变化。

回答3

We always had three profiles so far. One Dev to debug on a device, an AppStore one for the store and an adhoc for TestFlight (the old one, but we kept it for apples TestFlight). Apparently since the last weekend you can't do that anymore and have to sign your app with the AppStore profile at least that's what I did this time and it seemed to have worked so far. I also changed the signer from iPhone developer to iPhone distribution but I'm not sure if this was necessary (will try that again with the defaults next week). Maybe that helps you too: sign with the AppStore profile if you didn't do this before.到目前为止，我们总是有三个档案。一个Dev用于设备调试，一个AppStore用于商店，一个用于TestFlight（旧版本，但我们保留了它用于苹果TestFlight）。显然自上周末以来你不能再那样做了，并且必须用AppStore配置文件签署你的应用程序，至少这是我这次做的，而且它似乎已经工作到目前为止。我还将签名者从iPhone开发人员更改为iPhone发行版，但我不确定这是否有必要（将在下周再次尝试使用默认设置）。也许这对你有所帮助：如果你之前没有这样做，请使用AppStore配置文件进行签名。

回答4

We have discovered one or more issues with your recent delivery for "MyApp". To process your delivery, the following issues must be corrected:

Invalid Signature - The binary with bundle identifier 'com.mycompany.myframework' at path myframework.framework] contains an invalid signature. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target.

Once these issues have been corrected, you can then redeliver the corrected binary.

Regards,

The App Store team

This is also happening to me with my app. I don't have a watchKit extension, just a dynamic framework that i created. My BitCode is off for all my targets as well, and I've tried to revoke and generate all provisioning profiles and codesigning certificates. I also tried signing the framework with a wildcard certificate, but to no avail. I tried everything that email told me to try.

Is this issue solved? Is there anything that I can do to submit to iTunesConnect?

我们发现您最近为“MyApp”发送了一个或多个问题。要处理您的交付，必须纠正以下问题：

无效签名 - 路径myframework.framework中包含标识符“com.mycompany.myframework”的二进制文件包含无效签名。确保您已使用分发证书（而非临时证书或开发证书）对您的应用程序进行了签名。验证Xcode中的代码签名设置在目标级别是否正确（覆盖项目级别的任何值）。如果您确定您的代码签名设置正确，请在Xcode中选择“全部清除”，删除Finder中的“构建”目录，然后重建您的发布目标。

一旦纠正了这些问题，您就可以重新更新已更正的二进制文件。

问候，

App Store团队

我的应用程序也发生了这种情况。我没有watchKit扩展，只是我创建的动态项目。我的BitCode也关闭了所有目标，我试图撤销并生成所有配置文件和代码签名证书。我也尝试使用通配符证书签署项目，但无济于事。我尝试了电子邮件告诉我尝试的所有内容。

这个问题解决了吗？我有什么办法可以提交给iTunesConnect吗？

回答5

In our case we had forgetten the CODE_SIGN_RESOURCE_RULES_PATH value set in second target which is a Today Extension. Clearing the value for Code Sign Resource Rules Path in each target resolved the issue.在我们的例子中，我们忘记了在第二个目标中设置的CODE_SIGN_RESOURCE_RULES_PATH值，它是今天的扩展。清除每个目标中的代码签名资源规则路径的值解决了该问题。

友情链接