blocks|key|3039976|text|是的，这就是App+Store被拒绝的原因。如果您的临时配置文件具有aps-environment密钥，则意味着您的应用程序已在Apple+provisioning+Portal中正确配置。您只需删除本地计算机上的App+Store分发配置文件，然后从配给门户重新下载并安装分发配置文件。这个新的密钥应该包含aps-environment密钥。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3039977|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|$]]

Yes, that's the cause of the App Store rejection. If your ad-hoc provisioning profile has the aps-environment key, it means your app is configured correctly in the Apple Provisioning Portal. All you need to do is delete the App Store distribution profile on your local machine, then re-download and install the distribution profile from the Provisioning Portal. This new one should contain the aps-environment key.

blocks|key|3040142|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3040143|第一个应用程序ID|blockquote|3040144|3040145|3040146|确保您的ID推送通知在生产端开启|3040147|如图所示|3040148|​|3040149|📷|atomic|offset|length|3040150|3040151|3040152|第二个证书|3040153|3040154|3040155|在生产部分使用您的id创建两个证书(启用推送通知)|3040156|应用商店和即席证书|style|BOLD|3040157|苹果推送通知服务SSL+(沙盒)证书|3040158|3040159|3040160|3040161|3040162|第三次调配配置文件|3040163|3040164|3040165|从分发部分使用您的id创建应用商店配置文件|3040166|3040167|终于实现了|3040168|3040169|3040170|上传bin时，您必须检查所使用的配置配置文件，并且具有多个权利文件|3040171|3040172|3040173|3040174|这一切都导致了这个问题，希望这能对你有所帮助|3040175|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/3360e059c013ec80553f4ad97bc8f415.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/b4a718ebb4679eea39dbe492f5c574bc.png|2|https://ask.qcloudimg.com/http-save/yehe-900000/4218ac148539dcd354a9a1fa0d8a1082.png^0|0|0|0|0|0|0|0|0|1|0|0|0|0|0|0|0|0|0|7|0|0|G|0|0|0|1|1|0|0|0|0|0|0|D|4|0|0|0|0|0|0|0|0|1|2|0|0|0^^$0|@$1|2|3|-4|4|5|6|23|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|24|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|25|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|26|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|27|7|@]|8|@]|9|$]]|$1|H|3|I|4|5|6|28|7|@]|8|@]|9|$]]|$1|J|3|K|4|5|6|29|7|@]|8|@]|9|$]]|$1|L|3|M|4|N|6|2A|7|@]|8|@$O|2B|P|2C|1|2D]]|9|$]]|$1|Q|3|K|4|5|6|2E|7|@]|8|@]|9|$]]|$1|R|3|-4|4|5|6|2F|7|@]|8|@]|9|$]]|$1|S|3|T|4|C|6|2G|7|@]|8|@]|9|$]]|$1|U|3|-4|4|5|6|2H|7|@]|8|@]|9|$]]|$1|V|3|-4|4|5|6|2I|7|@]|8|@]|9|$]]|$1|W|3|X|4|5|6|2J|7|@]|8|@]|9|$]]|$1|Y|3|Z|4|5|6|2K|7|@$O|2L|P|2M|10|11]]|8|@]|9|$]]|$1|12|3|13|4|5|6|2N|7|@$O|2O|P|2P|10|11]]|8|@]|9|$]]|$1|14|3|K|4|5|6|2Q|7|@]|8|@]|9|$]]|$1|15|3|M|4|N|6|2R|7|@]|8|@$O|2S|P|2T|1|2U]]|9|$]]|$1|16|3|K|4|5|6|2V|7|@]|8|@]|9|$]]|$1|17|3|-4|4|5|6|2W|7|@]|8|@]|9|$]]|$1|18|3|19|4|C|6|2X|7|@]|8|@]|9|$]]|$1|1A|3|-4|4|5|6|2Y|7|@]|8|@]|9|$]]|$1|1B|3|-4|4|5|6|2Z|7|@]|8|@]|9|$]]|$1|1C|3|1D|4|5|6|30|7|@$O|31|P|32|10|11]]|8|@]|9|$]]|$1|1E|3|-4|4|5|6|33|7|@]|8|@]|9|$]]|$1|1F|3|1G|4|C|6|34|7|@]|8|@]|9|$]]|$1|1H|3|-4|4|5|6|35|7|@]|8|@]|9|$]]|$1|1I|3|-4|4|5|6|36|7|@]|8|@]|9|$]]|$1|1J|3|1K|4|5|6|37|7|@]|8|@]|9|$]]|$1|1L|3|K|4|5|6|38|7|@]|8|@]|9|$]]|$1|1M|3|M|4|N|6|39|7|@]|8|@$O|3A|P|3B|1|3C]]|9|$]]|$1|1N|3|K|4|5|6|3D|7|@]|8|@]|9|$]]|$1|1O|3|1P|4|5|6|3E|7|@]|8|@]|9|$]]|$1|1Q|3|-4|4|5|6|3F|7|@]|8|@]|9|$]]]|1R|$1S|$4|1T|1U|1V|9|$1W|1X|1Y|-4]]|1Z|$4|1T|1U|1V|9|$1W|20|1Y|-4]]|21|$4|1T|1U|1V|9|$1W|22|1Y|-4]]]]

<blockquote>
 First App ID
</blockquote>

make sure your ID push notification enable in production side 

as appear in picture 

<img src="https://i.stack.imgur.com/Kb8rx.png" alt="enter image description here">

<blockquote>
 Second Certificate 
</blockquote>

from production section create two certificate with your id (push notification enabled)

App Store and Ad Hoc certificate

Apple Push Notification service SSL (Sandbox) certificate 

<img src="https://i.stack.imgur.com/7qmdP.png" alt="enter image description here">

<blockquote>
 Third Provisioning Profiles 
</blockquote>

From Distribution section create App Store profile with your id 

<blockquote>
 Finally
</blockquote>

while you upload your bin , you must check what provisioning profile used
and have many entitlements 

<img src="https://i.stack.imgur.com/wcraF.png" alt="enter image description here">

this all cases cause this problem
hope this be helpful with you

blocks|key|198413|text|在XCode+8中，除了启用供应和证书上的所有内容外，还需要在目标上的Capabilities选项卡中启用推送：Xcode+8+"the+aps-environment+entitlement+is+missing+from+the+app's+signature"+on+submit|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|198414|我关于这个here的博客文章。|198415|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/39554177/xcode-8-the-aps-environment-entitlement-is-missing-from-the-apps-signature-on|1|http://www.devsbedevin.com/handling-missing-push-notification-entitlement-appstore-error/^0|1K|2F|0|0|5|4|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

In XCode 8 you need to enable push in the Capabilities tab on your target, on top of enabling everything on the provisions and certificates:
<a href="https://stackoverflow.com/questions/39554177/xcode-8-the-aps-environment-entitlement-is-missing-from-the-apps-signature-on">Xcode 8 &quot;the aps-environment entitlement is missing from the app&#39;s signature&quot; on submit</a>

My blog post about this <a href="http://www.devsbedevin.com/handling-missing-push-notification-entitlement-appstore-error/" rel="noreferrer">here</a>.

blocks|key|2827178|text|我收到这条消息是出于不同的原因--我通过Xcode提交了一个应用程序，而没有先创建一个专门针对该应用程序的app+Store+Distribution配置文件。我相信Xcode会自动使用通配符App+Store配置文件，如果你已经安装了一个的话。但使用推送通知的应用程序需要自己的配置文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2827179|修复方法是为应用程序创建一个新的app+Store分发配置文件。然后下载它，将其拖到Xcode上，并修改您的项目Build+Settings+>+Code+Signing+>+Release以使用新的概要文件。|2827180|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I got this message for a different reason -- I submitted an app via Xcode without first creating an App Store Distribution Profile specifically for the app. I believe Xcode automatically uses a wildcard App Store profile if you have one installed. But an app uses Push Notifications requires its own profile.

The fix is to create a new App Store Distribution profile for the app. Then you download it, drag it onto Xcode, and modify your project Build Settings > Code Signing > Release to use the new profile.

blocks|key|199179|text|根据@Vaiden给出的答案，在Xcode8中，您可以通过选择目标并单击“修复问题”来解决此问题。当然，你仍然需要在Apple+Developer+portal中设置推送通知(你可以通过使用新的“自动管理签名”选项来简化这个过程，这样就省去了下载配置文件的麻烦)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|199180|​|199181|📷|atomic|199182|199183|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/account/ios/profile/|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/8763bc11bee230be8e95e354913f5a2a.png|imageAlt^0|1M|M|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|I|3|E|5|6|7|16|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|17|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]|R|$5|S|N|T|C|$U|V|W|-4]]]]

Following on from the answer given by @Vaiden, in Xcode 8 you can resolve this issue by selecting the target and clicking the "Fix issue". Of course, you'll still need to set up push notifications in the <a href="https://developer.apple.com/account/ios/profile/" rel="noreferrer">Apple Developer portal</a> (you can simplify the process a little by using the new "Automatically manage signing" option, which saves you the hassle of downloading the provisioning profiles).

<a href="https://i.stack.imgur.com/VN7B7.png" rel="noreferrer"><img src="https://i.stack.imgur.com/VN7B7.png" alt="Fix me option"></a>

blocks|key|198358|text|对于那些在他们的应用中使用推送通知的人来说，他们遇到了这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|198359|我们的推送证书最近即将过期，所以我们以Apple概述的标准方式创建了新的dev+/+prod推送证书(我不会在这里详细介绍，在更新你的推送证书以供下一年使用时，网络上有很多关于它的信息)。|198360|然而，在这样做之后，这个问题就出现了。无论我们做了什么，我们都会在提交应用程序后收到来自Apple的这封电子邮件。当我们在Apple会员中心检查我们的分销供应配置文件的设置时，一切看起来都很好(为我们的生产/开发应用程序ID启用了推送，并且我们的分销供应配置文件仍然连接到此应用程序ID，按照标准做法，我们实际上只是在另一年创建了新的推送证书)。|198361|最后，这是最终为我解决这个问题的方法：|198362|198363|在Xcode中创建一个指向您的应用程序ID的新分发配置文件(保留您的当前配置文件)|ordered-list-item|198364|，通过设置>帐户>选择您的帐户>详细信息>单击刷新图标|198365|为您的应用程序手动创建授权plist文件：|198366|文件菜单>新建文件...|unordered-list-item|198367|<代码>H19选择iOS+>资源>属性列表<代码>H210H111将新文件命名为"foo.entitlements“(通常，“extension)|198368|”是目标名称)|198369|单击“授权文件”旁边的(%2B)以添加顶级项目(由于文件foo，属性列表编辑器将使用正确的架构|198370|198371|​|198372|198373|确保在目标的构建设置中使用此授权文件(目标>构建设置>搜索“授权”，在CODE_SIGN_ENTITLEMENTS中设置您刚才创建的授权文件的路径)|198374|确保目标中的配置配置文件/代码签名标识被正确设置为您适当的分发配置配置文件/签名标识(这一点应该很明显)|198375|我不能100%25确定这是否会影响它(它不应该影响它，因为目标设置覆盖了项目设置，但我还是这样做了)，确保您的项目的配置文件/签名身份与您创建的授权文件中的目标访问组相匹配，在空文件中右击并选择"Show+Raw+Keys/Values"|198376|Add+a+new+entry+to+the+entitlements+file“，并将其值设置为keychain-|198377|-|198378|注意，如果您以前使用的是keychain-access-|198379|授权，则需要在此处添加该密钥，因为出于某种原因，当我手动执行此操作时，该密钥已被清除。确保该值与以前版本中使用的值相同(您可以通过在管理器中查找以前的版本，尝试提交到应用程序商店，选择您的团队，然后在提交应用程序之前点击"(X)授权“字符串旁边的箭头，以展开授权并查看entitlement.|198380|Archive您的应用程序的keychain-access-group的值，然后尝试将其提交到最终的”提交“按钮。您应该看到此应用程序现在是使用您在成员中心创建的新配置文件构建的。现在取消此操作。|198381|返回苹果会员中心并删除你在步骤1中创建的新配置文件。|198382|返回Xcode，通过重复步骤2再次刷新你的配置文件列表。|198383|现在再次存档你的应用程序，你应该会看到该应用程序是使用你想要使用的旧分发配置文件构建的，并且正确地具有aps+environment权限。提交即完成。|198384|198385|我知道这不是很详细，因为它应该有屏幕截图，我会尝试更新它的屏幕截图，当我可以的时候，但我现在时间紧迫，想要得到我在那里所做的事情的摘要。我列出的一些或大部分步骤也很可能是不必要的，我之所以把它们放在这里，是因为我做了它们，它们可能导致了最终的解决方案。|198386|entityMap^0|0|0|0|0|0|0|0|1|1|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1W|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|1X|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|1Y|8|@]|9|@]|A|$]]|$1|L|3|M|5|K|7|1Z|8|@]|9|@]|A|$]]|$1|N|3|O|5|K|7|20|8|@]|9|@]|A|$]]|$1|P|3|Q|5|R|7|21|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|22|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|23|8|@]|9|@]|A|$]]|$1|W|3|X|5|R|7|24|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|25|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|26|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|27|8|@]|9|@]|A|$]]|$1|12|3|13|5|K|7|28|8|@]|9|@]|A|$]]|$1|14|3|15|5|K|7|29|8|@]|9|@]|A|$]]|$1|16|3|17|5|K|7|2A|8|@]|9|@]|A|$]]|$1|18|3|19|5|K|7|2B|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|2C|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|K|7|2D|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|K|7|2E|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|K|7|2F|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|K|7|2G|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|K|7|2H|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|K|7|2I|8|@]|9|@]|A|$]]|$1|1O|3|-4|5|6|7|2J|8|@]|9|@]|A|$]]|$1|1P|3|1Q|5|6|7|2K|8|@]|9|@]|A|$]]|$1|1R|3|-4|5|6|7|2L|8|@]|9|@]|A|$]]]|1S|$]]

For those running into this issue who actually are using Push Notifications in their apps:

Our push certs were recently about to expire, so we created new dev / prod push certs in the standard way outlined by Apple (I won't go into detail around this here, there is plenty of info on it all over the web when updating your push certs for another year of use).

After doing so however, the issue in this question popped up. No matter what we did, we received this email from Apple after submitting our app. When we checked the settings of our Distribution Provisioning Profile in the Apple Member Center, everything looked fine (Push was enabled for our App ID for both prod / dev, and our distribution provisioning profile was still connected to this App ID, we literally just created new push certs for another year as is the standard practice).

Finally, this is what ended up solving it for me:

<ol>
<li>Create a new Distribution Provisioning Profile pointing to your App ID (leave your current one in tact)</li>
<li>In Xcode, refresh your provisioning profiles via Settings > Accounts > Select your account > Details > Click the refresh icon</li>
<li>Manually create an entitlements plist file for your app:

<ul>
<li>File menu > New File...</li>
<li>Select iOS > Resource > Property List</li>
<li>Name the new file "foo.entitlements" (typically, "foo" is the target name)</li>
<li>Click the (+) next to "Entitlements File" to add a top-level item (the property list editor will use the correct schema due to the file extension)</li>
</ul></li>
<li>Ensure this entitlements file is being used in your target's Build Settings (Target > Build Settings > Search for "Entitlements", in the CODE_SIGN_ENTITLEMENTS set the path to your Entitlements file you just made)</li>
<li>Make sure the provisioning profile / code signing identity in your Target is set correctly to your appropriate distribution provisioning profile / signing identity (this should be obvious)</li>
<li>I'm not 100% sure if this affected it (it shouldn't since Target settings override project settings, but I did this anyways), make sure your Project's provisioning profile / signing identity match your Target's</li>
<li>In the entitlements file you made, right click in the empty file and select "Show Raw Keys/Values"</li>
<li>Add a new entry to the entitlements file called "aps-environment" and set it's value to "production"</li>
<li>One key note, if you were previously using the keychain-access-groups entitlement, you'll want to add that key here as well because for some reason it got cleared for me when doing this manually. Make sure the value is the same as the value used in previous builds (you can find the value by finding a previous build in Organizer, attempting to submit to the app store, select your team, then before submitting the app tap the arrow beside the "(X) Entitlements" string to expand the entitlements and see the value of the keychain-access-group entitlement.</li>
<li>Archive your app and attempt to submit it to the point of getting to the final "Submit" button. You should see this app was now built with the new provisioning profile you created in member center. Cancel out of this now.</li>
<li>Go back to the Apple member center and delete the new provisioning profile you created in step 1.</li>
<li>Back in Xcode, refresh your provisioning profiles list once again by repeating step 2.</li>
<li>Now archive your app again, and you should see that the app was built with the old Distribution provisioning profile you wanted to use, and correctly has the aps-environment entitlement. Submit and you're done.</li>
</ol>

I know this isn't as detailed as it should be as it should have screenshots, I will try to update it with screenshots when I can but for the time being I'm in a time crunch right now and wanted to get the jist of what I did out there. There is also a very likely chance that some or most of the steps I've outlined aren't necessary, I'm putting them here because I did them and they may have led to the final solution.

blocks|key|2827161|text|检查您的应用程序Id是否在iOS配置门户中的developer.apple.com上启用推送如果未启用，请为您的应用程序Id配置推送SSL证书下载该证书并重新安装在您的钥匙链中，然后下载分发配置文件安装在您的Xcode库中|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2827162|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|$]]

check Your App Id is Push Enabled or not on developer.apple.com in iOS Provisioning Portal
If Not then Enabled it,configure Your Push SSL Certificate for your App Id Download it,
and Reinstall in Your Keychain Once again then Download Your Distrubution Profile install in your Xcode Liabrary

blocks|key|3040247|text|我也面临着这个问题，即使我根本没有使用推送通知，在我的app.Making+中，新的资源调配配置文件也不适用于me.What我做的是：-|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3040248|1.仅为Ad+hoc和应用程序商店创建新证书。|3040249|Xcode2.然后使用该证书创建分发配置文件，并将配置文件与集成。|3040250|然后，在没有任何警告的情况下，新提交的带有此配置文件的构建获得批准。|3040251|entityMap^0|12|C|0|0|N|0|U|3|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|W|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|M|$]]

I was also facing this issue even I was not using push notifications at all in my app.Making new provisioning profile also did not work for me.What I did was:-

1.Create fresh new certificate for Ad hoc &amp; App Store only.

2.Then make distribution profile with this certificate and integrate profile with Xcode.

Then newly submitted build with this profile approved without any warning.

blocks|key|199162|text|这就是我修复它的方法。(我已经尝试打开/关闭功能，重新创建配置配置文件等)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|199163|在构建设置选项卡中，在代码签名授权中，我的.entitlements文件没有链接到所有部分。一旦我将它添加到Any+SDK部分，这个错误就被解决了。|offset|length|style|BOLD|199164|​|199165|📷|atomic|199166|199167|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/d2a7b26ebd5b3851e9de48c3de329cae.png|imageAlt^0|0|1|4|B|6|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@$D|Y|E|Z|F|G]|$D|10|E|11|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|13|8|@]|9|@$D|14|E|15|1|16]]|A|$]]|$1|M|3|I|5|6|7|17|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U|V|-4]]]]

This was what fixed it for me. (I had already tried toggling the capabilities on/off, recreating the provisioning profile, etc).

In the Build Settings tab, in Code Signing Entitlements, my .entitlements file wasn't link for all sections. Once I added it to the Any SDK section, the error was resolved.

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

blocks|key|201012|text|我也遇到了同样的问题，我的解决方案是从目标->功能添加推送通知权限。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|201013|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|$]]

I had the same problem and my solution was to add the push notification entitlement from Target -> Capabilities.

blocks|key|3040586|text|为了解决世博会“弹出”应用程序的这个问题，我转到了“功能”选项卡，启用了推送，然后再次禁用了它。这将从.entitlements文件中删除APNS的“权利”设置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3040587|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|$]]

To solve this for an expo 'ejected' app, I went to the capabilities tab, enabled push, then disabled it again. This removed the APNS 'entitlements' setting from the .entitlements file.

blocks|key|3040651|text|我做了一个应用程序，没有使用任何推送通知功能，但我还是收到了一封电子邮件。在苹果开发者门户检查了证书、ids和我用来在苹果商店连接中创建应用程序的捆绑标识符的配置文件后，我意识到推送通知已经打开了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3040652|你要做的是：|3040653|转到apple+developer登录站点，在这里您可以管理您的证书a.s.o+2.选择右侧的“证书，id和配置文件”选项卡3.现在选择“标识符”4.从右边的列表中选择捆绑包id+5.现在向下滚动，直到您看到推送通知6.关闭它7.存档您的构建并重新上传到Apple+Store+Connect|3040654|希望它能帮上忙！|3040655|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

FIX IDEA
Hey guys so i have made an app and did not used any push notification functions but i still got an email. After checking the certificates, ids and profiles of the bundle identifier i used to create my app in apple store connect in the apple developer portal i realized that push notificiations were turned on.

What you have to do is:

go to apple developer login site where you can manage your certificates a.s.o
2. select "Certificates, IDs and Profiles" Tab on the right side
3. now select "Identifiers"
4. and the bundle id from the list to the right
5. now scroll down till you see push notification
6. turn it off
7. archive your build and reupload it to Apple Store Connect

Hope it helps!

blocks|key|2827202|text|在我的例子中，甚至我创建了一个环境并在xcode中手动设置它，当我选择“在查找器中显示”并找到embedded.mobileprovision并检查以确保aps-+myapp.profile在文件中时，错误仍然存在。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2827203|然后我去开发者中心，发现XC:+myapp.profile的状态是无效的。我更新了它并安装了XC:+myapp.profile，它工作得很好。|2827204|我认为xcode正在尝试管理配置文件，当您提交二进制文件存储时，您需要检查配置配置文件，并确保它是正确的。根据其他答案，它可能是由各种原因造成的，所以它可能真的很烦人。|2827205|更新：|2827206|一旦您使用下载的配置文件进行了签名，并在您尝试提交到App+Store时确认aps-environment在那里，您就应该能够将配置文件和代码签名实体更改为automatic和iOS+Developer。希望它能在Xcode7中得到改进。|offset|length|style|CODE|2827207|entityMap^0|0|0|0|0|Q|9|12|F|2G|D|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@$J|U|K|V|L|M]|$J|W|K|X|L|M]|$J|Y|K|Z|L|M]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|O|$]]

In my case, even I created a myapp.profile and set it in xcode manually, and when I chose "show in finder" and located the embedded.mobileprovision and checked to make sure aps-environment is there in the file, the error was still there.

I then went to developer center and found that the status of XC: myapp.profile is invalid. I updated it and installed the XC: myapp.profile and it worked fine.

I think xcode is trying to manage the profile and you need to check the provisioning profile when you submit your binary to store, and ensure it is the correct one. And according to other answers it can be caused for various reasons so it can be really annoying.

UPDATE:

Once you've signed with the downloaded profile and confirmed that <code>aps-environment</code> was there when you try to submit to <code>App Store</code>, you should be able to change the profile and code signing entity to automatic and <code>iOS Developer</code>. Hope it can be improved in Xcode 7.

blocks|key|196526|text|我有这个问题是因为我的授权文件由于之前的手动编辑而格式不正确。我删除了错误格式的授权条目语法，然后我可以单击capabilities选项卡中的"fix“，Xcode将授权添加到我的文件中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|196527|下面是一个格式正确的授权文件(“Runner.entitlements”)的示例：|offset|length|style|CODE|196528|<!DOCTYPE+plist+PUBLIC+"-//Apple//DTD+PLIST+1.0//EN"+"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist+version="1.0">
<dict>
++++<key>aps-environment</key>
++++<string>development</string>
++++<key>com.apple.developer.applesignin</key>
++++<array>
++++++++<string>Default</string>
++++</array>
</dict>
</plist>|code-block|syntax|javascript|196529|entityMap^0|0|G|J|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|S|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I had this problem because my entitlements file was malformed due to previous manual editing. I removed the wrongly formatted entitlement entry syntax and then i could click "fix" in the capabilities tab and Xcode added the entitlement to my file.

Here is an example of a properly formatted entitlements file ("<code>Runner.entitlements</code>"):

<pre><code>&lt;!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"&gt;
&lt;plist version="1.0"&gt;
&lt;dict&gt;
 &lt;key&gt;aps-environment&lt;/key&gt;
 &lt;string&gt;development&lt;/string&gt;
 &lt;key&gt;com.apple.developer.applesignin&lt;/key&gt;
 &lt;array&gt;
 &lt;string&gt;Default&lt;/string&gt;
 &lt;/array&gt;
&lt;/dict&gt;
&lt;/plist&gt;
</code></pre>

blocks|key|196444|text|这里有一些非常好的建议。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|196445|提到Mina提供的最后一个屏幕截图，在最初归档我的应用程序后，上传过程中提到的配置配置文件包含一个通配符(XC.*)。这是错误的。|196446|为了解决这个问题，我们付出了相当大的努力。我不得不执行Simon+Woodside和Mina+Fawzy提供的建议的组合。|196447|如果您有任何与您的项目相关的现有证书和配置配置文件，现在是在本地删除它们并远程撤销它们的好时机。给自己一个新的开始。|196448|Mina+Fawzy的详细建议非常好。执行Mina的建议，如果执行正确，应该会在网上照顾到你。|196449|输入Simon的建议。我需要在我的项目中检查两件事。使用XCode，转到此处：|196450|项目->生成设置->代码签名|offset|length|style|BOLD|196451|查看代码签名Identity和Provisioning+Profile属性。确保将这两个属性设置为项目名称的属性。不要让XCode自动为你选择，也不要使用一些通用的代码签名身份(例如Iphone开发者)。|196452|在决定存档之前，请确保您可以将应用程序实际安装到您的设备上。|196453|entityMap^0|0|0|0|0|0|0|0|E|0|2|C|F|K|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@$N|14|O|15|P|Q]]|9|@]|A|$]]|$1|R|3|S|5|6|7|16|8|@$N|17|O|18|P|Q]|$N|19|O|1A|P|Q]]|9|@]|A|$]]|$1|T|3|U|5|6|7|1B|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|W|$]]

There are some really good suggestions on here. 

Referring to the last screenshot that Mina provided, after initially archiving my app, the provisioning profile mentioned during uploading contained a wildcard (XC.*). This is wrong.

It took some considerable effort in order to resolve this. I had to perform a combination of the suggestions that Simon Woodside &amp; Mina Fawzy provided. 

If you have any existing certificates and provisioning profiles related to your project, now would be a good time to remove them all locally, and revoke them all remotely. Give yourself a fresh start.

Mina Fawzy's detailed suggestion is excellent. Performing Mina's suggestion, if performed correctly, should take care of you online. 

Enter Simon's suggestion. Two things I needed to check inside my project. Using XCode, go here:

PROJECT -> BUILD SETTINGS -> CODE SIGNING

Review the Code Signing Identity and Provisioning Profile properties. Make sure you set those two properties to that of your project name. Don't allow XCode to automatically select for you, and don't use some generic code signing identity (e.g. Iphone Developer).

Make sure you can actually install the app onto your devices before deciding to archive.

blocks|key|2827746|text|在从Capabilities启用Push+Notification并重新制作所有证书后，我遇到的最大问题是，存储项目的目标名称和文件夹名称由两个用空格分隔的字符串组成。删除空间后，一切工作正常！|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|BOLD|entityRanges|data|2827747|entityMap^0|2|C|G|H|1N|4|1S|5|0^^$0|@$1|2|3|4|5|6|7|I|8|@$9|J|A|K|B|C]|$9|L|A|M|B|C]|$9|N|A|O|B|D]|$9|P|A|Q|B|D]]|E|@]|F|$]]|$1|G|3|-4|5|6|7|R|8|@]|E|@]|F|$]]]|H|$]]

The biggest problem that i have after enabling the <code>Push Notification</code> from <code>Capabilities</code> and remaking all the certificates is that the Target name and the folder name where was stored the project was composed from 2 strings separated by space. After removing the space all worked just fine!

blocks|key|2827870|text|Flutter中的|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2827871|您可以在ios/Runner下添加一个包含以下内容的文件Runner.entitlements，创建后，您的文件parh将类似于ios/Runner/Runner.entitlements：|offset|length|style|BOLD|CODE|2827872|<?xml+version="1.0"+encoding="UTF-8"?>
<!DOCTYPE+plist+PUBLIC+"-//Apple//DTD+PLIST+1.0//EN"+"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist+version="1.0">
<dict>
++++<key>aps-environment</key>
++++<string>development</string>
</dict>
</plist>|code-block|syntax|javascript|2827873|entityMap^0|0|0|2N|4|A|S|J|1S|U|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@$D|R|E|S|F|G]|$D|T|E|U|F|H]|$D|V|E|W|F|H]|$D|X|E|Y|F|H]]|9|@]|A|$]]|$1|I|3|J|5|K|7|Z|8|@]|9|@]|A|$L|M]]|$1|N|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|O|$]]

In Flutter
You can add a file <code>Runner.entitlements</code> under <code>ios/Runner</code> with below content and after created your file parh will be like <code>ios/Runner/Runner.entitlements</code> :
<pre><code>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&lt;!DOCTYPE plist PUBLIC &quot;-//Apple//DTD PLIST 1.0//EN&quot; &quot;http://www.apple.com/DTDs/PropertyList-1.0.dtd&quot;&gt;
&lt;plist version=&quot;1.0&quot;&gt;
&lt;dict&gt;
 &lt;key&gt;aps-environment&lt;/key&gt;
 &lt;string&gt;development&lt;/string&gt;
&lt;/dict&gt;
&lt;/plist&gt;
</code></pre>

blocks|key|199001|text|这突然发生在我身上，因为我的应用程序的分发配置文件已经过期了。Xcode开始使用通配符配置文件，但没有启用推送通知权限。我没有收到任何警告。修复很简单；我只需在Apple+Developer+Member中为我的应用程序生成另一个分发配置文件，下载它，然后双击以Xcode安装即可。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|199002|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|$]]

This happened to me suddenly because my app's distribution profile had expired. Xcode began using the wildcard profile instead, which did not have the push notification entitlement enabled. I didn't receive any warning. The fix was easy; I just had to generate another distribution profile for my app in the Apple Developer Member Center, download it, and double-click to install in Xcode.

I have an app for submission when it got rejected and I got the message

<blockquote>
 Missing Push Notification Entitlement - Your app appears 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.
</blockquote>

I checked my ad-hoc provisiong and there I found aps-environment and production however, when I open up my distribution provisioning, I don't find such.

Is this the cause of this error message and apple rejection, how can I fix it?

Missing Push Notification Entitlement

推送通知服务

文件存储

Flutter

Xcode

我有一个应用程序，当它被拒绝时，我收到了消息缺少推送通知权限-您的应用程序似乎注册了苹果推送通知服务，但应用程序签名的权限不包括“app environment”权限。如果您的应用程序使用Apple推送通知服务，请确保在预配门户中为推送通知启用了您的应用程序ID，并在使用包含"aps-environment“权利的分发预配配置文件对您的应用程序进行签名后重新提交。我检查了我的ad-hoc配置，在那

问缺少推送通知权利
EN

回答 18

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问缺少推送通知权利EN

回答 18

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问缺少推送通知权利
EN