blocks|key|112036|text|实际上，这很简单。由于某种原因，它在Xcode8上被禁用了，但请转到Targets+->功能，并验证该视图上的推送通知都是正确的。对我来说，它有一个“修复我”，我必须点击，瞧。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|112037|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Very easy actually. For some reason it got disabled on Xcode 8 but go to Targets -> Capabilities and verify Push Notifications is all correct on that view. For me it had a "Fix Me" I had to click, and voila.

blocks|key|2866439|text|Xcode8中有一个变化，您的权利不再来自应用程序标识符，而是来自您的应用程序目标中选择的功能。因此，就像Unome+(the+OP)所说的那样，您必须验证推送通知是否已打开。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2866440|对我来说，这不是一个“修复我”按钮，但我有两个授权文件(一个用于开发，一个用于分发)。切换推送通知功能会将值为development的aps-environment密钥添加到开发授权文件，但不会将其添加到分发授权文件。将相同的密钥复制到分发中，可以在上传到iTunes连接时消除警告电子邮件。|offset|length|style|CODE|2866441|对于大多数项目，切换推送通知就足够了，或者如果推送通知已经打开，但关键不在授权中，请尝试关闭并再次打开它。|2866442|同样值得注意的是，权限在归档过程中会自动更新。即，为release版本生成的权利可以与为开发版本生成的权利不同。请参阅here|BOLD|2866443|2866444|在应用程序分发过程中，通过Xcode+Organizer+>+Archives选项卡，通过用于代码签名的供应配置文件将权限设置到应用程序上。重要的是要意识到，在此阶段重新应用授权可能会在您可能测试过的任何先前的开发版本之间产生意外的授权差异。本文档的主要目的是验证您的授权对于用于beta测试和应用商店提交的分发版本是正确的。|blockquote|2866445|2866446|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/library/archive/qa/qa1798/_index.html^0|0|1J|B|1V|F|0|0|Q|7|18|2|1N|4|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@$D|11|E|12|F|G]|$D|13|E|14|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|15|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|16|8|@$D|17|E|18|F|L]|$D|19|E|1A|F|L]]|9|@$D|1B|E|1C|1|1D]]|A|$]]|$1|M|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|1F|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y]]]]

There was a change in Xcode 8, where your entitlements no longer come from the App Identifiers, but from the capabilities selected in your app target. So, like Unome (the OP) said, you have to verify that Push Notifications is switched on.
For me, it wasn't a &quot;Fix Me&quot; button, but I had two entitlement files (one for development and one for distribution). Toggling the Push Notifications capability would add the <code>aps-environment</code> key - with the value <code>development</code> - to the development entitlements file, but it wouldn't add it to the distribution entitlements file. Copying the same key over to distribution worked to get rid of the warning email when uploading to iTunes Connect.
For most projects, it should be sufficient to toggle on Push Notifications, or if it's already on but the key isn't in the entitlements, try toggling it off and on again.
It's also worth noting that entitlements automatically get updated during archive. ie the entitlements generated for release builds can be different from entitlements generated for development builds. See <a href="https://developer.apple.com/library/archive/qa/qa1798/_index.html" rel="nofollow noreferrer">here</a>
<blockquote>
During the app distribution process through the Xcode Organizer &gt;
Archives tab, entitlements are set onto the app by way of the
provisioning profile used for code signing. It is important to be
aware that the re-application of entitlements at this phase creates
the opportunity for unintended entitlement differences between any
prior development builds you may have tested. The primary purpose of
this document is to verify that your entitlements are correct for your
distribution builds for beta testing and App Store submission.
</blockquote>

blocks|key|112538|text|我也有同样的问题，我确信在Xcode8中推送通知是默认关闭的。我没注意到。要当心。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|112539|​|112540|📷|atomic|offset|length|112541|112542|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/7876f345169d9630f51665b4d2312b8d.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

I also have the same problem, and I'm sure Push notification is off by default in Xcode8. I didn't notice it. Be careful about it.

<a href="https://i.stack.imgur.com/IsvC4.png" rel="noreferrer"><img src="https://i.stack.imgur.com/IsvC4.png" alt="capability"></a>

blocks|key|2655466|text|在与Xcode8斗争了一天之后，我们弄不明白为什么aps-environment开发没有添加到我们的调试版本中。在用于调试测试的内置应用程序的授权部分中找不到它...即使我们已经启用了新的功能和授权文件仍然存在。问题是需要在调试授权的Xcode构建设置中为任何SDK设置授权文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2655467|​|2655468|📷|atomic|2655469|2655470|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/a527a1b6411f691da37b61f2066fd1d4.png|imageAlt^0|P|F|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|K|3|G|5|6|7|12|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S|T|-4]]]]

After a day of struggle with Xcode 8 we could not figure out why the <code>aps-environment</code> development was NOT added to our debug builds. It was missing from the entitlements section in the built app for debug testing... even though we had ENABLED the new Capability and the entitlements file existed. The issue is that the entitlements file needs to be set for ANY SDK in the Xcode Build Settings for Debug Entitlements.

<a href="https://i.stack.imgur.com/V0DZ9.png" rel="noreferrer"><img src="https://i.stack.imgur.com/V0DZ9.png" alt="screenshot"></a>

blocks|key|2655489|text|从Xcode+release+notes|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2655490|2655491|+Xcode8不会在构建时自动复制配置文件中的at+environment权限。此行为是故意的。要使用此授权，请在项目编辑器的功能窗格中启用推送通知，或手动将授权添加到您的授权文件中。(28076333)|blockquote|2655492|2655493|2655494|这是一个巨大的变化，因为它总是很奇怪的是，aps-environment授权不需要plist，但许多其他人需要。|2655495|对于那些不想盲目地按下“修复我”并且当前没有授权文件的人来说，它只是一个plist文件，在您的项目的构建设置中的“代码签名授权”下引用了它。|2655496|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/library/content/releasenotes/DeveloperTools/RN-Xcode/Chapters/Introduction.html#//apple_ref/doc/uid/TP40001051-CH1-SW78^0|7|D|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|D|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|10|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|11|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|12|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|13|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|14|8|@]|9|@]|C|$]]|$1|N|3|-4|5|6|7|15|8|@]|9|@]|C|$]]]|O|$P|$5|Q|R|S|C|$T|U]]]]

From the Xcode <a href="https://developer.apple.com/library/content/releasenotes/DeveloperTools/RN-Xcode/Chapters/Introduction.html#//apple_ref/doc/uid/TP40001051-CH1-SW78" rel="noreferrer">release notes</a>:

<blockquote>
 Xcode 8 does not automatically copy the aps-environment entitlement from provisioning profiles at build time. This behavior is intentional. To use this entitlement, either enable Push Notifications in the project editor’s Capabilities pane, or manually add the entitlement to your entitlements file. (28076333)
</blockquote>

This is a great change as it was always quite odd that the aps-environment entitlement didn't require the plist, but many others did.

For those of you that do not want to just blindly press "Fix Me" and do not currently have an entitlements file, it is just a plist file which is referenced in your project's Build Settings under "Code Signing Entitlements"

blocks|key|110128|text|我用XCode+7.3.1从苹果收到了同样的邮件。我解决这个问题的方法是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|110129|Capabilities+>+Set+PUSH+Identity下的|110130|，如@Bruce+Tsai答案所示。Build-Settings+>+Code+Signing+>+Code+Signing+Identity下的|ordered-list-item|110131|设置调试的开发者证书和发布的分发证书，如下图所示：|110132|110133|​|110134|📷|atomic|offset|length|110135|110136|110137|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/cf7f8f51d7c7dae1b1518d2b0976191d.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/f2f91bfb48ee3391046728b23896a4e1.jpeg^0|0|0|0|0|0|0|0|1|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|15|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|16|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|18|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|19|8|@]|9|@$O|1A|P|1B|1|1C]]|A|$]]|$1|Q|3|M|5|N|7|1D|8|@]|9|@$O|1E|P|1F|1|1G]]|A|$]]|$1|R|3|K|5|6|7|1H|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z|10|-4]]|11|$5|V|W|X|A|$Y|12|10|-4]]]]

I got the same email from Apple using XCode 7.3.1. What I did to solve the problem was:

<ol>
<li>Under Capabilities > Set PUSH notification ON as stated in @Bruce Tsai answer.</li>
<li>Under Build-Settings > Code Signing > Code Signing Identity set the developer cert for debug and the distribution cert for release, as is shown in the image:</li>
</ol>

<a href="https://i.stack.imgur.com/lNWPT.png" rel="noreferrer"><img src="https://i.stack.imgur.com/lNWPT.png" alt="enter image description here"></a>
<a href="https://i.stack.imgur.com/ALrdw.jpg" rel="noreferrer"><img src="https://i.stack.imgur.com/ALrdw.jpg" alt="enter image description here"></a>

blocks|key|112582|text|​|type|unstyled|depth|inlineStyleRanges|entityRanges|data|112583|📷|atomic|offset|length|112584|112585|自动管理签名对我来说是关闭的，我检查了，对我来说工作得很好。|112586|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/bf721a42d1970519ca8dcd10d4fd2b63.png|imageAlt^0|0|0|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@$E|U|F|V|1|W]]|A|$]]|$1|G|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

<a href="https://i.stack.imgur.com/68yK4.png" rel="noreferrer"><img src="https://i.stack.imgur.com/68yK4.png" alt="Automatically manage signing was off for me "></a>

Automatically manage signing was off for me, i checked and working fine for me.

blocks|key|2655640|text|使用Xcode+9推送通知已启用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2655641|我尝试禁用/重新启用推送通知功能。(不起作用)|offset|length|style|BOLD|2655642|我尝试禁用/重新启用自动管理签名。(不起作用)|2655643|结果，我不得不删除并重新添加我的配置配置文件。(see+here+how+to+do+it)您可能需要禁用/重新启用自动管理wards后的签名。|2655644|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/44061528/3325104^0|0|A|4|0|A|6|0|1M|D|O|L|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@$D|V|E|W|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@$D|11|E|12|F|G]]|9|@$D|13|E|14|1|15]]|A|$]]|$1|L|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

Using Xcode 9 push Notifications was enabled.

I tried disabling/re-enabling Push Notification capabilities. (didn't work)

I tried disabling/re-enabling Automatically manage signing. (didn't work)

Turns out I had to delete and re-add my provisioning profiles. (<a href="https://stackoverflow.com/a/44061528/3325104">see here how to do it</a>)
You might have to disable/re-enable Automatically manage signing after wards.

blocks|key|112176|text|如果你使用的是Firebase框架，而不是推送通知，有两种解决方案:+1.只需忍受每次上传二进制文件时发送给整个团队的“问题”消息。该应用程序仍将被接受为提交，只要你实际上没有使用通知，你可以忽略警告。或者2.这样做：https://stackoverflow.com/a/46802075/7529450。这将删除恼人的电子邮件通知，也会被接受为提交。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|112177|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/46802075/7529450^0|31|18|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

If you're using Firebase frameworks and aren't using push notifications there are two solutions 1. just put up with the 'issue' message that gets sent to your whole team every time uploading a binary. The app will still be accepted as a submission as long as you're not actually using notifications you can ignore the warning. or 2. do this: <a href="https://stackoverflow.com/a/46802075/7529450">https://stackoverflow.com/a/46802075/7529450</a> . This will remove the annoying email notification and also get accepted as a submission.

blocks|key|110236|text|对我来说，问题是因为有两个授权文件：Entitlements-Debug.plist和Entitlements-Release.plist。其中只有一个(Debug)需要在其中进行设置。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|110237|将构建设置>签名>代码签名授权的多个值更改为单个MyAppName/MyAppName.entitlements，然后重新启用功能>推送通知切换器为我做了这件事。|BOLD|110238|希望能有所帮助。|110239|entityMap^0|I|O|17|Q|0|1|E|1R|7|O|W|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@$9|S|A|T|B|H]|$9|U|A|V|B|H]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|I|3|J|5|6|7|Y|8|@]|D|@]|E|$]]|$1|K|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|L|$]]

For me the problem was because there were two entitlements files: <code>Entitlements-Debug.plist</code> and <code>Entitlements-Release.plist</code>. And only one of them (Debug) has needed settings in it.

Changing multiple value of Build Settings > Signing > Code Signing Entitlements to a single <code>MyAppName/MyAppName.entitlements</code> and then reenabling Capabilities > Push Notifications switcher did the trick for me.

Hope it helps.

blocks|key|112191|text|另一个有效的方法是:将AppName/Entitlements-Debug.plist的源代码复制粘贴到AppName/Entitlements-Release.plist中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|112192|entityMap^0|B|W|1G|Y|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

One more option that worked: copy-pasting the source of <code>AppName/Entitlements-Debug.plist</code> into <code>AppName/Entitlements-Release.plist</code>.

I've got an app that we've submitted dozends of versions to in the last 6 months and we do use APNS. I got the following email from Apple after upgrading to Xcode 8

<blockquote>
 Dear developer,
 
 We have discovered one or more issues with your recent delivery for
 APP_NAME. Your delivery was
 successful, but you may wish to correct the following issues in your
 next delivery:
 
 Missing Push Notification Entitlement - Your app includes an API for
 Apple's Push Notification service, but the aps-environment entitlement
 is missing from the app's signature. To resolve this, make sure your
 App ID is enabled for push notification in the Provisioning Portal.
 Then, sign your app with a distribution provisioning profile that
 includes the aps-environment entitlement. This will create the correct
 signature, and you can resubmit your app. See "Provisioning and
 Development" in the Local and Push Notification Programming Guide for
 more information. If your app does not use the Apple Push Notification
 service, no action is required. You may remove the API from future
 submissions to stop this warning. If you use a third-party framework,
 you may need to contact the developer for information on removing the
 API.
 
 After you’ve corrected the issues, you can use Xcode or Application
 Loader to upload a new binary to iTunes Connect.
 
 Regards,
 
 The App Store team
</blockquote>

What is weird is I went to developer.apple.com -> Certificates, Identifiers &amp; Profiles and my AppId does have Push Notifications enabled still. I'm not doing anything different then I've ever done on it so am curious if the Xcode 8 update broke something. Any ideas? 

BTW: The link they put for the Push Notification Programming Guide was broken in the email, so that's not a good sign.

Xcode 8 "the aps-environment entitlement is missing from the app's signature" on submit

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

我有一个应用程序，在过去的6个月里，我们已经提交了几十个版本，我们确实使用了APNS。在升级到Xcode8之后，我收到了来自Apple的以下电子邮件亲爱的开发人员：我们发现您最近交付的APP_NAME存在一个或多个问题。您的交付已成功，但您可能希望在下次交付时更正以下问题：缺少推送通知权限-您的应用程序包含苹果推送通知...

问提交时Xcode 8“应用程序的签名中缺少aps-环境授权”
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问提交时Xcode 8“应用程序的签名中缺少aps-环境授权”EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问提交时Xcode 8“应用程序的签名中缺少aps-环境授权”
EN