无法上传由 ios5 构建的应用程序 - 与 UIRequiredDeviceCapability 问题相关
我面临一个问题，我像以前一样使用 ios 5 构建分发版本应用程序， 当我将二进制应用程序上传到 iTunes 时，它报告错误如下：
“此捆绑包无效，info.plist 中的关键 UIRequiredDeviceCapability 可能不包含阻止此应用程序运行的值......”
我也搜索此类类型问题，我得到的答案是，我必须从 iTunes 中删除旧版本的应用程序（这将丢弃旧的应用程序用户和评级）并将新的应用程序上传到 iTunes…这种方式看起来是糟糕的解决方案，我想保留旧的应用程序用户…任何人都可以提供帮助这个目的？非常感谢
I face a problem, I use ios 5 build the distribute version app as before,
while I upload the binary app to iTunes, it report error as follows:
"This bundle is invalid, The key UIRequiredDeviceCapabilities in the info.plist may not contains values that would prevent this application from running on…"
I also googing such type problem, I got answer that say I have to remove the old version app from iTunes (this will discard old app user and rating) and upload new app to iTunes … this way looks is bad solution, I want keep old app users… anyone can help for this purpose ? thanks a lots
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
我遇到了同样的问题，我将我的 plist 文件与运行良好的旧版本进行了比较，并且所需的设备功能行甚至不存在。删除这些值，以便该行不存在，这样就可以解决它。
I had the same issue, I compared my plist file to an older build that worked fine and the Required Device Capabilities row didn't even exist. Delete the values so the row is not present and that should take care of it.
是的，删除所需的设备功能行就可以了！
Yes , remove Required Device Capabilities row is ok!
我在 Xcode 4.2 之前创建的一些项目中看到了这个问题，然后使用 Xcode 4.2 将二进制文件提交到应用程序商店。
您需要进入您的信息列表并添加“所需设备功能”键。该键是一个数组，您需要两个字符串项：“armv6”和“armv7”。
plist 源看起来像这样：
I have seen this issue in a few projects that were created prior to Xcode 4.2, and then used Xcode 4.2 to submit the binary to the app store.
You need to go into your info-plist and add the key "Required Device Capabilities". This key is an array, and you need two string items: "armv6" and "armv7".
The plist source looks like this:
我们尝试了上面列出的解决方案，并将armv6和armv7添加到我们的info.plist文件中。但是，当 plist 文件同时包含 UIRequiredDeviceCapability 的armv6 和armv7 时，应用程序商店拒绝上传我们的应用程序，因为要求armv7 会阻止应用程序在armv6 设备上运行。上传错误是：
“此捆绑包无效。Info.plist 中的关键 UIRequiredDeviceCababilties 可能不包含阻止此应用程序在以前版本支持的设备上运行的值。
因此，要使用 xcode 4.2 将 armv6 添加到我们的应用程序，我们必须做两件事：
1）在 info.plist 文件的 UIRequiredDeviceCapability 中仅设置 armv6，
2）将armv6和armv7设置为项目文件中的Architecture设置
We tried the solution listed above and added armv6 and armv7 to our info.plist file. But, the App store rejected the upload of our app when the plist file contained both armv6 and armv7 for UIRequiredDeviceCapabilities because requiring armv7 would prevent the app from running on armv6 devices. The upload error was:
"This bundle is invalid. The key UIRequiredDeviceCababilities in the Info.plist may not contain values that would prevent this application from running on devices that were supported by previous versions.
So, to add armv6 to our app using xcode 4.2, we had to do two things:
1) Set just armv6 in UIRequiredDeviceCapabilities in info.plist file,
2) Set armv6 and armv7 to the Architecture setting in the project file
原因是在 info plist 中添加/更新 REQUIREDDEVICECAPABILITIES。
当我尝试使用 XCODE 4.2 为使用 XCODE 3.2 提交的应用程序提交更新时，我遇到了这个问题，而没有在 info plist 中添加 REQUIREDDEVICECAPABILITIES。
我尝试更改架构，添加/删除 REQUIREDDEVICECAPABILITIES 等。
Atlast 将部署目标更改为 4.3 并且成功了。
更明确地说，低于 4.3 的部署目标需要 armv6/armv7 架构，而 XCODE 3.2 不需要，而 XCODE 4.3 要求用户提及。
The reason for this is adding/updating REQUIREDDEVICECAPABILITIES in info plist.
I faced this issue, when I tried submitting an update using XCODE 4.2 for an app submitted using XCODE 3.2 without adding the REQUIREDDEVICECAPABILITIES in info plist.
I tried changing the architecture, adding/deleting REQUIREDDEVICECAPABILITIES,etc.
Atlast changed the deployment target to 4.3 and it worked.
To be more clear, deployment target below 4.3 required armv6/armv7 architectures and XCODE 3.2 didn't require that where as XCODE 4.3 is asking the user to mention.
如果想要定位所有 iOS 设备，您只需删除 UIRequiredDeviceCapability 键即可。
请点击develope.apple 上的此链接
https://developer.apple.com/library/ios/qa/qa1623 /_index.html
If want to target all iOS Devices, you can simply delete the key UIRequiredDeviceCapabilities.
Follow this link at develope.apple
https://developer.apple.com/library/ios/qa/qa1623/_index.html