blocks|key|3372941|text|好吧，在重复了几次这些步骤之后，我终于成功地上传了我的应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3372942|我不知道到底是什么修复了它，但在成功尝试之前，我关闭了Xcode和Firefox，并重新启动了它们。我猜其中一个应用程序有一些不好的魔力。|3372943|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Well, after repeating the steps several times, I was finally successful in uploading my app.

I don't know exactly what fixed it, but prior to the successful attempt, I closed Xcode and Firefox and restarted them. I guess one of those apps had some bad juju.

blocks|key|364275|text|根据我的经验，Xcode有时会对使用哪个签名证书感到困惑。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|364276|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It's been my experience that Xcode occasionally gets confused about which signing certificate to use. I got into the habit of quitting and restarting Xcode after any change to the code signing settings (and doing a clean build) to work around this problem.

blocks|key|369146|text|我也遇到了同样的问题，并以这种方式解决了它：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|369147|属性证书安装在我的开发机器上，mobileprovision.embedded包含在分发存档中。经过大约一个小时的谷歌搜索和挖掘，我找到了错误的来源。在Xcode中，我复制了发布配置并创建了一个新的分发配置，然后将签名身份更改为我的分发证书。但是，即使在GUI中进行了更新，项目文件也没有正确更新。|369148|如果您遇到相同的错误，请在您的ProjectName.xcodeproj目录中查找project.pbxproj文件，并在您喜欢的编辑器中打开它。查找“分发”部分。我的坏掉的那个看起来像这样：|369149|C384C90C0F9939FA00E76E41+/*+Distribution+*/+=+{
isa+=+XCBuildConfiguration;
buildSettings+=+{
ARCHS+=+"$(ARCHS_STANDARD_32_BIT)";
CODE_SIGN_ENTITLEMENTS+=+"";
"CODE_SIGN_IDENTITY[sdk=iphoneos*]”+=+“iPhone+Distribution:+Edward+McCreary”;
GCC_C_LANGUAGE_STANDARD+=+c99;
GCC_WARN_ABOUT_RETURN_TYPE+=+YES;
GCC_WARN_UNUSED_VARIABLE+=+YES;
PREBINDING+=+NO;
“PROVISIONING_PROFILE[sdk=iphoneos*]”+=+“F00D3778-32B2-4550-9FCE-1A4090344400″;
SDKROOT+=+iphoneos2.2.1;
};
name+=+Distribution;
};
C384C90D0F9939FA00E76E41+/*+Distribution+*/+=+{
isa+=+XCBuildConfiguration;
buildSettings+=+{
ALWAYS_SEARCH_USER_PATHS+=+NO;
CODE_SIGN_IDENTITY+=+“iPhone+Developer:+Edward+McCreary”;
“CODE_SIGN_IDENTITY[sdk=iphoneos*]”+=+“iPhone+Developer:+Edward+McCreary”;
COPY_PHASE_STRIP+=+YES;
GCC_PRECOMPILE_PREFIX_HEADER+=+YES;
GCC_PREFIX_HEADER+=+GenPass_Prefix.pch;
INFOPLIST_FILE+=+Info.plist;
PRODUCT_NAME+=+GenPass;
PROVISIONING_PROFILE+=+“DB12BCA7-FE72-42CA-9C2B-612F76619788″;
“PROVISIONING_PROFILE[sdk=iphoneos*]”+=+“DB12BCA7-FE72-42CA-9C2B-612F76619788″;
};
name+=+Distribution;
};|code-block|syntax|javascript|369150|您可以在第二部分中看到签名身份和配置配置文件不正确。编辑它以匹配第一部分，即rebuild，您就应该可以开始工作了。最后一个看起来像这样：|369151|C384C90C0F9939FA00E76E41+/*+Distribution+*/+=+{
isa+=+XCBuildConfiguration;
buildSettings+=+{
ARCHS+=+"$(ARCHS_STANDARD_32_BIT)";
CODE_SIGN_ENTITLEMENTS+=+"";
"CODE_SIGN_IDENTITY[sdk=iphoneos*]”+=+“iPhone+Distribution:+Edward+McCreary”;
GCC_C_LANGUAGE_STANDARD+=+c99;
GCC_WARN_ABOUT_RETURN_TYPE+=+YES;
GCC_WARN_UNUSED_VARIABLE+=+YES;
PREBINDING+=+NO;
“PROVISIONING_PROFILE[sdk=iphoneos*]”+=+“F00D3778-32B2-4550-9FCE-1A4090344400″;
SDKROOT+=+iphoneos2.2.1;
};
name+=+Distribution;
};
C384C90D0F9939FA00E76E41+/*+Distribution+*/+=+{
isa+=+XCBuildConfiguration;
buildSettings+=+{
ALWAYS_SEARCH_USER_PATHS+=+NO;
CODE_SIGN_IDENTITY+=+“iPhone+Distribution:+Edward+McCreary”;
“CODE_SIGN_IDENTITY[sdk=iphoneos*]”+=+“iPhone+Distribution:+Edward+McCreary”;
COPY_PHASE_STRIP+=+YES;
GCC_PRECOMPILE_PREFIX_HEADER+=+YES;
GCC_PREFIX_HEADER+=+GenPass_Prefix.pch;
INFOPLIST_FILE+=+Info.plist;
PRODUCT_NAME+=+GenPass;
PROVISIONING_PROFILE+=+“F00D3778-32B2-4550-9FCE-1A4090344400″;
“PROVISIONING_PROFILE[sdk=iphoneos*]”+=+“F00D3778-32B2-4550-9FCE-1A4090344400″;
};
name+=+Distribution;
};|369152|guids改变是为了保护无辜的人|369153|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|X|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

I had the same issue and solved it this way:

The property certificates were installed on my development machine and mobileprovision.embedded was included in the distribution archive. After an hour or so of Googling and digging I found the source the error. Inside Xcode I had copied the Release configuration and created a new Distribution configuration and then changed the signing identity to my distribution certificate. However, even though it was updated in the GUI the project file was not updated correctly.

If you come across the same error, look in your [ProjectName].xcodeproj directory for the project.pbxproj file and open it in your favorite editor. Look for the Distribution section. My broken one looked like this:

<pre><code>C384C90C0F9939FA00E76E41 /* Distribution */ = {
isa = XCBuildConfiguration;
buildSettings = {
ARCHS = "$(ARCHS_STANDARD_32_BIT)";
CODE_SIGN_ENTITLEMENTS = "";
"CODE_SIGN_IDENTITY[sdk=iphoneos*]” = “iPhone Distribution: Edward McCreary”;
GCC_C_LANGUAGE_STANDARD = c99;
GCC_WARN_ABOUT_RETURN_TYPE = YES;
GCC_WARN_UNUSED_VARIABLE = YES;
PREBINDING = NO;
“PROVISIONING_PROFILE[sdk=iphoneos*]” = “F00D3778-32B2-4550-9FCE-1A4090344400″;
SDKROOT = iphoneos2.2.1;
};
name = Distribution;
};
C384C90D0F9939FA00E76E41 /* Distribution */ = {
isa = XCBuildConfiguration;
buildSettings = {
ALWAYS_SEARCH_USER_PATHS = NO;
CODE_SIGN_IDENTITY = “iPhone Developer: Edward McCreary”;
“CODE_SIGN_IDENTITY[sdk=iphoneos*]” = “iPhone Developer: Edward McCreary”;
COPY_PHASE_STRIP = YES;
GCC_PRECOMPILE_PREFIX_HEADER = YES;
GCC_PREFIX_HEADER = GenPass_Prefix.pch;
INFOPLIST_FILE = Info.plist;
PRODUCT_NAME = GenPass;
PROVISIONING_PROFILE = “DB12BCA7-FE72-42CA-9C2B-612F76619788″;
“PROVISIONING_PROFILE[sdk=iphoneos*]” = “DB12BCA7-FE72-42CA-9C2B-612F76619788″;
};
name = Distribution;
};
</code></pre>

You can see the signing identity and provisioning profile are incorrect in the second section. Edit it to match the first section, rebuild, and you should be good to go. The final one looked like this:

<pre><code>C384C90C0F9939FA00E76E41 /* Distribution */ = {
isa = XCBuildConfiguration;
buildSettings = {
ARCHS = "$(ARCHS_STANDARD_32_BIT)";
CODE_SIGN_ENTITLEMENTS = "";
"CODE_SIGN_IDENTITY[sdk=iphoneos*]” = “iPhone Distribution: Edward McCreary”;
GCC_C_LANGUAGE_STANDARD = c99;
GCC_WARN_ABOUT_RETURN_TYPE = YES;
GCC_WARN_UNUSED_VARIABLE = YES;
PREBINDING = NO;
“PROVISIONING_PROFILE[sdk=iphoneos*]” = “F00D3778-32B2-4550-9FCE-1A4090344400″;
SDKROOT = iphoneos2.2.1;
};
name = Distribution;
};
C384C90D0F9939FA00E76E41 /* Distribution */ = {
isa = XCBuildConfiguration;
buildSettings = {
ALWAYS_SEARCH_USER_PATHS = NO;
CODE_SIGN_IDENTITY = “iPhone Distribution: Edward McCreary”;
“CODE_SIGN_IDENTITY[sdk=iphoneos*]” = “iPhone Distribution: Edward McCreary”;
COPY_PHASE_STRIP = YES;
GCC_PRECOMPILE_PREFIX_HEADER = YES;
GCC_PREFIX_HEADER = GenPass_Prefix.pch;
INFOPLIST_FILE = Info.plist;
PRODUCT_NAME = GenPass;
PROVISIONING_PROFILE = “F00D3778-32B2-4550-9FCE-1A4090344400″;
“PROVISIONING_PROFILE[sdk=iphoneos*]” = “F00D3778-32B2-4550-9FCE-1A4090344400″;
};
name = Distribution;
};
</code></pre>

guids changed to protect the innocent

blocks|key|3373208|text|这是我遇到的一个问题:我在上传之前将二进制文件添加到Subversion中。比较/压缩二进制文件，然后包含隐藏的.svn目录，这会使代码签名变得混乱。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3373209|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Here's an issue I ran into: I added the binary to Subversion before uploading. Comparessing/zipping the binary then included the hidden .svn directories, which messed up the code signing.

blocks|key|3373220|text|同样的问题，不同的解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3373221|在我的例子中，我使用zip+-r+myapp.zip+myapp.app压缩文件，结果是zip命令破坏了捆绑包。从搜索器上压缩后就能工作了。|offset|length|style|CODE|3373222|entityMap^0|0|A|Q|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Same problem, different solution.

In my case, I was compressing the file using <code>zip -r myapp.zip myapp.app</code>
Turns out, the zip command screwed the bundle. Compressing it from the finder made it work.

blocks|key|369170|text|我只想提一下，我也有从命令行压缩的问题。问题出在默认情况下它处理符号链接的方式。使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|369171|zip+-y+-r+myapp.zip+myapp.app|369172|解决了这个问题。|369173|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I just wanted to mention that I too had the problem with zip from the command
line as well. The problem lies in the way it handles symlinks by default. Using:

zip -y -r myapp.zip myapp.app

Solved that problem.

blocks|key|364342|text|在阅读了各种帖子后，我尝试了各种方法，包括上面的那些。最终对我起作用的是完全重新开始！我删除了与我的应用程序关联的每个证书和配置配置文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|364343|我重新创建了一个新的开发证书和一个新的分发证书。我重新下载了中间证书。然后，我重新创建了开发配置文件和分发配置文件。|364344|在安装了三个证书(我注意到这次发行版同时具有私钥和公钥)和两个配置配置文件(我的发行版配置文件没有标记为没有有效证书！)之后，一切都正常了。|364345|一旦我决定撤销所有东西并重新开始，创建新的东西并重新安装只需要大约5分钟。|364346|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I tried various things after reading various posts including those above. What finally worked for me was starting completely over! I deleted every certificate and provisioning profile associated with my app. 

I recreated a new development certificate and a new distribution certificate. I downloaded the intermediate certificate again. Then I recreated both the development profile and the distribution profile.

After installing the three certificates (I noticed the distribution had both private and public keys this time) and the two provisioning profiles (my distribution profile didn't get flagged as not having a valid certificate!), everything worked.

Once I made the decision to revoke everything and just start over, it only took about 5 minutes to create the new stuff and re-install.

blocks|key|3373308|text|我也有同样的问题，在构建时，我注意到配置没有添加到构建中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3373309|对我来说，的修复方法是将构建设置为我通常使用模拟器的位置，但随后它将不包含配置配置文件...|offset|length|style|BOLD|3373310|这可能是一个新手犯的错误。通常情况下，你不能构建到设备上，但是当你为发行版这样做时，你可以。|3373311|entityMap^0|0|5|15|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

I had the same problem aswell, when building I noticed the provisioning wasn't added in the build.

The fix for me was to set the build to the iphone device as where I normally use the simulator, but then it won't include the provisioning profile...

This might be a noob mistake. Normally you can't build to device, but when you do it for distribution you can.

blocks|key|3160511|text|我遇到了同样的问题，在尝试了几种方法之后--我从代码签名授权中删除了.plist授权(只是把它留空了)，它构建得很好，最后被上传了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3160512|祝大家好运:-D|3160513|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had the same issue and after trying several things - I removed the .plist entitlements from the Code Signing Entitlements (just left it blank) and it built fine and uploaded FINALLY.

Good luck all :-D

blocks|key|366093|text|今天刚遇到这个问题，但这里的答案没有帮助。我终于找到了问题所在。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|366094|确保使用下拉菜单：Project>Edit+Active+Target+"ProjectName“将代码签名更改为分发-我在组和文件窗格中选择项目，并使用信息按钮显示项目信息而不是目标信息-非常令人困惑！只有当我在项目中关闭代码签名并构建时才意识到，它仍然想要代码签名！|offset|length|style|BOLD|366095|我认为这就是为什么在埃迪的帖子中他必须在project.pbxproj级别上进行更改|366096|同样在第一步的原始帖子中:+1.在Xcode中，选择Device%7CRelease目标它肯定应该是Device%7CDistribution目标？(假设此版本已复制，并根据配置门户中的Apples说明将其重命名为Distribution+)|366097|entityMap^0|0|9|Q|2B|2|2I|2|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]|$D|R|E|S|F|G]|$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|M|$]]

Just had this problem today but the answers here didn't help. I finally found the problem.

Make sure using pull down menu: Project>Edit Active Target "ProjectName" to change Code Signing to Distribution - I was selecting the Project in the Groups &amp; Files pane and using the Info button which shows the PROJECT info rather than the TARGET info - very confusing! Only realized when I turned code signing off in the project and built and it still wanting to code sign!

I think this is why in Eddie's post he had to change it at the project.pbxproj level

Also on original post in 1st step:
1. In Xcode, select the Device|Release target
Surely it should be Device|Distribution target? (assuming this copied release and renamed it Distribution as per Apples instructions in the Provisioning Portal)

blocks|key|3373445|text|我的两点意见：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3373446|下载最新版本的应用程序加载器。我刚刚更新，现在得到了一个不同的错误消息。|3373447|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

My two cents:

Download the latest version of the Application Loader. I've just updated and now get a different error message.

blocks|key|365840|text|我也有同样的问题。我已经准备好在这个问题上认输了，但当我使用Murky签入我的代码时，我发现了这一点。我总是在签入之前浏览一下更改过的文件上的差异。当这次这样做时，我注意到project.pbxproj文件在分发部分有changed....and，“PROVISIONING_PROFILEsdk=iphoneos*”的条目是空的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|365841|退出和重启Xcode对我来说不起作用。相反，我进入了我的项目和目标设置，并更改了代码签名，以直接选择我的分发配置文件，而不是依赖于自动选择功能。这样做会导致project.pbxproj文件填充正确的值，即使自动选择功能假定选择的配置文件与我手动选择的配置文件完全相同。|365842|我需要一杯啤酒。|365843|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I had the same problem. I was ready to throw in the towel on this problem but I figured it out when I went to check in my code using Murky. I always skim the diffs on the files that changed before I check in. When doing so this time I noticed that the project.pbxproj file had changed....and in the Distribution section the entry for “PROVISIONING_PROFILE[sdk=iphoneos*]” was blank.

Quiting and restarting Xcode didn't work for me. Instead, I went into both my project and target settings and changed the code signing to directly select my Distribution profile rather than relying on the auto-select feature. Doing this caused the project.pbxproj file to populate with the correct values even though the auto-select feature supposedly selected the exact same profile that I selected manually.

I need a beer...

blocks|key|366151|text|我也有类似的问题，但我不使用entitlements.plist。然而，在十几次上传失败后，我检查了我的info.plist，发现了一些东西。我的CFBundleIconFiles数组有一个空条目。我删除了它并重新提交，它最终被接受了！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|366152|说真的，苹果要揭露这些验证错误有多难？|366153|编辑:由于CFBundleIconFiles使用了不同的名称，因此并不能立即显示出它们的位置。在项目信息视图中，单击并选择“显示原始键/值”，然后您将看到对CFBundleWhatever的引用。在这个编辑器的例子中，他试图使用一个不存在的icon=72-@2x.png文件。|366154|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I was having a similar problem, but I don't use entitlements.plist. However, after a dozen failed uploads, I checked my info.plist and discovered something. My CFBundleIconFiles array had an empty entry. I removed that and re-submitted, and it was finally accepted! 

Seriously, how hard would it be for Apple to expose those kind of validation errors?

Edit: It's not immediately apparant where the CFBundleIconFiles are because they use a different name. In the project info view, Ctl click and select "Show Raw Keys/Values" and then you will see the references to CFBundleWhatever. In this editor's case, he was trying to use a non-existent icon=72-@2x.png file.

blocks|key|3373570|text|有关解决方案，请参阅此链接：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3373571|http://greghaygood.com/2010/09/04/invalid-binary-message-from-itunesconnect|offset|length|3373572|简短的回答是：“最终我仔细检查了我的info.plist，发现了一些东西。我根据新的指南添加了CFBundleIconFiles，但数组列表中有一个空条目。我删除了它并重新提交，它最终被接受了！”|3373573|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|23|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

See this link for the solution:

<a href="http://greghaygood.com/2010/09/04/invalid-binary-message-from-itunesconnect" rel="noreferrer">http://greghaygood.com/2010/09/04/invalid-binary-message-from-itunesconnect</a>

The short answer is that "Eventually I double-checked my info.plist and discovered something. I added CFBundleIconFiles per the new guidelines, but there was an empty entry in the array list. I removed that and re-submitted, and it was finally accepted!"

blocks|key|3373595|text|我刚刚经历了这个麻烦(再次)，但这一次我发现我的分发配置文件的状态为“无效”。如果您认为其他一切正常，请仔细检查门户中的状态，并续订/重新下载任何未处于活动状态的内容。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3373596|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I just went through this hassle (again) but this time I found that my distribution profile had a status of "Invalid". If you think everything else is right, double-check the status in the portal and renew/re-download anything that isn't in the Active state.

blocks|key|364484|text|解决这个问题的方法是清理myProject.xcodeproj文件(右键单击，打开包)，包中包含来自共同开发人员的文件，删除这些文件后问题就解决了|type|unstyled|depth|inlineStyleRanges|entityRanges|data|364485|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Resolved this by cleaning up the myProject.xcodeproj file (right click, open package), the package contained files from co-developer, after deleting these the problem was solved

blocks|key|369341|text|在上传应用程序后，我收到了一个无效的二进制文件，但没有后续的电子邮件说明失败的原因。我试着一次做几件事，但我不确定下面哪一件能解决这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|369342|369343|重新启动Macbook+Pro|ordered-list-item|369344|将我的项目的源代码从NTFS驱动器移动到HFS%2B驱动器并重新编译。|369345|369346|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|L|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|M|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|N|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|J|$]]

I received an Invalid Binary after an app upload, with no e-mail followup as to why it failed. I tried doing a couple things at once, and I'm not sure which of the following actually fixed it:

<ol>
<li>Restarted Macbook Pro</li>
<li>Moved the source code for my project from an NTFS drive to an HFS+ drive and recompiled.</li>
</ol>

blocks|key|369375|text|我在Monotouch中也遇到过类似的问题。我发现我的发布配置文件被设置为使用开发人员证书。它应该看起来像这样：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|369376|📷|atomic|offset|length|369377|​|369378|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/b73225b23e807b0ac0a672128a55a0cf.png|imageAlt^0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|S|8|@]|9|@$E|T|F|U|1|V]]|A|$]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P|Q|-4]]]]

I had a similar issue but in Monotouch. I found that my Release profile was set to use developer certs. It should look like this:
<img src="https://i.stack.imgur.com/F9kuX.png" alt="enter image description here">

blocks|key|364526|text|对我来说，解决方案是在Apple+Developer+Provisioning+Portal上创建一个分发认证。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|364527|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.apple.com/ios/manage/provisioningprofiles/viewDistributionProfiles.action^0|B|Z|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

For me the solution was creating a distributing certification at:
<a href="http://developer.apple.com/ios/manage/provisioningprofiles/viewDistributionProfiles.action" rel="nofollow">Apple Developer Provisioning Portal</a>.

blocks|key|366311|text|我对此和4.3+GM+SDK有一个问题。我们的一个应用程序不会让它通过上传收到。事实证明，这是一个配置配置文件问题。我重新生成了应用商店配置文件，它工作得很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|366312|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had a problem with this and the 4.3 GM SDK. One of our apps would not make it past upload received. It turned out to be a provisioning profile issue. I regenerated the app store profile and it worked fine.

blocks|key|3161008|text|另一个数据点:有一段时间，我的应用程序通过了。现在我已经添加了对应用内购买的支持，但突然它失败了，并出现了“无效的二进制/无效的签名”问题。仔细查看后，我发现授权plist文件中的application-identifier的值是off。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3161009|这很可能是因为我已经将配置配置文件从通配符替换为应用程序特定的配置文件(应用内购买所必需的)。在旧配置文件下限定的应用程序ID错误。它与info.plist中的应用程序ID不匹配，但显然iTunes已经原谅了这一点。|3161010|所以，重述一下：|3161011|info.plist:+com.mydomain.foo
dist.plist:+com.mydomain.bar
Profile:+com.mydomain.*|code-block|syntax|javascript|3161012|是可以的，而|3161013|info.plist:+com.mydomain.foo
dist.plist:+com.mydomain.bar
Profile:+com.mydomain.foo|3161014|导致“无效的二进制文件”。|3161015|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|X|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Another data point: for a while, my app went through. Now I've added support for in-app purchases, and suddenly it fails with an "Invalid binary/invalid signature" problem. Upon careful looking, I found out that the value of application-identifier in the entitlements plist file was off.

This, most likely, had to do with the fact that I've replaced the provisioning profile from a wildcarded one to a app-specific one (required for in-app purchases). The wrong app ID qualified under the old profile. It did not match the app ID in the info.plist, but apparently iTunes forgave that.

So, to recap:

<pre><code>info.plist: com.mydomain.foo
dist.plist: com.mydomain.bar
Profile: com.mydomain.*
</code></pre>

is OK, while 

<pre><code>info.plist: com.mydomain.foo
dist.plist: com.mydomain.bar
Profile: com.mydomain.foo
</code></pre>

causes "Invalid binary".

blocks|key|3373885|text|如果应用程序不使用远程推送通知，我收到了一个无效的二进制文件，但我保留了注册推送的代码和注册/接收远程通知的回调委托的注释，即使代码没有使用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3373886|这是最近的。我上周提交的上一篇文章很好。本周，它返回无效的二进制文件。幸运的是，有一封电子邮件解释了这个错误。|3373887|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I received an invalid binary, if the app does not use remote push notification, but I left the code for registering push and the callback delegates for registering/receiving remote notification uncommented, even if the code does not get used. 

This is recent. My last submission last week was fine. This week, it returns invalid binary. Luckily, there is an email that explains the error.

blocks|key|366365|text|这个问题似乎有很多原因。下面是我的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|366366|这适用于属于多个开发团队的任何人(例如，您自己的应用程序和您的公司)。|366367|如果您使用一组凭据构建构建，并使用另一组凭据对其进行重新签名(例如，对于adhoc/appstore分发版)，则必须确保该构建最初是使用属于同一iOS开发团队的凭据构建和签名的，而您重新签名的分发凭据属于。|offset|length|style|BOLD|366368|因此，不要使用"Indy+Dev+Inc“凭据构建，然后尝试使用"Company+Inc”凭据进行部署。确保您同时设置了"Company+Inc“开发人员和分发凭据，并使用它们。|366369|我在我的博客上发布了更多关于这方面的信息：http://omegadelta.net/2011/06/09/fiendish-ios-code-signing-invalid-binary-issue/|366370|entityMap|0|LINK|mutability|MUTABLE|url|http://omegadelta.net/2011/06/09/fiendish-ios-code-signing-invalid-binary-issue/^0|0|0|1M|18|0|0|L|28|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@$F|Y|G|Z|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|11|8|@]|9|@$F|12|G|13|1|14]]|A|$]]|$1|N|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

It seems this issue has many causes. Here's the solution to mine:

This applies to anyone who belongs to multiple development teams (e.g. your own apps, and your companies).

If you building the build with one set of credentials and re-signing it with a different one (e.g. for adhoc/appstore distribution), you must ensure that the build was originally built &amp; signed with credentials belonging to the same iOS development team that the distribution credentials you are re-signing with belong to.

So don't build with "Indy Dev Inc" credentials then try to deploy with "Company Inc" credentials. Make sure you setup both "Company Inc" dev, and distribution credentials, and use them.

I posted more info about this on my blog: <a href="http://omegadelta.net/2011/06/09/fiendish-ios-code-signing-invalid-binary-issue/" rel="nofollow">http://omegadelta.net/2011/06/09/fiendish-ios-code-signing-invalid-binary-issue/</a>

blocks|key|3161103|text|对于它的价值，我想补充它是什么解决了这个问题为我。我有一个？(问号)在我的应用程序标题中导致了这个错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3161104|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For what it is worth, I want to add what it was that fixed this issue for me. I had a ? (question-mark) in my app title that was causing the error.

blocks|key|3373962|text|我的解决方案包括创建一个新的应用程序ID。我不确定这到底是为什么修复它，但我怀疑它可能是不匹配的捆绑标识符-创建新的应用程序ID迫使我确保我的应用程序和iTunes期望相同的东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3373963|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

My solution involved creating a new App ID. I'm not sure exactly why that fixed it, but I suspect it may have been mismatched Bundle Identifiers — creating the new App ID forced me to make sure my app and iTunes were expecting the same thing.

blocks|key|3374049|text|在尝试了这里列出的所有其他修复后，我们在Apple上记录了TSI。在遵循了Technical+Note+TN2250中的所有步骤之后，我们的问题是因为缺少或无效的密封资源而导致的。在我们的例子中，它是._.DS_Store。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3374050|"..“被称为Apple双文件，是将Xcode项目文件夹*解压缩*复制到一个不能正确支持HFS%2B的“资源分支”(用于代码签名)的文件系统上并从该文件系统返回的结果。这些额外的"..“文件结果并导致代码签名验证失败。|3374051|要从Xcode项目文件夹中清除有问题的Apple+Double文件，请在Xcode项目的文件夹上运行dot_clean命令，执行一个干净的构建，然后重新归档并重新尝试提交。|3374052|dot_clean+/the/path/to/xcode/project|code-block|syntax|javascript|3374053|注意:您只需将项目文件夹拖入终端即可自动填充路径|3374054|运行该命令时没有消息，但项目生成可能会在您下次生成时显示有关该文件的警告。你可以忽略这一点，应用程序将验证并提交成功。|3374055|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/legacy/library/technotes/tn2250/_index.html#//apple_ref/doc/uid/DTS40009933^0|2S|B|11|L|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@$9|13|A|14|1|15]]|E|$]]|$1|F|3|G|5|6|7|16|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|17|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|18|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|19|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1A|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]]|T|$U|$5|V|W|X|E|$Y|Z]]]]

After trying all of the other fixes listed here we logged a TSI with Apple. Having followed all the steps in <a href="https://developer.apple.com/legacy/library/technotes/tn2250/_index.html#//apple_ref/doc/uid/DTS40009933" rel="nofollow noreferrer">Technical Note TN2250</a> our problem was caused because a sealed resource was missing or invalid. In our case it was <code>._.DS_Store</code>.

The ".." is called an Apple Double file, and is the result of copying the Xcode Project folder, *unzipped*, onto and back from a file system that doesn't properly support HFS+'s 'resource forks' (used for code signatures). These extra ".." files result and cause code signing verification failure.

To clean the problematic Apple Double files from your Xcode project folder, run the dot_clean command on your Xcode project's folder, do a clean build, and then rearchive and reattempt your submission. 

<pre><code>dot_clean /the/path/to/xcode/project
</code></pre>

Note: You can just drag the project folder into the terminal to automatically populate the path

There is no message when you run the command but the project build might show a warning about the file when you next build. You can ignore this, the app will validate and submit successfully.

blocks|key|3161217|text|另一种解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3161218|对我来说，只需在“代码签名”下设置“发布”证书就可以解决这个问题。它们最初被设置为“不要编码签名”。|3161219|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Another solution:

For me simply setting the 'Release' certificates under 'code signing' fixed it. They were initially set to 'Don't code sign'.

blocks|key|369532|text|对我来说，这个问题是通过重新保存带有非交错选项的PNG图像来解决的。在以前的版本中，交错的png是允许的，但知道这个图像可能会导致无效的二进制文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|369533|我的苹果信息:损坏的图标文件-图标文件iconGQ@2x.png似乎已损坏。您的图标不能是交错的PNG文件。|369534|您可以在终端中使用命令"+file“查看PNG是否隔行扫描:+Eva-Madrazos-MacBook-Pro-2:GQ+7+integracion+ads+Eva$+file+*.png+Default.png:+PNG+image+data，320+x+480，8位/彩色RGB，非隔行扫描|369535|祝你好运，伊娃|369536|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

For me the problem was solved by resaving a PNG image with the non-interlaced option. In previous versions interlaced png were allowed, but know this images can cause the invalid binary.

My apple message:
Corrupt Icon File - The icon file iconGQ@2x.png appears to be corrupt. Your icon must not be an interlaced PNG file. 

You can see if the PNG is interlaced using the command "file" in the terminal:
Eva-Madrazos-MacBook-Pro-2:GQ 7 integracion ads Eva$ file *.png
Default.png: PNG image data, 320 x 480, 8-bit/color RGB, non-interlaced

Good luck,
 Eva

blocks|key|3161294|text|我想指出给苹果发电子邮件的可能性，并要求他们检查他们的日志。在尝试了很多东西之后，我就这么做了。近四周后，有必要提醒他们，但最终他们回复并指出了问题的确切位置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3161295|在我的案例中，问题是我之前尝试过其他应用程序图标，对旧图像的引用仍然保留在“CFBundleIcons”中。我使用了拖放功能来设置图标，但我没有注意到，在添加新引用之前，旧内容并没有完全清除。|3161296|要查看错误的引用，有必要展开箭头以查看plist文件中的每个子元素。提示之一是在文件中单击鼠标右键，然后选择查看原始内容的选项。这样你就不需要扩展任何东西了。|3161297|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I want to point out the possibility to email Apple and ask them to check their logs. I did just that, after having tried loads of things first. It was necessary to remind them after almost four weeks, but finally they replied and pointed to the exact spot of the issue. 

The problem in my case was that I had previously tried other app icons, and a reference to the old image still remained in 'CFBundleIcons'. I used the drag and drop functionality to set the icon, but I didn't notice that the old content wasn't completely cleared before the new reference was added. 

To see the faulty reference it was necessary to expand the arrows to view each and every sub element in the plist file. One tips is to right-click in the file and select the option for viewing the raw content. In that way you will not need to expand anything.

blocks|key|369553|text|我尝试了所有其他提出的解决方案，但都没有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|369554|我最终创建了一个新的Xcode项目，并将我所有的代码和资源复制到其中。这就成功了，我的应用程序被放到了审查队列中。|offset|length|style|BOLD|369555|我还可以推荐使用Apples+technical+notes+on+code+signing进行调试/验证。|369556|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.apple.com/library/ios/#technotes/tn2250/_index.html^0|0|8|9|0|8|12|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

I tried all other proposed solutions, but nothing helped.

I ended up creating a new Xcode project and copy all my code and resources into it. That did the trick, and my app got placed into the review queue.

I can also recommend <a href="http://developer.apple.com/library/ios/#technotes/tn2250/_index.html" rel="nofollow">Apples technical notes on code signing</a> for debugging/verification.

blocks|key|366487|text|不允许使用uuid。我通过移除所有[UIDevice+currentDevice+uniqueIdentifier]修复了它；|type|unstyled|depth|inlineStyleRanges|entityRanges|data|366488|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

uuid is not allowed.
I fixed it by remove all [[UIDevice currentDevice] uniqueIdentifier];

blocks|key|3374229|text|截至2013年5月1日，苹果更新了iPhone人机界面指南，如果你想上传一个新的应用程序或更新，它必须是iPhone5(4英寸)友好的-这意味着它不应该是一个3.5英寸的应用程序运行在更大的屏幕上。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3374230|来自苹果：|3374231|3374232|亲爱的开发人员：|blockquote|3374233|3374234|我们发现您最近交付的“-”存在一个或多个问题。要处理您的交付，必须更正以下问题：|3374235|iPhone+5优化要求-您的二进制文件未针对iPhone+5进行优化。从5月1日起，所有提交的新iPhone应用程序和应用程序更新都必须支持iPhone+5上的4英寸显示屏。所有应用程序都必须包含适当大小的启动图像。通过查看iOS人机接口指南，了解有关iPhone+5支持的更多信息。|3374236|纠正这些问题后，转到版本详细信息页面并单击“准备上传二进制文件”。继续执行提交过程，直到应用程序状态为“正在等待上传”。然后，您可以交付更正后的二进制文件。|3374237|致以敬意，|3374238|应用商店团队|3374239|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|X|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|11|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

As of May 1st 2013, Apple updated their iOS Human Interface Guidelines so that if you wish to upload a new app or an update, it must be iphone 5 (4inch) friendly - meaning it should not be a 3.5inch app running on the bigger screen. 

From apple: 

<blockquote>
 Dear developer,
 
 We have discovered one or more issues with your recent delivery for
 "-------------". To process your delivery, the following issues must
 be corrected:
 
 iPhone 5 Optimization Requirement - Your binary is not optimized for
 iPhone 5. As of May 1, all new iPhone apps and app updates submitted
 must support the 4-inch display on iPhone 5. All apps must include a
 launch image of the appropriate size. Learn more about iPhone 5
 support by reviewing the iOS Human Interface Guidelines.
 
 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.
 
 Regards,
 
 The App Store team
</blockquote>

blocks|key|3161393|text|还有一个情况下，二进制文件将被认为是无效的。从2015年2月1日开始，新的iOS应用程序需要支持64位架构。以下是来自苹果的电子邮件：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3161394|3161395|亲爱的开发人员：|blockquote|3161396|3161397|我们发现您最近交付的"Home+-+Recruitment“存在一个或多个问题。要处理您的交付，必须更正以下问题：|3161398|缺少64位支持-从2015年2月1日起，提交到应用商店的新iOS应用必须包含64位支持，并且必须使用iOS+8软件开发工具包构建。从2015年6月1日开始，应用程序更新也需要遵循相同的要求。要在您的项目中启用64位，我们建议使用默认的Xcode构建设置“Standard+architectures”来构建包含32位和64位代码的单个二进制文件。|3161399|一旦纠正了这些问题，您就可以重新交付更正后的二进制文件。|3161400|致以敬意，|3161401|应用商店团队|3161402|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|U|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

There is one more instance when the binary will be deemed invalid. Starting February 1, 2015 new iOS apps need to support 64-bit architecture. Here is the email from apple:

<blockquote>
 Dear developer,
 
 We have discovered one or more issues with your recent delivery for
 "Home - Recruitment". To process your delivery, the following issues
 must be corrected:
 
 Missing 64-bit support - Beginning on February 1, 2015 new iOS apps
 submitted to the App Store must include 64-bit support and be built
 with the iOS 8 SDK. Beginning June 1, 2015 app updates will also need
 to follow the same requirements. To enable 64-bit in your project, we
 recommend using the default Xcode build setting of “Standard
 architectures” to build a single binary with both 32-bit and 64-bit
 code.
 
 Once these issues have been corrected, you can then redeliver the
 corrected binary.
 
 Regards,
 
 The App Store team
</blockquote>

blocks|key|366526|text|在我的例子中，它是包含在项目二进制文件中的TestFlight+SDK。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|366527|我从一个不同的旧项目源(包括testflight)创建了一个新项目，但由于此项目是具有新is的新项目，因此这里不再允许使用TestFlight+SDK。|366528|我删除了它，然后归档并再次上传。这次没有“无效的二进制”错误。|366529|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

In my case, it was the TestFlight SDK included in the project binary.

I created an new project from a different old project source (that included testflight), but since this project is a new one with new IDs, TestFlight SDK is no longer allowed here.

I removed it, then archived and uploaded it again. No "invalid binary" error this time.

I'm trying to upload an application to the iPhone App Store, but I get this error message from iTunes Connect:

<blockquote>
 The binary you uploaded was invalid. The signature was invalid, or it was not signed with an Apple submission certificate.
</blockquote>

<hr>

Note: The details of original question have been removed, as this page has turned into a repository for all information about possible causes of that particular error message.

For general information on submitting iPhone applications to the App Store, see <a href="https://stackoverflow.com/questions/796482/steps-to-upload-an-iphone-application-to-the-appstore">Steps to upload an iPhone application to the AppStore</a>.

Invalid iPhone Application Binary

软件开发

文件系统

Xcode

我正在尝试将应用程序上传到iPhone应用商店，但从iTunes连接收到以下错误消息：您上传的二进制文件无效。签名无效，或者没有使用Apple提交证书签名。注意:原始问题的详细信息已被删除，因为此页面已变成一个存储库，其中包含有关该特定错误消息的可能原因的所有信息。有关将iPhone应用程序提交到App Store的一...

问无效的iPhone应用程序二进制文件
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无效的iPhone应用程序二进制文件EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无效的iPhone应用程序二进制文件
EN