另一个应用程序未通过协同设计验证错误
我知道以前曾有人问过这个问题，但尝试了一切但没有运气。尝试使用应用程序加载器上传我的二进制文件并收到上述错误。
我的案例有一些有趣的事情：
我的应用程序名称中不小心有一个空格。这会导致代码签名失败吗？
查看构建日志，最后一个条目是 * 警告：默认使用标准协同设计工具。这可能是导致问题的原因吗？如果是这样我该如何解决。
在公司防火墙后面。我可以访问网络，但某些端口可能被关闭。这会影响吗？
尝试了一切，除了撤销所有证书，主要是因为我几个小时前刚刚创建了它们。
编辑：好的，我已经重新创建了整个项目，我已经撤销了所有证书并重新创建并安装了它们，我已经从 subversion 导出了最后一个版本以确保 subversion 不会影响它，使用命令行工具来压缩它使目标协同设计正确的配置文件，使项目协同设计默认和分发配置文件，尝试不同的网络连接以确保它不是防火墙。
正如你所看到的，我已经尝试了我能找到的一切，但愚蠢的事情仍然行不通。
有什么帮助吗？
干杯
I know this has been asked before but tried everything and no luck. Trying to upload my binaries using Application Loader and getting the above error.
Some interesting things for my case:
I accidentally have a space in my App name. Would this cause the code signing to fail?
Looked in the build log and the last entry is * Warning: Defaulting to the standard codesign tool. Could this be the issue causing the problem? If so how do I solve it.
Behind a corporate firewall. I have access to the net but certain ports may be closed. Could this affect it?
Tried everything except revoking all the certificates mainly because I've just created them a few hours ago.
EDIT: OK, I've recreated the entire project, I've revoked all my certificates and recreated them and installed them, I've exported the last version from subversion to make sure subversion is not affecting it, used command line tool to compress it, made the target codesign the correct profile, made the project codesign both default and the distribution profile, tried a different net connection to make sure its not the firewall.
As you can see I've tried everything I can find and the stupid thing still wont work.
Any help?
Cheers
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
我在使用 XCode4 时遇到了同样的问题。结果我需要编辑方案并指定存档的构建配置是与分发配置文件关联的配置 - 在我的例子中是“App Store”。
如果您遇到同样的问题，可能需要检查一下。
I had the same issue using XCode4. Turns out I needed to Edit the Scheme and specify that the Build Configuration for Archive was to the be the one for the one associated with the Distribution Provisioning Profile - in my case "App Store".
If you're having the same problem, that may be something to check.
在项目级别，您想要设置代码签名身份，但将配置配置文件保留为默认值。
然后，在目标级别，您必须设置代码签名身份和配置文件。
如果您不这样做，软件包将被签名，但 iTunes Connect 无法正确解释。
At the project level you want to set your code signing identity, BUT LEAVE THE PROVISIONING PROFILE TO DEFAULT.
Then at the target level you have to set both the code signing identity and the provisioning profile.
If you fail to do that the package will be signed but not interpreted correctly by itunes connect.
我也遇到了这个问题，直到我意识到现在有一种不同的方式来上传应用程序。
我的“发布”应用程序构建为存档
如果您打开管理器并选择顶部的“存档”，则您的应用程序的标题信息中会有“验证”、“共享”和“提交”按钮。
单击“验证”将我的代码签名信息添加到应用程序中（使用适当的开发人员登录名登录后）
单击“提交”让我完成了应用程序加载器曾经提出的相同问题，并毫无问题地上传了应用程序。 （再次使用适当的开发人员信息登录后）
显然，当我更新到 xcode 4 时，它只是没有删除旧的应用程序加载器。
I too had this problem, until I realized there's a different way to upload the apps now.
My 'release' Apps build as Archives
If you open the organizer and select 'Archives' at the top, there are 'Validate', 'Share', and 'Submit' buttons in the header info for your app.
Clicking on 'Validate' added my code signing information to the app (after logging in with the appropriate developer login)
Clicking on 'Submit' ran me through the same questions the Application Loader used to ask and uploaded the app without problems. (again after signing in with the appropriate developer information)
Apparently when I updated to xcode 4, it just didn't remove the old application loader.
Rudiger 通过更新到最新版本的 Xcode 解决了他的问题，但对于其他遇到错误“应用程序协同设计验证失败”的人，请参阅 Apple 在以下 URL 上发布的潜在原因列表 "如何解决该错误：应用程序未通过协同设计验证？"
Rudiger has worked around his problem by updating to the latest version of Xcode, but for others experiencing the error "Application failed codesign verification", see Apple's published list of potential causes at the following URL "How do I resolve the error: Application failed codesign verification?"
K，这太烦人了。按照我在问题中所说的方式完成所有操作并做了两次之后，决定在其他人的计算机上尝试应用程序加载器。第一次工作，没有跳过。
奇怪的是我有当前的 Xcode（我认为这是应用程序加载器的来源）而另一台计算机正在运行旧的。也许现在的那个坏了？
K, This is incredibly annoying. After doing everything as I said in the question and doing some things twice decided to try the Application Loader on someone else's computer. Worked first time, didn't skip a beat.
Strange thing is I have the current Xcode (which I assume is where Application Loader comes from) and the other computer is running an old one. Perhaps the current one is broken?