无效签名 - 代码对象根本没有签名 [英] Invalid Signature - Code object is not signed at all

查看:26
本文介绍了无效签名 - 代码对象根本没有签名的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我可以通过 Xcode 6.3.2 完美提交我的应用程序.验证和分析完美通过.一旦它成功提交到应用程序商店,尽管我收到了来自 Apple 的电子邮件:

Im able to submit my app through Xcode 6.3.2 perfectly fine. Validation and analyzing pass perfectly. Once it successfully submits to the app store though I get an email from Apple:

亲爱的开发者,我们发现您最近的应用程序"交付存在一个或多个问题.要处理您的交货,必须更正以下问题:无效签名 - 代码对象根本没有签名.确保您已使用分发证书而不是临时证书或开发证书对您的应用程序进行签名.验证 Xcode 中的代码签名设置在目标级别(覆盖项目级别的任何值)是否正确.此外,请确保您上传的包是使用 Xcode 中的 Release 目标构建的,而不是 Simulator 目标.如果您确定代码签名设置正确,请在 Xcode 中选择Clean All",删除 Finder 中的build"目录,然后重建您的发布目标.更多信息请参考https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html更正这些问题后,您就可以重新交付更正后的二进制文件."

"Dear developer, We have discovered one or more issues with your recent delivery for "App". To process your delivery, the following issues must be corrected: Invalid Signature - Code object is not signed at all. 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). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. 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 more information, please consult https://developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html Once these issues have been corrected, you can then redeliver the corrected binary."

我尝试重新下载分发证书,重新生成分发配置文件,将--deep"添加到代码签名其他代码签名标志"中.我什至检查了包名称等,一切都是字母数字.我能够在 5 月 22 日提交罚款,现在在 6 月 3 日一切都坏了.

I have tried redownloading the distribution cert, regenerating the distribution provisioning profile, added "--deep" to the code signing "Other Code Signing Flags." I even checked the bundle name etc, everthing is alpha numeric. I was able to submit fine on May 22nd, now on June 3rd everything breaks.

没有任何意义,任何帮助将不胜感激!

Doesnt make any sense, any help would be appreciated!

更新和更新解决方案:

虽然我没有很好的解释为什么会在上周突然发生这种情况,但我今天早上终于找到了解决方案.

While I don't have a good explanation of why this suddenly has happened within the last week, I finally found a solution this morning.

我从一个新项目开始,然后提交到应用商店,除了标识符、正确的版本和内部版本号之外什么都没有,处理得很好.之后,我开始拼凑任何不是我自己代码的资产,直到我收到无效的二进制"电子邮件.我将范围缩小到导致问题的 Hockey App SDK(嵌入式框架),甚至不再使用,因此我将其从项目中删除(问题已解决).令人不安的是,在验证或提交过程中,我没有任何失败,而且根据 github,这个目录和内容在一年内没有改变,这让我相信 Apple 的服务器端发生了一些变化.

I started with a new project and submitted to the app store with nothing but the identifier and correct version and build numbers, which processed fine. After that I started piecing in any assets that wasnt my own code until I got the "Invalid Binary" email. I narrowed it down to the Hockey App SDK (embedded framework) which was causing the issue and not even being used anymore so I removed it from the project (problem solved). The disturbing part is that nothing fails on my end during validation or submission and according to github this directory and content hasn't changed in a year, which leads me to believe something changed server side at Apple.

我确实通过谷歌看到很多帖子说框架需要签名等,当使用 Xcode 6 和 iOS 8 时,这似乎是标准,这就是为什么我认为它可能是这些方面的东西.

I did see a lot of posts via google saying that frameworks needed signed etc and when using Xcode 6 and iOS 8 it seems to be the standard which is why I assumed it might be something along these lines.

我不确定这有多大帮助,因为我是为 iOS 构建的,这篇文章参考了 Mac,但 HockeyApp 解释说,为了分发到应用商店,您需要在此处使用您自己的身份对框架进行签名:

Im not sure how helpful this is as I was building for iOS and this article is in reference to Mac, but HockeyApp explains in order to distribute to the app store you need to sign the framework with your own identity here:

http://support.hockeyapp.net/kb/client-integration-ios-mac-os-x/hockeyapp-for-mac-os-x

如果有人对此有任何技术说明,或者为什么这会突然改变,我很想更好地理解这一点.

If anyone has anymore technical notes on this or why this suddenly changed Id love to understand this better.

推荐答案

当我为我的资源文件夹创建文件夹引用"而不是在添加时创建组"时,我可以重现这一点.

I can reproduce this when I 'create folder references' for my resources folder as opposed to 'create groups' when adding in.

这篇关于无效签名 - 代码对象根本没有签名的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆