在提交beta测试二进制：＆QUOT;缺少推送通知授权＆QUOT; [英] Submitting a binary for beta testing: "Missing Push Notification Entitlement"
问题描述
我目前使用会员中心网站，我有一定的应用程序ID开发和生产APNS证书，而这些应用程序ID出现与这两个环境启用推送通知。我还创建了几个预置描述文件：一个用于与关联的应用程序ID的发展，并在其启用的服务推送通知，另一个用于相同的应用程序ID特设分布，并与推送通知启用的服务
I'm currently using Xcode 6.4. In my Member Center site, I have both development and production APNS certificates for a certain App ID, and such App ID appears with Push Notifications enabled for both environments. I also created a couple of provisioning profiles: one for development with that App ID associated and Push Notifications in their enabled services, and another one for ad Hoc distribution for the same App ID and also with Push Notifications enabled services.
我可以看到X $ C $既调配型材C> preferences>帐户>我的帐户设置配置文件的详细名单，但推送通知的权利似乎并没有根据显示的图标权利有出现
I can see both provisioning profiles in Xcode > Preferences > Accounts > Details list of provisioning profiles in my account, but the Push Notifications entitlement doesn't seem to appear there according to the entitlements icons displayed.
此外，当我归档应用程序，并希望为临时部署导出，X code不允许我选择一个特定的供应配置文件签署的应用程序，即使我已经在目标的构建设置设置> code签署>供应配置文件。在该对话框的应用程序还列出了4权利存档的应用程序，但没有一个是APS。
Moreover, when I archive the app and want to export for ad Hoc deployment, Xcode doesn't allow me to choose a certain provisioning profile to sign the app, even I had set it in target's Build Settings > Code Signing > Provisioning Profile. The app in that dialog also lists 4 entitlements for the archived app, but none is "aps".
不管怎样，我通过使用X $ C $设置C并没有让我改变配置导出的应用程序（XC特设：*），并将其发送到iTunes连接。然后，我收到一封电子邮件，说：
Anyway, I exported the app by using the provisioning that Xcode set and doesn't allow me to change (XC Ad Hoc: *) and sent it to iTunes Connect. Then I received an email saying:
缺少推送通知的权利 - 您的应用似乎包括用于与苹果推送通知服务注册API，但应用程序签名的权利不包括在APS-环境的权利。如果您的应用程序使用Apple推送通知服务，请确保您的应用程序ID是在配置门户推送通知启用，并与包括APS-环境问题的发行配置文件签署您的应用程序后，重新提交权利。
Missing Push Notification Entitlement - Your app appears to include API used to register with the Apple Push Notification service, but the app signature's entitlements do not include the "aps-environment" entitlement. If your app uses the Apple Push Notification service, make sure your App ID is enabled for Push Notification in the Provisioning Portal, and resubmit after signing your app with a Distribution provisioning profile that includes the "aps-environment" entitlement.
可能是什么回事？在我的会员中心我有推送通知功能的应用程式ID，我有相应的证书和配置配置文件。我没有结果刷新了供应曲线的两倍。我能怎么会mising？我真的需要这个问题有所帮助。
What could be happening? In my Member Center I have App ID enabled for push notifications, and I have the corresponding certificates and provisioning profiles. I refreshed the provisioning profiles twice with no result. What could I be mising? I really need help with this issue.
在此先感谢
编辑：如果我打开一个文本编辑器的供应配置文件，它实际上包含行：
If I open the provisioning profile in a text editor, it actually contains the lines:
<key>aps-environment</key>
<string>production</string>
那为什么这个权利在X $ C $列C> preferences>账户开通的图标？
Then why is this entitlement listed in Xcode > Preferences > Accounts icons of the provisioning?
编辑2：我要补充一个Entitlements.plist文件到我的项目？我在哪里能找到有关该文档？
EDIT 2: Should I add an Entitlements.plist file to my project? Where could I find documentation regarding that?
推荐答案
我花了过去2周处理同样的问题。终于得到它的工作。这个问题可能是在 X $ C $ 6.4ç的错误。 X code，采用不同的供应配置文件签署应用程序（通配符XC：*'），这恰好不是有'APS-环境的权利，即使我是正确的选择我的资源调配配置文件中的生成设置作为你。因此，要解决此我不得不建立和分发通过的 深圳
I spent the last 2 weeks dealing with the same problem. And finally got it working. The problem is probably a bug in Xcode 6.4. Xcode was using a different Provisioning Profile to sign the App (the wildcard 'XC: *') which happens to not have the 'aps-environment' entitlement, even though I was selecting my provisioning profiles correctly in 'Build Settings' as you. So to workaround this I had to build and distribute via Shenzhen.
希望这有助于你。
这篇关于在提交beta测试二进制：＆QUOT;缺少推送通知授权＆QUOT;的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
