blocks|key|2899292|text|您确定您构建的是发行版，而不是开发、证书和移动设备吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2899293|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|$]]

Are you sure you're building with a distribution, as opposed to development, certificate and mobileprovision?

blocks|key|2899331|text|我想你是在上传一个.zip文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2899332|我刚刚查看了我上传的一个应用程序，CFBundleResourceSpecification只在签名版本中(即设备构建)。|2899333|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 assume you're uploading a .zip file.

I just checked an app I uploaded, and CFBundleResourceSpecification is only in the signed versions (i.e. the device builds).

blocks|key|1217363|text|您是否正在从命令行执行任何构建/复制/压缩操作？如果是这样的话，你必须非常小心符号链接。.app附带一个子目录作为另一个子目录的符号链接，如果您没有正确的标志复制或压缩它，它将硬复制内容，这会扰乱协同设计。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1217364|这种情况发生在我身上-最糟糕的是，没有符号链接的临时构建运行良好，所以在应用程序商店构建之前，您不会注意到这个问题。|1217365|entityMap^0|18|4|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

Are you doing any of your building/copying/zipping from the command line? If so, you have to be very careful about symbolic links. The <code>.app</code> comes with a subdirectory as a symbolic link to another, and if you copy it or zip it without the right flags, it'll hard-copy the contents, which messes with the codesigning.

This happened to me - and the worst part is, the ad-hoc builds work fine without the symbolic link, so you don't notice the problem until the app store build.

blocks|key|1375556|text|问题似乎是，我在我的应用程序中使用了json-框架，并将它作为每个wiki中的说明的附加SDK。我的猜测是，XCode被>1SDK的存在搞糊涂了，因此无法找到默认的ResourceRules.plist。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1375557|我找到了两个解决方案(不管怎样，解决办法是这样的)：|1375558|使用“代码签名资源规则路径”生成设置(默认为空白)指定XCode应该使用的文件的路径：$(SDKROOT)/ResourceRules.plist。这是可行的，而且似乎是无害的，但令人沮丧的是，XCode应该能够自己解决这个问题。(我在json框架上的一个很老的问题文件中找到了这个解决方案。)|ordered-list-item|style|CODE|1375559|不要使用SDK方法。相反，只需将文件直接包含到项目中，并使用本地路径更新#import语句。这就是我最后采取的方法，因为我们做出了一个一般性决定，将所有外部依赖项折叠到项目本身中(这样，其他开发人员在他们的机器上可以进行更少的配置来启动和运行)。|1375560|我不确定这是XCode中的bug，还是json框架的错误，但我已经对后者进行了提出了一个问题，以防万一。|1375561|更新，2010年6月30日:我提交的问题已经结束，Brautaset先生计划在项目的下一个版本(2.3)中取消对SDK选项的支持。此外，代码现在生活在GitHub上，虽然谷歌代码页仍然存在，目前。|BOLD|1375562|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/json-framework/|1|http://code.google.com/p/json-framework/wiki/InstallationInstructions#Option_2:_Use_the_iPhone_Custom_SDK|2|http://code.google.com/p/json-framework/issues/detail?id=18|3|http://code.google.com/p/json-framework/issues/detail?id=58|4|http://github.com/stig/json-framework^0|I|7|0|X|8|1|0|0|17|U|3K|5|2|0|10|7|0|13|7|3|0|0|K|1W|E|4|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@$A|18|B|19|1|1A]|$A|1B|B|1C|1|1D]]|C|$]]|$1|D|3|E|5|6|7|1E|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|1F|8|@$A|1G|B|1H|I|J]]|9|@$A|1I|B|1J|1|1K]]|C|$]]|$1|K|3|L|5|H|7|1L|8|@$A|1M|B|1N|I|J]]|9|@]|C|$]]|$1|M|3|N|5|6|7|1O|8|@]|9|@$A|1P|B|1Q|1|1R]]|C|$]]|$1|O|3|P|5|6|7|1S|8|@$A|1T|B|1U|I|Q]]|9|@$A|1V|B|1W|1|1X]]|C|$]]|$1|R|3|-4|5|6|7|1Y|8|@]|9|@]|C|$]]]|S|$T|$5|U|V|W|C|$X|Y]]|Z|$5|U|V|W|C|$X|10]]|11|$5|U|V|W|C|$X|12]]|13|$5|U|V|W|C|$X|14]]|15|$5|U|V|W|C|$X|16]]]]

The problem seems to have been that I was using <a href="http://code.google.com/p/json-framework/" rel="nofollow noreferrer">json-framework</a> in my app, and including it as an additional SDK per <a href="http://code.google.com/p/json-framework/wiki/InstallationInstructions#Option_2:_Use_the_iPhone_Custom_SDK" rel="nofollow noreferrer">the instructions in the wiki</a>. My guess is that XCode got confused by the presence of >1 SDK, and thus couldn't find the default ResourceRules.plist like it's supposed to.

I found two solutions (well, workarounds, anyway):

<ol>
<li>Use the "Code Signing Resource Rules Path" build setting (which is blank by default) to specify the path to the file XCode should use: <code>$(SDKROOT)/ResourceRules.plist</code>. This works, and seems reasonably harmless, but is frustrating in the sense that XCode should be able to figure this out on its own. (I found this solution in a <a href="http://code.google.com/p/json-framework/issues/detail?id=18" rel="nofollow noreferrer">very old issue</a> filed on json-framework.)</li>
<li>Don't use the SDK approach. Instead, just include the files directly into the project, and update the <code>#import</code> statements with local paths. This is the approach I ended up taking, since we made a general decision to fold all of the external dependencies into the project itself (so that other developers have less configuration to do on their machines to get up and running).</li>
</ol>

I'm not sure whether this is a bug in XCode, or something wrong with json-framework but I've <a href="http://code.google.com/p/json-framework/issues/detail?id=58" rel="nofollow noreferrer">filed an issue</a> on the latter just in case.

UPDATE, 30 June 2010: the issue I filed has been closed, and Mr. Brautaset plans to remove support for the SDK option in the next release (2.3) of the project. Also, the <a href="http://github.com/stig/json-framework" rel="nofollow noreferrer">code now lives on GitHub</a>, though the Google Code pages still exist for now.

blocks|key|2899594|text|这个消息可能有另一个原因(正如我今天早上所发现的)：如果您的项目中有多个Info.plists，Application可能会发现“错误”的Info.plist并感到困惑。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2899595|这种情况发生在我身上，因为构建的一个自动化部分是在一个捆绑包中创建一个Info.plist。|2899596|这里是解决方案的提示：http://infinite-sushi.com/2010/08/the-case-of-the-missing-cfbundleresourcespecification/|offset|length|2899597|entityMap|0|LINK|mutability|MUTABLE|url|http://infinite-sushi.com/2010/08/the-case-of-the-missing-cfbundleresourcespecification/^0|0|0|B|2G|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

This message can happen for another reason (as I've just discovered this morning): if your project has multiple Info.plists in it, the Application Uploader may discover the "wrong" Info.plist and get confused. 

This was happening to me because an automated part of the build was creating an Info.plist in a bundle brought into the project.

Hat tip to here for the solution:
<a href="http://infinite-sushi.com/2010/08/the-case-of-the-missing-cfbundleresourcespecification/" rel="nofollow noreferrer">http://infinite-sushi.com/2010/08/the-case-of-the-missing-cfbundleresourcespecification/</a>

blocks|key|1218714|text|对我来说，在检查完所有内容后(codesign，图标文件.)但是你不能上传你的应用程序，尝试删除构建的文件。记得复制file.app来压缩你的应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1218715|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 me, after checking all things (codesign, the icon file...) but you can't upload your App, try to delete the Built File. Remember copying file.app to zip your app.

blocks|key|2899649|text|对我来说，解决方案是在：Apple+Developer供应门户创建一个分发证书。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2899650|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.apple.com/ios/manage/provisioningprofiles/viewDistributionProfiles.action^0|C|J|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>.

We've finally gotten to the point of submitting our first iPhone app to the app store (or trying to), but I can't seem to get iTunes Connect to accept the upload.

I've attempted through both the web site ("The binary you uploaded was invalid. The signature was invalid, or it was not signed with an Apple submission certificate.") and the Application Loader ("Info.plist does not contain a CFBundleResourceSpecification").

After lots of reading (including <a href="https://stackoverflow.com/search?q=binary+you+uploaded+was+invalid">questions like these</a>), re-reading, and googling, I can say that:

<ul>
<li>I'm sure that the bundle identifier matches the AppID.</li>
<li>There is an Icon.png, it's a 57x57 px PNG file, and that's the exact name in the Info.plist.</li>
<li>I'm doing a device, not simulator, build.</li>
<li>The signing process succeeds: the build results show this, and running <code>codesign -vvvv MyApp.app</code> indicates no problems.</li>
<li>There are no strange characters in the path to the ZIP file.</li>
<li>I've deleted the build folder and re-built the binary quite a few times.</li>
</ul>

Now, it is true that in the built app, the Info.plist does not contain a <code>CFBundleResourceSpecification</code> key, but it's not at all clear to me where that value should come from, or what else I need to add to make this work. (The only reference I can find using Apple's search is some <a href="http://developer.apple.com/mac/library/releasenotes/Security/RN-CodeSigning/" rel="nofollow noreferrer">code signing release notes</a>... but, as I mentioned above, the code signing step is succeeding, as far as I can tell.)

Has anyone run across any explanations for this problem that I haven't mentioned already?

EDIT: Here's the (slightly redacted) output from the code signing step of the build, FWIW:

<a href="http://img70.yfrog.com/img70/8988/codesign.png" rel="nofollow noreferrer">code signing screenshot http://img70.yfrog.com/img70/8988/codesign.png</a>

Can't upload application binary to the App Store

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我们终于到了将我们的第一个iPhone应用提交到应用商店(或试图)的地步，但我似乎无法让iTunes连接来接受上传。我试图通过这两个网站(“您上传的二进制文件无效。签名无效，或者它没有用苹果提交证书签名)。”以及Application ("Info.plist不包含CFBundleResourceSpecificati...

问无法将应用程序二进制文件上载到App
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法将应用程序二进制文件上载到AppEN