应用程序协同设计验证失败 - 非法密钥 aps-环境

发布于 2024-12-18 21:30:09 字数 594 浏览 1 评论 0 原文

我有一个使用 XCode 4.2 构建的应用程序。它具有推送功能,自从修改应用程序 ID 以包含推送通知服务以来,我重新下载了证书和配置文件。我有一个用于测试的临时目标和一个我当前正在尝试构建的发布目标(以提交到应用程序商店)。我已经验证所有这些设置都是正确的(例如,它实际上使用的是 App Store 规定)。我的项目中有一个 Entitlements.plist 文件,其中包括键值对“aps-environment,生产”以及其他三个键(可以调试、应用程序标识符和钥匙串访问组)。

当我进行存档时,我收到一条警告:

warning: Application failed codesign verification.  The signature was invalid,
or it was not signed with an iPhone Distribution Certificate. (-19011)
Illegal entitlement key/value pair: aps-environment, production

如果我在构建设置中清空“代码签名权利”行,应用程序将构建并且我可以提交,但推送不起作用。 4.2 让 Push 发挥作用的神奇清单是什么?

I have an app that I'm building with XCode 4.2. It has push, and I've re-downloaded the certificate and provisioning profile since modifying the App ID to include Push Notification services. I have both an Ad Hoc target that I've used for testing, and a Release target that I'm currently trying to build with (to submit to the app store). I've verified that all of these settings are correct (eg that it's actually using the App Store provision). I have an Entitlements.plist file in the project, which includes the key-value pair "aps-environment, production" among three other keys (Can be debugged, application-identifier, and keychain-access-groups).

When I do an Archive, I get a warning:

warning: Application failed codesign verification.  The signature was invalid,
or it was not signed with an iPhone Distribution Certificate. (-19011)
Illegal entitlement key/value pair: aps-environment, production

If I blank out the "Code Signing Entitlements" line in the build settings, the app will build and I can submit, but Push doesn't work. What's the 4.2 magic checklist for getting Push to work?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

北城挽邺 2024-12-25 21:30:09

阅读

您需要检查“创建和安装配置文件”部分,那里是您问题的解决方案。看来苹果公司已经知道这个问题,但没有采取任何行动。

Read that

Your need to check "Creating and Installing the Provisioning Profile" part, there is a solution of your problem. Seems like Apple knows about this problem and does nothing.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文