blocks|key|275608|text|本质上，答案和其他人说的一样模糊。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|275609|确保你有一个“生产”添加(新的文件/代码Signing/Entitlements)|275610|Add“获取-任务-允许”(布尔值关闭)到Entitlements.plist|unordered-list-item|275611|
|275612|Add“aps”“生产”对到Entitlements.plist+--这最后一步可能是不必要的，但这是我在它工作之前做的步骤之一|275613|从iPhone/iPod中删除旧的手机配置文件(在设置/常规中)，使用文本编辑器在证书中为“aps+Organiser|275614|Delete”"production“对从iPhone/iPod|275615|Quit+XCode|275616|Download+|275617|删除旧的mobileprovision文件从XCode+Organiser|275618|Delete应用程序中|275619|启动XCode+|275620|通过拖动到XCode文档图标添加新的mobileprovision文件|275621|确保您已在目标信息:代码签名:代码签名|275622|检查构建结果是否使用了正确的配置文件以及是否已正确签名F227|275623|275624|冷静地重复这些步骤，直到它起作用，我花了大约五次不同的组合。我也从开发切换到了Ad-hoc，这显然不是必须的，但确实保证了一个新的mobileprovision文件。|275625|entityMap^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|19|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1A|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1B|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|1C|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|1D|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|1E|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|1F|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|1G|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|1H|8|@]|9|@]|A|$]]|$1|S|3|T|5|F|7|1I|8|@]|9|@]|A|$]]|$1|U|3|V|5|F|7|1J|8|@]|9|@]|A|$]]|$1|W|3|X|5|F|7|1K|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|F|7|1L|8|@]|9|@]|A|$]]|$1|10|3|11|5|F|7|1M|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|1N|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|15|3|16|5|6|7|1P|8|@]|9|@]|A|$]]|$1|17|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|18|$]]

Essentially the answer is the same vague one everyone else says

<ul>
<li>Make sure you have a "Entitlements.plist" added (New File/Code Signing/Entitlements)</li>
<li>Add "get-task-allow" (Boolean Off) to Entitlements.plist</li>
<li>Add "aps-environment" "production" pair to Entitlements.plist
-- This last step may be unnecessary but it was one of the steps I did just before it worked</li>
<li>Delete old mobileprovision files from iPhone/iPod (In Settings/General), </li>
<li>Delete old mobileprovision files from XCode Organiser</li>
<li>Delete App from iPhone/iPod</li>
<li>Quit XCode</li>
<li>Download fresh copy of Provisioning Certificate</li>
<li>Check for "aps-environment" "production" pair in certificate with a Text Editor</li>
<li>Start XCode</li>
<li>Add fresh mobileprovision file by dragging to XCode Doc icon</li>
<li>Make sure you have reassigned/assigned the correct certificate in the Target Info : Code Signing : Code Signing Identity</li>
<li>Double check that the Build Results to see it it's using the correct profile and is signed correctly</li>
</ul>

Repeat these steps calmly until it works, took me about five goes of various combinations. I also switched from Development to Ad-hoc which apparently isn't necessary but did guarantee a new mobileprovision file.

blocks|key|270116|text|我是几个小时后才弄明白的，所以除了JulianB说的|type|unstyled|depth|inlineStyleRanges|entityRanges|data|270117|270118|make确保您有一个应用程序图标。你可能有一个，但是当我们在图标版本之间时，我碰巧添加了推送。我尝试了很多不同的方法，但最终都是这样，所以这可能根本不是证书或签名设置的问题。|unordered-list-item|offset|length|style|BOLD|270119|我还读取了损坏的镜像文件，这也可能是导致|270120|在构建|270121|之前没有在我的entitlements.plist|270122|clean中添加/查看a环境密钥的原因|270123|270124|entityMap^0|0|0|0|G|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|W|8|@$F|X|G|Y|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|Z|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|10|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|11|8|@]|9|@]|A|$]]|$1|P|3|Q|5|E|7|12|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

I just figured this out after a few hours, so in addition to what JulianB said, 

<ul>
<li>make sure you have an application icon. You probably have one but i happened to add push when we were between icon versions. I tried allot of different things and in the end that was all it took so it might not even be a cert or signing setting issue.</li>
<li>I've also read a corrupt image file could also be the cause</li>
<li>i did not add/see an aps-environment key in my entitlements.plist</li>
<li>clean all targets before building</li>
</ul>

blocks|key|270126|text|我遇到了同样的问题“没有为应用程序找到有效的'aps-environment‘授权字符串”，但上面的解决方案对我不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|270127|我找不到关于这个错误的很好的文档，甚至找不到关键字“aps+environment”。|270128|经过一些修修补补，下面是为我解决问题的方法：|270129|使用文本编辑器打开您的开发配置证书"Appname.mobileprovision“，查找密钥”授权“，然后将此处找到的所有值添加到您的代码签名授权设置所引用的授权文件中。|270130|下面是一个你可以在里面找到的键/值的例子：|270131|<key>application-identifier</key>
<string>xyz.com.xyz.xyz</string>
<key>aps-environment</key>
<string>development</string>
<key>com.apple.developer.ubiquity-container-identifiers</key>
<array>
<string>xyz.*</string>
</array>
<key>com.apple.developer.ubiquity-kvstore-identifier</key>
<string>xyz.*</string>
<key>get-task-allow</key>
<true/>
<key>keychain-access-groups</key>
<array>
<string>xyz.*</string>
</array>|code-block|syntax|javascript|270132|将所有这些值添加到我的权限文件后，我的应用程序成功构建，我终于可以开始处理推送通知了。|270133|我不确定这些值是否应该由XCode自动添加到您的授权文件中，但它们肯定不是在我的项目中为我生成的。|270134|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|X|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|Z|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

I ran into the same "no valid 'aps-environment' entitlement string found for application" problem, but the above solutions did not work for me.

I could not find very good documentation about this error or even just the key "aps-environment".

After some tinkering around, here is what solved the problem for me:

Open your development provisioning certificate, "Appname.mobileprovision" with a text editor, look for the key "Entitlements" then add all of the values found here to your Entitlements file referenced by your Code Signing Entitlements setting.

Here is an example of what keys/values you'll find inside:

<pre><code>&lt;key&gt;application-identifier&lt;/key&gt;
&lt;string&gt;xyz.com.xyz.xyz&lt;/string&gt;
&lt;key&gt;aps-environment&lt;/key&gt;
&lt;string&gt;development&lt;/string&gt;
&lt;key&gt;com.apple.developer.ubiquity-container-identifiers&lt;/key&gt;
&lt;array&gt;
&lt;string&gt;xyz.*&lt;/string&gt;
&lt;/array&gt;
&lt;key&gt;com.apple.developer.ubiquity-kvstore-identifier&lt;/key&gt;
&lt;string&gt;xyz.*&lt;/string&gt;
&lt;key&gt;get-task-allow&lt;/key&gt;
&lt;true/&gt;
&lt;key&gt;keychain-access-groups&lt;/key&gt;
&lt;array&gt;
&lt;string&gt;xyz.*&lt;/string&gt;
&lt;/array&gt;
</code></pre>

After adding all of these values to my Entitlements file my app builds successfully and I can finally get back to working on Push Notifications.

I'm not sure if these values are supposed to be automatically added to your entitlements file by XCode, but they certainly weren't being generated for me in my project.

blocks|key|273757|text|当我从一个开发环境转移到一个正在开发的应用程序的生产环境时，我发现了这个问题。此过程包括创建新的配置文件、新的应用程序ID等。我创建了应用程序ID和配置文件，但团队代理必须配置推送通知。当我尝试使用新的配置文件恢复测试时(在应用程序配置为推送通知之后)，我遇到了“找不到适用于应用程序的有效'aps-environment‘授权字符串”的问题。然后，我记得在文档中读到了一点警告：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|273758|您必须以某种方式修改配置文件(例如，切换一个选项)，门户才能生成新的配置文件。如果配置文件不是那么“脏”，则会为您提供没有推送授权的配置文件。|273759|来源：Local+and+Push+Notification+Programming+Guide|offset|length|273760|对我来说，“弄脏”配置文件并重新安装它是解决问题所需的全部。根据文档，这是必需的，因为配置配置文件是在为应用程序配置推送通知之前创建的。这可能对任何人都有帮助，也可能没有帮助，但这可能解释(并消除了)手动向配置配置文件添加任何内容的需要。|273761|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Chapters/ProvisioningDevelopment.html#//apple_ref/doc/uid/TP40008194-CH104-SW5^0|0|0|3|19|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$F|U|G|V|1|W]]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

I found this question when I was moving from a development environment to a production one on an application that I am working on. This process involved the creation of a new profile, a new app ID, etc. I created the app ID and a profile, but the Team Agent had to configure the push notifications. I ran into the problem of "no valid 'aps-environment' entitlement string found for application" when I tried to resume testing with the new profile (after the app had been configured for push notifications). I then remembered reading a little caveat in the documentation:

"You have to modify the profile in some way (for example, toggle an option) for the portal to generate a new provisioning profile. If the profile isn't so "dirtied", you're given the profile without the push entitlements."

Source: <a href="https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Chapters/ProvisioningDevelopment.html#//apple_ref/doc/uid/TP40008194-CH104-SW5" rel="nofollow">Local and Push Notification Programming Guide</a>

For me, "dirtying" the provisioning profile and reinstalling it was all that was needed to fix the issue. Per the documentation, this was required because the provisioning profile was created before the app was configured for push notifications. This may or may not help anyone, but this probably explains (and eliminates) the need to manually add anything to the provisioning profile.

blocks|key|3187413|text|使用XCode4并收到相同的“没有为应用程序找到有效的‘aps+environment’授权字符串”时，我不得不执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3187414|从开发人员门户网站启用了APN+dev的Organizer|3187415|Regenerate新配置文件中从两个库%2B设备面板中删除旧的配置文件|unordered-list-item|3187416|
|3187417|3187418|3187419|确保在Organizer|3187420|3187421|Manually中的两个库%2B设备面板中都添加了新配置文件从我的设备上删除我的应用程序(按住直到它闪烁，然后点击X)|3187422|3187423|CMD%2BOPT%2BSHIFT%2BK+(清理构建文件夹)和CMD%2BSHIFT%2BK+(清理)|3187424|3187425|在项目>构建设置>代码签名|3187426|3187427|下设置正确的配置文件|3187428|
确保未选中目标>摘要<代码>F215下的‘使用权利’|3187429|entityMap^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|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|14|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|15|8|@]|9|@]|A|$]]|$1|I|3|-4|5|F|7|16|8|@]|9|@]|A|$]]|$1|J|3|H|5|6|7|17|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|18|8|@]|9|@]|A|$]]|$1|M|3|H|5|6|7|19|8|@]|9|@]|A|$]]|$1|N|3|O|5|F|7|1A|8|@]|9|@]|A|$]]|$1|P|3|H|5|6|7|1B|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|1C|8|@]|9|@]|A|$]]|$1|S|3|H|5|6|7|1D|8|@]|9|@]|A|$]]|$1|T|3|U|5|F|7|1E|8|@]|9|@]|A|$]]|$1|V|3|H|5|6|7|1F|8|@]|9|@]|A|$]]|$1|W|3|X|5|F|7|1G|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1H|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|11|$]]

Using XCode4 and receiving the same "no valid 'aps-environment' entitlement string found for application" I had to do the following:

<ul>
<li>Delete old provisioning profiles from both Library + Device panels in Organizer</li>
<li>Regenerate new profile with APN dev enabled from the developer portal website</li>
<li>Make sure new profile is added to both Library + Device panels in Organizer</li>
<li>Manually delete my app off my device (holding till it jiggles and hitting X)</li>
<li>CMD+OPT+SHIFT+K (Clean Build Folder) and CMD+SHIFT+K (Clean)</li>
<li>Set the proper profile under Project > Build Settings > Code Signing </li>
<li>Make sure 'Use Entitlements' is not checked under Targets > Summary</li>
</ul>

blocks|key|272223|text|对我来说，在将捆绑包标识符改成随机的东西之后，它就起作用了。确保签名错误确实出现(从organizer和device中删除所有供应配置文件，然后执行一次干净的构建CMD+%2B+OPT+%2B+SHFT+%2B+K，然后是CMS+%2B+SHFT+%2B+K，然后是CMD+%2B+R)，然后将捆绑包标识符改回适当的标识符。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|272224|entityMap^0|29|K|2X|E|3F|7|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

For me it worked after changing the bundle identifier to something random. Making sure that the signing error indeed shows up (remove all provision profiles from organizer and device and do a clean build <code>CMD + OPT + SHFT + K</code> then <code>CMS + SHFT + K</code> and then <code>CMD + R</code>) and then changing the bundle identifier back to appropriate one.

blocks|key|272232|text|我的解决方案是删除并重新创建开发配置文件。它被列为“无效”-未过期，续订失败(Xcode4.3.2和iOS+5.1)|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|272233|entityMap^0|E|6|N|6|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|$]]

My solution was to remove and create again Development Provisioning Profile. It was listed as "Invalid" - not expired and also renew failed (Xcode 4.3.2 and iOS 5.1)

blocks|key|2973686|text|设置：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2973687|Mac+OS+X+10.8+%2B+Xcode+4.4|2973688|我的简单解决方案：|2973689|2973690|在为您的应用程序ID设置推送通知并将其导入Xcode后，重新发出即席配置文件。|ordered-list-item|2973691|查看您的.xcodeproj文件夹(右键单击->显示程序包内容)，然后删除xcuserdata+|CODE|2973692|2973693|在这个问题上的一些提示：|2973694|在为我的应用激活推送通知后，我突然无法再创建即席文件。当我尝试安装我的应用程序时，我在iPhone上的控制台日志中遇到了如下错误：|2973695|Apr++1+20:56:10+unknown+installd[384]+<Error>:+entitlement+'keychain-access-groups'+has+value+not+permitted+by+a+provisioning+profile
Apr++1+20:56:10+unknown+installd[384]+<Error>:+entitlement+'get-task-allow'+has+value+not+permitted+by+a+provisioning+profile
Apr++1+20:56:10+unknown+installd[384]+<Error>:+entitlement+'application-identifier'+has+value+not+permitted+by+a+provisioning+profile
Apr++1+20:56:10+unknown+installd[384]+<Error>:+2ff66000+verify_signer_identity:+Could+not+copy+validate+signature:+-402620394
Apr++1+20:56:11+unknown+installd[384]+<Error>:+2ff66000+preflight_application_install:+Could+not+verify+executable+at+/var/tmp/install_staging.44jV0O/foo_extracted/Payload/PersonalTrainer-Tester-iPhone.app
Apr++1+20:56:11+unknown+com.apple.itunesstored[392]+<Notice>:+MobileInstallationInstall:+failed+with+-1
Apr++1+20:56:11+unknown+installd[384]+<Error>:+2ff66000+install_application:+Could+not+preflight+application+install
Apr++1+20:56:11+unknown+installd[384]+<Error>:+2ff66000+handle_install:+API+failed
Apr++1+20:56:11+unknown+installd[384]+<Error>:+2ff66000+send_message:+failed+to+send+mach+message+of+71+bytes:+10000003
Apr++1+20:56:11+unknown+installd[384]+<Error>:+2ff66000+send_error:+Could+not+send+error+response+to+client|code-block|syntax|javascript|2973696|有一些technical+note推荐使用codesign+-d+--entitlements+-+<YourAppName>.app来检查你的应用程序是否为苹果推送通知正确签名。如果codesign命令的输出没有将aps-environment设置为production或development，那么就有问题了！|2973697|据我所知，我使用临时配置文件注册的应用程序在<YourAppName>.app文件夹中总是有一个embedded.mobileprovision，其中包含特定的部分，例如：|2973698|<key>Entitlements</key>
<dict>
++++<key>application-identifier</key>
++++<string>ABCDEFGH.com.myappname.tester</string>
++++<key>aps-environment</key>
++++<string>production</string>
++++<key>get-task-allow</key>
++++<false/>
++++<key>keychain-access-groups</key>
++++<array>
++++++++<string>ABCDEFGH.*</string>
++++</array>
</dict>|2973699|在使用codesign之后，我意识到<YourAppName>.app中的实际二进制文件也包含了一些XML，这与我的embedded.mobileprovision文件非常不同：|2973700|<!DOCTYPE+plist+PUBLIC+"-//Apple//DTD+PLIST+1.0//EN"+"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist+version="1.0">
<dict>
++++<key>application-identifier</key>
++++<string>ABCDEFGH.com.myappname.tester</string>
++++<key>get-task-allow</key>
++++<true/>
++++<key>keychain-access-groups</key>
++++<array>
++++++++<string>ABCDEFGH.com.myappname.tester</string>
++++</array>
</dict>
</plist>|2973701|我认为这就是我们都遇到的错误消息的原因。(尽管这个错误可能有一些不同的根源，以及stackoverflow上的其他帖子建议)|2973702|The+executable+was+signed+with+invalid+entitlements.
The+entitlements+specified+in+your+application's+Code+Signing+Entitlements
file+do+not+match+those+specified+in+your+provisioning+profile.+(0xE8008016).|2973703|我的猜测是Xcode中有一些bug，它会阻止你plist中的设置在你的方案中被更新，然后导致你的应用程序最终使用错误的配置文件进行签名。因此，通过删除xcuserdata文件夹，您可以删除所有方案。因此，Xcode下一次将使用适当的设置重新创建它们，您将再次满意。|2973704|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/library/ios/#technotes/tn2265/_index.html^0|0|3|0|0|0|9|0|0|0|11|A|0|0|0|C|0|0|0|L|1A|3|E|0|0|M|H|1C|O|0|0|I|H|1M|O|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1O|8|@$9|1P|A|1Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1R|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1S|8|@$9|1T|A|1U|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|1V|8|@]|D|@]|E|$]]|$1|K|3|L|5|M|7|1W|8|@]|D|@]|E|$]]|$1|N|3|O|5|M|7|1X|8|@$9|1Y|A|1Z|B|P]]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|20|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|21|8|@$9|22|A|23|B|C]]|D|@]|E|$]]|$1|T|3|U|5|6|7|24|8|@]|D|@]|E|$]]|$1|V|3|W|5|X|7|25|8|@]|D|@]|E|$Y|Z]]|$1|10|3|11|5|6|7|26|8|@$9|27|A|28|B|P]]|D|@$9|29|A|2A|1|2B]]|E|$]]|$1|12|3|13|5|6|7|2C|8|@$9|2D|A|2E|B|P]|$9|2F|A|2G|B|P]]|D|@]|E|$]]|$1|14|3|15|5|X|7|2H|8|@]|D|@]|E|$Y|Z]]|$1|16|3|17|5|6|7|2I|8|@$9|2J|A|2K|B|P]|$9|2L|A|2M|B|P]]|D|@]|E|$]]|$1|18|3|19|5|X|7|2N|8|@]|D|@]|E|$Y|Z]]|$1|1A|3|1B|5|6|7|2O|8|@]|D|@]|E|$]]|$1|1C|3|1D|5|X|7|2P|8|@]|D|@]|E|$Y|Z]]|$1|1E|3|1F|5|6|7|2Q|8|@]|D|@]|E|$]]|$1|1G|3|-4|5|6|7|2R|8|@]|D|@]|E|$]]]|1H|$1I|$5|1J|1K|1L|E|$1M|1N]]]]

Setup: 

Mac OS X 10.8 + Xcode 4.4

My Simple Solution:

<ol>
<li>Reissue your ad hoc provisioning profile after you have setup push notifications for your app ID and import them to Xcode.</li>
<li>Take a look into your .xcodeproj folder (right click -> Show Package Contents) and delete the <code>xcuserdata</code> folder.</li>
<li>That's it ;)</li>
</ol>

Some hints on that issue:

After activating Push Notifications for my app I suddenly couldn't create ad hoc files anymore. I ran across errors in my Console log on my iPhone while trying to install my app such as those:

<pre><code>Apr 1 20:56:10 unknown installd[384] &lt;Error&gt;: entitlement 'keychain-access-groups' has value not permitted by a provisioning profile
Apr 1 20:56:10 unknown installd[384] &lt;Error&gt;: entitlement 'get-task-allow' has value not permitted by a provisioning profile
Apr 1 20:56:10 unknown installd[384] &lt;Error&gt;: entitlement 'application-identifier' has value not permitted by a provisioning profile
Apr 1 20:56:10 unknown installd[384] &lt;Error&gt;: 2ff66000 verify_signer_identity: Could not copy validate signature: -402620394
Apr 1 20:56:11 unknown installd[384] &lt;Error&gt;: 2ff66000 preflight_application_install: Could not verify executable at /var/tmp/install_staging.44jV0O/foo_extracted/Payload/PersonalTrainer-Tester-iPhone.app
Apr 1 20:56:11 unknown com.apple.itunesstored[392] &lt;Notice&gt;: MobileInstallationInstall: failed with -1
Apr 1 20:56:11 unknown installd[384] &lt;Error&gt;: 2ff66000 install_application: Could not preflight application install
Apr 1 20:56:11 unknown installd[384] &lt;Error&gt;: 2ff66000 handle_install: API failed
Apr 1 20:56:11 unknown installd[384] &lt;Error&gt;: 2ff66000 send_message: failed to send mach message of 71 bytes: 10000003
Apr 1 20:56:11 unknown installd[384] &lt;Error&gt;: 2ff66000 send_error: Could not send error response to client
</code></pre>

There is some <a href="https://developer.apple.com/library/ios/#technotes/tn2265/_index.html">technical note</a> which recommends using <code>codesign -d --entitlements - &lt;YourAppName&gt;.app</code> to check if your app is signed properly for Apple Push Notifications. In case the output of the codesign command does not have an aps-environment set to production or development there is something fishy!

As far as I knew so far, my apps signed with an adhoc provisioning profile always have an <code>embedded.mobileprovision</code> inside the <code>&lt;YourAppName&gt;.app</code> folder with a specific part in them such as:

<pre><code>&lt;key&gt;Entitlements&lt;/key&gt;
&lt;dict&gt;
 &lt;key&gt;application-identifier&lt;/key&gt;
 &lt;string&gt;ABCDEFGH.com.myappname.tester&lt;/string&gt;
 &lt;key&gt;aps-environment&lt;/key&gt;
 &lt;string&gt;production&lt;/string&gt;
 &lt;key&gt;get-task-allow&lt;/key&gt;
 &lt;false/&gt;
 &lt;key&gt;keychain-access-groups&lt;/key&gt;
 &lt;array&gt;
 &lt;string&gt;ABCDEFGH.*&lt;/string&gt;
 &lt;/array&gt;
&lt;/dict&gt;
</code></pre>

After using codesign I realized that the actual binary in <code>&lt;YourAppName&gt;.app</code> had some XML included as well, which said something very different than my <code>embedded.mobileprovision</code> file:

<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;application-identifier&lt;/key&gt;
 &lt;string&gt;ABCDEFGH.com.myappname.tester&lt;/string&gt;
 &lt;key&gt;get-task-allow&lt;/key&gt;
 &lt;true/&gt;
 &lt;key&gt;keychain-access-groups&lt;/key&gt;
 &lt;array&gt;
 &lt;string&gt;ABCDEFGH.com.myappname.tester&lt;/string&gt;
 &lt;/array&gt;
&lt;/dict&gt;
&lt;/plist&gt;
</code></pre>

I assume this is the cause for the error message we are all experiencing. (although this error can have some different roots as well as other posts on stackoverflow suggest)

<pre><code>The executable was signed with invalid entitlements.
The entitlements specified in your application's Code Signing Entitlements
file do not match those specified in your provisioning profile. (0xE8008016).
</code></pre>

My guess is that there is some bug in Xcode which keeps the settings in your plist from being updated in you schemes which then causes your app to be signed with the wrong provisioning profile in the end. So by deleting the xcuserdata folder you delete all schemes. Therefore Xcode will recreate them next time with the proper settings and you are happy again.

blocks|key|2973729|text|在“项目”“->”“生成设置”“->”“代码签名”“下，确保已选择正确的设置配置文件(启用推送的配置文件)。”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2973730|这就是我为了让它工作而需要改变的全部。|2973731|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|$]]

Under 'Project' -> 'Build Settings' -> 'Code Signing',
make sure you have selected the correct Provisioning profile (the one with push enabled).

That was all I needed to change in order to make it work.

blocks|key|270198|text|请确保选择正确。配置配置文件。我发现我正在尝试使用Team+Provisioning+profile。(应用程序标识符：*的)在列表的更下面，有一个正确的应用程序配置文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|270199|entityMap^0|1Q|O|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Make sure you have selected correct. Provisioning Profile. I found that I was trying with Team Provisioning profile.(for application identifier: *) Further down in the list, there was correct one for the app.

blocks|key|273873|text|10.8Xcode4.4的解决方案是打开appname.entitlements文件|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|273874|如果DataProtectionClass键的值为NSFileProtectionComplete，则将其删除！|273875|删除此键允许我在设备上测试来自Xcode的应用程序(这不会影响模拟)。|273876|entityMap^0|K|K|0|2|J|P|O|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|K|$]]

the solution for 10.8 Xcode 4.4 is
to open the <code>appname.entitlements</code> file 

and if the <code>DataProtectionClass</code> key has the value <code>NSFileProtectionComplete</code>,
delete it!

Deleting this key allows me to test apps from Xcode on devices (it wasn't affecting simulation).

blocks|key|2973831|text|我也有同样的问题。对我来说，修复方法是这样的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2973832|从项目设置->代码签名下的organizer.|2973833|Selected我的命名配置文件中，|unordered-list-item|2973834|删除并重新加载了配置文件。不知何故，它想要使用blabla.*身份。|ordered-list-item|2973835|2973836|2973837|当您尝试运行启用APN的应用程序时，通配符配置文件(前缀.*)不起作用，您需要指定启用APN的配置文件。|2973838|entityMap^0|0|0|0|0|0|0|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|F|7|R|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|S|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

I had the same problem. For me the fix was like this:

<ol>
<li>Removed and reloaded the provisioning profiles from the organizer.</li>
<li>Selected my named provisioning profile under project settings->code signing. Somehow it wanted to use the blabla.* identity.</li>
</ol>

The wildcard profile ([prefix].*) won't do when your trying to run a APN enabled application, you need to specify the APN enabled profile.

blocks|key|273903|text|我的问题是。我创建了一个配置了推送通知的应用程序，在应用程序代理中，我使用以下内容注册了推送通知：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|273904|[[UIApplication+sharedApplication]+registerForRemoteNotificationTypes:(UIRemoteNotificationTypeAlert+%7C+UIRemoteNotificationTypeBadge+%7C+UIRemoteNotificationTypeSound)];|code-block|syntax|javascript|273905|但在发布应用程序之前，我必须在其他开发人员门户上创建新的配置文件。我创建了新的应用程序Id，为开发和分发提供了新的配置，下载了新的配置，在应用程序目标中设置了正确的配置。我还更改了捆绑包的标识符。但是我得到了那个错误。|273906|问题是新的AppId没有配置为推送通知，而是调用|273907|[[UIApplication+sharedApplication]+registerForRemoteNotificationTypes:(UIRemoteNotificationTypeAlert+%7C+UIRemoteNotificationTypeBadge+%7C+UIRemoteNotificationTypeSound)];|273908|正在创建错误。当我配置推送通知时，错误没有再次显示。|273909|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|U|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

My problem was this.
I created app that had configured push notifications, and in app delegate I was registering for push notifications with:

<pre><code>[[UIApplication sharedApplication] registerForRemoteNotificationTypes:(UIRemoteNotificationTypeAlert | UIRemoteNotificationTypeBadge | UIRemoteNotificationTypeSound)];
</code></pre>

But before releasing app I had to create new provisioning profile on other developer portal. I created new App Id, new provisioning for development and distribution, downloaded new provisioning, in application target I've set correct provisioning. Also I changed bundle identifier.
But I was getting that error. 

Problem was that new AppId was not configured for push notifications, but calling 

<pre><code>[[UIApplication sharedApplication] registerForRemoteNotificationTypes:(UIRemoteNotificationTypeAlert | UIRemoteNotificationTypeBadge | UIRemoteNotificationTypeSound)];
</code></pre>

was creating error. 
When I configured push notifications error did not show again.

blocks|key|270257|text|以上这些对我来说都不起作用！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|270258|<>e116+Keychain|offset|length|style|BOLD|270259|Delete+device|ordered-list-item|270260|In+iPhone+device|270261|In中的iPhone+device|270262|In中的|270263|Delete+all+Provisioning+Profiles+in+Xcode+all+Developers++in+iPhone+all+Provisioning+Profiles，通过将正确的(证书/AppID/设备)+combination|270264|Download新Xcode|270265|Create+Provisioning+Profile|270266|Import新Provisioning+Profile分配到Xcode+Organizer|270267|CMD+%2B+Option+%2B+Shift+%2BK+CMD+H143+H143%2B+Shift+%2BK+CMD%2BShift%2BK+CMD%2BH244+CMD%2BShift%2BK+CMD：)H250+H250G251中，删除由Xcode|270268|Create自动创建的新Provisioning+Profile|270269|270270|270271|entityMap^0|0|7|8|0|0|3|D|0|0|1|B|L|10|2H|1|0|E|1|0|R|1|7|K|U|F|1|2W|5|1|1|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@$D|18|E|19|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|1A|8|@]|9|@]|A|$]]|$1|K|3|L|5|J|7|1B|8|@$D|1C|E|1D|F|G]]|9|@]|A|$]]|$1|M|3|N|5|J|7|1E|8|@]|9|@]|A|$]]|$1|O|3|P|5|J|7|1F|8|@]|9|@]|A|$]]|$1|Q|3|R|5|J|7|1G|8|@$D|1H|E|1I|F|G]|$D|1J|E|1K|F|G]]|9|@]|A|$]]|$1|S|3|T|5|J|7|1L|8|@$D|1M|E|1N|F|G]]|9|@]|A|$]]|$1|U|3|V|5|J|7|1O|8|@$D|1P|E|1Q|F|G]]|9|@]|A|$]]|$1|W|3|X|5|J|7|1R|8|@$D|1S|E|1T|F|G]|$D|1U|E|1V|F|G]]|9|@]|A|$]]|$1|Y|3|Z|5|J|7|1W|8|@$D|1X|E|1Y|F|G]]|9|@]|A|$]]|$1|10|3|11|5|J|7|1Z|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|20|8|@]|9|@]|A|$]]|$1|13|3|-4|5|6|7|21|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|22|8|@]|9|@]|A|$]]]|15|$]]

None of the above worked for me!

<ol>
<li>Delete all Provisioning Profiles in Xcode Organizer</li>
<li>Delete all Developers certificates in Keychain</li>
<li>Delete all Provisioning Profiles in iPhone device</li>
<li>In iOS Provisioning Portal, delete Development Provisioning Profile which was created automatically by Xcode</li>
<li>Create a new Provisioning Profile by assigning the correct (Certificate/AppID/Device) combination</li>
<li>Download the new Provisioning Profile</li>
<li>Import the new Provisioning Profile into Xcode Organizer</li>
<li>CMD + Option + Shift + K</li>
<li>CMD + Shift + K</li>
<li>CMD + R</li>
<li>Hooray :)</li>
</ol>

blocks|key|270273|text|确保您以正确的方式使用配置文件中的应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|270274|我的意思是，如果你的应用程序只为分发启用了推送通知，而你试图通过构建XCode来获得推送通知，那么这将不会起作用。|270275|我遇到了这个问题，通过为App+ID启用开发推送通知，然后使用开发配置文件，我不再收到错误，正确的警报视图询问我是否想要获得推送通知。|270276|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Make sure that you are using the app in the correct way with the provisioning profile.

What I mean is that if you've enabled your app for Push notifications for Distribution only, and you are trying to get push notifications to work via building with XCode, this will not work.

I ran into this problem, and by enabling push notification for Development for the App ID, and then using the development provisioning profile I no longer got the error and the correct alert view asked if I wanted to get push notifications.

blocks|key|2973981|text|我遇到了这个问题，场景是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2973982|我已经设置了一个没有推送通知支持的应用程序id。我使用的是Xcode5.1%2B+iOS+7.1|2973983|之后，编辑了app+id，添加了开发和生产中的推送通知。|2973984|已为两者创建APNs证书。|2973985|当您使用连接到Xcode的设备测试PN时，一切工作正常。当您将应用程序发布到生产环境时，问题就会出现，您会不断收到：|2973986|"Error+Domain=NSCocoaErrorDomain+Code=3000+"no+valid+'aps-environment'+entitlement+string
+found+for+application"+UserInfo=0x15b200+{NSLocalizedDescription=no+valid+++++
'apsenvironment'+entitlement+string+found+for+application}"+error.|code-block|syntax|javascript|2973987|对我有效的解决方案是|2973988|为开发和分发删除配置文件(Xcode和Developer+portal).|2973989|Delete您的应用程序ID+(Developer+portal).|unordered-list-item|2973990|
|2973991|Create+a+new+App+ID，具有开发推送通知支持))和使用新应用程序ID的新配置文件。|2973992|2973993|在Xcode上安装它们。|2973994|2973995|在开发和分发版本上进行测试。|2973996|2973997|entityMap^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|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1A|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1B|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1C|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1D|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|1E|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1F|8|@]|9|@]|A|$]]|$1|S|3|T|5|U|7|1G|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1H|8|@]|9|@]|A|$]]|$1|X|3|Y|5|U|7|1I|8|@]|9|@]|A|$]]|$1|Z|3|W|5|6|7|1J|8|@]|9|@]|A|$]]|$1|10|3|11|5|U|7|1K|8|@]|9|@]|A|$]]|$1|12|3|W|5|6|7|1L|8|@]|9|@]|A|$]]|$1|13|3|14|5|U|7|1M|8|@]|9|@]|A|$]]|$1|15|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|16|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|17|$]]

I had this problem, the scenario was:

I had setup an app id without push notifications support. I'm using Xcode 5.1 + iOS 7.1

Later, edited the app id to add push notifications in development and production.

Created the APNs certificates for both.

When you test PN using your device attached to Xcode, everything works ok. The problem appears when you release the app to production, you keep getting:

<pre><code>"Error Domain=NSCocoaErrorDomain Code=3000 "no valid 'aps-environment' entitlement string
 found for application" UserInfo=0x15b200 {NSLocalizedDescription=no valid 
'apsenvironment' entitlement string found for application}" error.
</code></pre>

The solution that worked for me was:

<ol>
<li>Delete provisioning profiles for development and distribution (Xcode and Developer portal).</li>
<li>Delete your app ID (Developer portal).</li>
<li>Create a new App ID with Push Notifications Support for Development and Production.</li>
<li>Create new provisioning profiles using the NEW App ID.</li>
<li>Install them on Xcode.</li>
<li>Test on development and distribution release.</li>
</ol>

blocks|key|2974008|text|​|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2974009|📷|atomic|offset|length|2974010|2974011|让配置文件正确无误，这样就可以帮助me.Hope了。|2974012|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/5cf408af5e0b308903b1c9053604fe85.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]]]]

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

Make the profile right and this work for me.Hope this help.

blocks|key|3187738|text|实际上，您的临时配置文件已从apple+developer站点中删除。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3187739|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|$]]

Actually your provisional profile deleted from apple developer site.&amp; you get error for

blocks|key|275911|text|在我的例子中，这个错误的解决方案在经过几个小时的证书修补后变得很简单……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|275912|在项目配置的Capabilities选项卡中，我必须启用Push+Notification标志才能生成环境文件。|offset|length|style|CODE|275913|macOS+Sierra+10.12+-Xcode8.1|275914|​|275915|📷|atomic|275916|275917|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/94f82d6dec084de92fe3a6f932952837.png|imageAlt^0|0|6|C|S|H|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@$D|10|E|11|F|G]|$D|12|E|13|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|14|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|15|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|16|8|@]|9|@$D|17|E|18|1|19]]|A|$]]|$1|O|3|K|5|6|7|1A|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W|X|-4]]]]

In my case, the solution for this error turned out to be simple after hours of tinkering with certificates...

In the <code>Capabilities</code> tab of the project configuration, I had to enable the <code>Push Notification</code> flag in order for the environment files to be generated.

macOS Sierra 10.12 - Xcode 8.1

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

I've read <a href="https://stackoverflow.com/questions/3728800/where-does-xcode-take-applications-identifier-from">Where does xcode take application&#39;s Identifier from?</a> , <a href="https://stackoverflow.com/questions/2309821/xcode-bundle-identifier-formatting-from-product-name">XCode bundle identifier formatting from {PRODUCT_NAME}</a> , and loads more but...

I'm trying to get push notifications going and getting the dreaded 

<blockquote>
 "Error Domain=NSCocoaErrorDomain Code=3000 "no valid 'aps-environment'
 entitlement string found for application" UserInfo=0x15b200
 {NSLocalizedDescription=no valid 'aps-environment' entitlement string
 found for application}" error.
</blockquote>

I'm fairly certain I've followed all the steps correctly, including:

<ul>
<li>made the push certificate well in advance of the provisioning cert</li>
<li>made a 'Entitlements.plist'</li>
<li>added a get-task-allow boolean and set it to true (ad-hoc release)</li>
</ul>

The only think I can't quite get my head around is the Bundle Identifier

The push certificate is for

<pre><code>XXXXXXXXXX.com.julianbaker.pwcnewsuk
</code></pre>

The Bundle Indentifier in PwCNewUK-Info.plist is for

<pre><code>com.julianbaker.${PRODUCT_NAME:rfc1034identifier}
</code></pre>

If I manually change it to

<pre><code>com.julianbaker.pwcnewsuk
</code></pre>

I get a UDID mismatch error as the app is seen as PwCNewsUK

When I've Googled this there seems to be some confusion over the matter, but it seems they have to match?

QUESTION:

What should the Bundle Indentifer be to match the push certificate of 
XXXXXXXXXX.com.julianbaker.pwcnewsuk ?

QUESTION:

Do I need to add a "aps-environment" entitlement to the provisioning profile, and if so where and how? (See <a href="http://www.airplaysdk.com/node/3174" rel="nofollow noreferrer">http://www.airplaysdk.com/node/3174</a> amongst others)

Loving iPhone development but sheesh it can be a headbanger at times!

Bundle Identifier and push certificate... aps-environment entitlement error

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我读过，，还有更多，但是...我正在试着让推送通知开始，让可怕的 "Error Domain=NSCocoaErrorDomain Code=3000“找不到应用程序的有效'aps-environment‘授权字符串”UserInfo=0x15b200 {为应用程序找到的NSLocalizedDescription=n...

问捆绑标识符和推送证书...aps-环境授权错误
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问捆绑标识符和推送证书...aps-环境授权错误EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问捆绑标识符和推送证书...aps-环境授权错误
EN