配置文件中缺少 aps-environment！
由于某种原因，我们的临时配置文件没有 aps-environment 权利！我们已确保在为该应用 ID 启用生产 apns 后生成配置文件。实际上，我们甚至为该应用程序 ID 创建了一个新的临时配置文件，并且在使用文本编辑器检查时甚至新的配置文件也没有该权利。这是怎么回事？
For some reason our adhoc provisioning profile just won't have the aps-environment entitlement! We've made sure that the profile is generated after we enabled the production apns for that app id. We've actually even created a new adhoc profile for that app id and even the new profile does not have that entitlement when checked using a text editor. What's going on?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
如果在重新生成该配置文件和/或创建新配置文件后，权利仍然丢失，这听起来像是 iOS 门户网站（服务器端）中的错误。
联系开发者计划请求他们的帮助或解释（不计入您的 DTS TSI）。使用该页面上的“计划优势”链接，因为它是“有关创建配置文件的问题......”
对于其他人，请注意，一旦应用程序 ID 具有新的权利设置（例如，当您为该应用程序 ID 启用推送通知时发生），您必须手动重新生成所有关联的配置文件，以将新权利添加到配置文件中。在 iOS 门户网站配置侧边栏、“开发”或“分发”选项卡（如合适的）。进入每个配置文件并通过单击“修改”或“编辑”重新生成它们。在编辑页面上，需要进行一些更改才能启用“提交”按钮，因此，对于分发配置文件，暂时将分发方法从“App Store”切换到“Ad Hoc”，然后再切换回来。然后单击“提交”以更新配置文件。
If the entitlement is still missing after regenerating that profile and/or making a new one, it sounds like a bug in the iOS Portal site (server side).
Contact Developer Programs to request their help or explanation (doesn't count toward your DTS TSI's). Use the "Program Benefits" link on that page, as it is "for questions about creating provisioning profiles..."
For others, note that once an App ID has new entitlement settings (such as happens when you enable Push Notification for that App ID) you must then manually regenerate all associated profiles to get the new entitlements onto the profile. Do that on the iOS Portal site Provisioning sidebar, "Development" or "Distribution" tab (as appropriate). Go into each profile and regenerate them by clicking "Modify" or "Edit". On the edit page, something needs to change to enable the "Submit" button, so, for a Distribution Provisioning Profile, temporarily switch the distribution method from "App Store" to "Ad Hoc" and then back. Then click Submit to update the profile.
确保您的本地授权文件不包含额外的密钥，例如 aps-environment。
Apple 门户上没有错误。我通过从本地权利文件中删除 aps-environment 密钥解决了这个问题。显然，Xcode 通过将您的权利文件与已安装的配置文件进行比较来进行初步检查。如果它在您的权利文件中发现任何未包含在您的配置文件中的内容，则它在编译错误中列出的操作是将缺少的权利添加到配置文件中。然而，它真正应该说的是确保您的权利文件与您的个人资料匹配。
因此，这似乎是 Xcode 配置文件验证过程中的一个错误。
Make sure your local entitlements file doesn't include extra keys, e.g. aps-environment.
There is not a bug on the Apple Portal. I fixed this issue on my end, by removing the aps-environment key from my local entitlements file. Apparently, Xcode does a preliminary check by comparing your entitlements files with your installed provisioning profiles. If it sees anything in your entitlements file that is not included in your profile, then the action it lists in the compile error is to add the missing entitlement to the profile. However, what it really should say instead is to ensure that your entitlements file matches your profile.
Therefore, this appears to be a bug in the Xcode's profile verification process.