iTunes Connect上的签名无效（无效二进制） [英] Invalid Signature (Invalid Binary) on iTunes Connect

问题描述

我知道这是一个重复的问题，但在所有其他问题上，我无法找到解决方案，所以我重新发布问题并提供更多详细信息。

I know is a duplicate question, but on all other questions i cant find a solution, so i retry to post question with more details.

我归档了我的应用on xcode5 for iOS7 with Release Scheme 并更正配置分配

I archive my app on xcode5 for iOS7 with Release Scheme and correct Provisioning Distribution

这是屏幕：

这是打开的项目

这是在目标

我尝试做很多不同的资产，我肯定对我的建筑档案在发布上，但 iTunesConnect 的答案是每次都相同：

I try to do many different asset, i'am sure to my Building Archive is on Release but the answer of iTunesConnect is every time the same:

亲爱的开发者，

Dear developer,

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

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

无效签名 - 确保您已使用
分发证书签署了您的申请，不是临时证书或开发
证书。验证Xcode中的代码签名设置在目标级别是否为
是否正确（覆盖项目
级别的任何值）。此外，请确保使用Xcode中的Release目标而不是模拟器目标，将要上传的包构建为
。如果您的
确定您的代码签名设置正确，请在
Xcode中选择全部清除，删除Finder中的build目录，然后重建
版本目标。

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

一旦这些问题得到纠正，请转到版本详细信息页面
并单击准备上传二进制文件。继续完成提交
流程，直到应用状态为等待上传。然后你可以
提供更正后的二进制文件。

Once these issues have been corrected, go to the Version Details page and click "Ready to Upload Binary." Continue through the submission process until the app status is "Waiting for Upload." You can then deliver the corrected binary.

问候，

App Store团队

The App Store team

和无效二进制文件

我很难理解如何解决这个问题，任何机构都有这样的想法吗？

I become to crazy to understand how to sole this issue, any body have idea to do this?

谢谢。

****测试回复****

****Test Response****

Athority Screen
是正确的

Athority Screen is correct

推荐答案

在Xcode中，在目标级别执行以下操作：

In Xcode, at the target level do the following:

1. 首先选择发布的配置文件组态。 （对于任何SDK ）
   配置文件必须匹配应用的捆绑ID （正如您在常规选项卡中看到的那样）。


2. 在代码签名标识中，点击任何iOS SDK的子菜单并确保选择自动。如果您在下面看不到。


3. 全部清除和存档。

1. First choose the provisioning profile for the Release configuration. (For Any SDK) The provisioning profile must match the app's Bundle ID (As you can see in the General tab).
2. In the code signing identity, tap on the sub-menu for Any iOS SDK and make sure you choose Automatic. If you can't see below.
3. Clean All and Archive.

选择CodeSign标识：

Choosing CodeSign identity:

在第2步中，如果您不能选择自动，这意味着您可能没有AppID和应用程序的Bundle ID之间的匹配。
AppID由您选择的配置文件指向。

In step 2, if you can't choose Automatic, then it means you might not have a match between the AppID and the app's Bundle ID. The AppID is pointed by the provisioning profile you chose.

如果是这种情况，请登录开发人员门户并确保配置文件是您的使用指向正确的AppID。

If this is the case, then login in the developer portal and make sure that the provisioning profile you used points to the correct AppID.

要在提交之前验证.ipa或.app，请尝试使用这些命令。
然后查看打印输出，看看是否所有看起来都正确。同时验证到期日期。

To verify the the .ipa or .app before you submit try these commands. Then look at the printout, and see if all looks right. Also verify the expiration date.

$cd <where the app is>
$unzip *.ipa
$cd Payload
$codesign -d --entitlement - *.app
$codesign --verify -dvvv *.app
$security cms -D -i *.app/embedded.mobileprovision

这篇关于iTunes Connect上的签名无效（无效二进制）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！