xcode 无效的代码签名权利
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/6427735/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Invalid Code Signing Entitlements
提问by MGD
I ve followed all the procedure that app store support placed for help yet when ever i sumit the app after upload the status becomes "invalid binary" with following msg in the mail.
我已经遵循了应用程序商店支持人员提供的所有帮助程序，但是当我在上传后加载应用程序时，状态变为“无效的二进制文件”，并在邮件中显示以下 msg。
Invalid Code Signing Entitlements - Your application bundle's signature contains ubiquity code signing entitlements that are not supported.
Specifically, value "( 79FWT492R4.* )" for key "com.apple.developer.ubiquity-container-identifiers" in is not supported.
I will be thankful if someone help
如果有人帮助，我将不胜感激
Thanks MGD
感谢 MGD
回答by MGD
Well i really dont know why Apple has set so many complications for the app submission.Now coming towards the solution, What i did was, I used the same APP ID but i reconfigured it by uncheckingthe iCloudoption, then i renewed the provision and distribution profiles downloaded them, deleted the old profiles from the xcode organizer added the new ones (those i downloaded after renew), first my app started giving error during the that "key does not match .... " then i went to the built info of the target there i simply set "iphone distribution" in code signing, Thats it i build the app and uploaded via organizer, and it went with the status "Waiting for Review" :)
那么我真的不知道为什么苹果已经设定所以对于应用submission.Now对解决未来许多并发症，我所做的就是，我用同样的APP ID，但我通过重新配置它取消选中了iCloud的选项，然后我添了规定和分发配置文件下载了它们，从 xcode 组织者中删除了旧配置文件，添加了新配置文件（我在续订后下载的那些），首先我的应用程序在“密钥不匹配......”期间开始出现错误，然后我去了内置目标的信息我只是在代码签名中设置了“iphone 分发”，就是这样，我构建了应用程序并通过组织者上传，它的状态为“等待审核”:)
Cheers MGD
干杯MGD
回答by rregister
Just to clarify the answer, which I found confusing. I had ths problem just now (October 2011) and solved it quickly. I thought I had to revoke my own distribution certificate, but this clarifying note saved me (can't find the source right now but THANK YOU)
只是为了澄清答案，我觉得这很令人困惑。我刚刚（2011 年 10 月）遇到了这个问题并很快解决了。我以为我必须撤销我自己的分发证书，但是这个澄清说明救了我（现在找不到来源，但谢谢）
- Go to App IDs in the provisioning portal. Scroll to the bottom. Click configure on the row that represents your app's ID. Uncheck Enable for iCloud. Click Done.
- 转至供应门户中的 App ID。滚动到底部。单击代表您的应用程序 ID 的行上的配置。取消选中为 iCloud 启用。单击完成。
-- Now you can just regenerate your distro provisioning prof (no need to create a new one) and redownload it into Xcode, reubild and resubmit. i hope this helps people
-- 现在您可以重新生成您的发行版配置教授（无需创建新的）并将其重新下载到 Xcode，重新合并并重新提交。我希望这能帮助人们
回答by vieuxrenard
There is indeed no more option to disable iCloud in Provisioning Portal. But apparently Apple has noticed that the iCloud entitlements in distribution certificates may cause trouble during submission and has recently REMOVED these entitlements from the certificates again.
确实没有更多选项可以在 Provisioning Portal 中禁用 iCloud。但显然 Apple 已经注意到分发证书中的 iCloud 权利可能会在提交过程中造成麻烦，并且最近再次从证书中删除了这些权利。
So help is near: Just re-create your distribution certificate and you'll see that it doesn't contain the offending keys any more. Hope that helps.
所以帮助就在附近：只需重新创建您的分发证书，您就会看到它不再包含有问题的密钥。希望有帮助。
回答by mpatzer
Under the Code Signing section in my Build Settings, Xcode had selected iOS Developer for Release instead of iOS Distribution. Selecting the correct distribution profile for Release resolved this issue for me.
在我的 Build Settings 中的 Code Signing 部分下，Xcode 选择了 iOS Developer 来发布而不是 iOS Distribution。为 Release 选择正确的分发配置文件为我解决了这个问题。
回答by Gujamin
My solution was to remove the provisioning profile entries. Evidently in addition to the Code Signing entries, now there are also Provisioning Profile entries and mine was stuck on an old version or something. Clearing that fixed the problem.
我的解决方案是删除配置文件条目。显然除了 Code Signing 条目之外，现在还有 Provisioning Profile 条目，而我的被困在旧版本或其他东西上。清除解决了问题。
