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.

我使用 Release Scheme 在 xcode5 上为 iOS7 存档我的应​​用程序，并正确的 Provisioning Distribution

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

那是屏幕:

这是在项目

这是在Target

我尝试做许多不同的资产，我确定我的 Building Archive 是在 Release 上，但 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:

亲爱的开发者:

我们发现您最近的交货有一个或多个问题我的应用程序".要处理您的交货，必须解决以下问题更正:

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 目标，而不是 Simulator 目标.如果你是确定您的代码签名设置是正确的，请选择全部清除"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****

Ahority 屏幕是对的

推荐答案

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

In Xcode, at the target level do the following:

1. 首先为发布配置选择配置文件.(对于Any SDK)配置文件必须匹配应用的Bundle ID(正如您在常规"标签中看到的那样).
2. 在代码签名标识中，点击Any iOS SDK 的子菜单并确保选择Automatic.如果你看不到下面.
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 步中，如果您不能选择 Automatic，则表示您的 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屋！