blocks|key|2774230|text|我认为您的问题在于您使用xCode4.6的配置文件，而现在您使用的是xCode5。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2774231|您需要通过XCode+>+Preferences+>+Accounts刷新证书/配置配置文件|2774232|XCode+>首选项>帐户>单击您的开发人员帐户>查看详细信息按钮(右下角)>签名Iden/PPs屏幕出现>点击刷新。|2774233|然后从构建设置中再次选择正确的配置文件，并清理和构建您的项目。|2774234|希望这对你有帮助。|2774235|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

I think your problem lies because of the profile that you were using xCode4.6 and now you are using xCode5.

You need to refresh certificates/provisioning profiles via XCode > Preferences > Accounts

XCode > Preferences > Accounts > Click on your DEV ACCOUNT > View Details button (bottom right) > Signing Iden/PPs screen appears > hit Refresh.

Then choose again from build settings the correct profile and clean and build your project. 

Hope this helps you.

blocks|key|2774259|text|我发现了问题所在。我在developer.apple.com上创建的应用程序不包含应用程序间音频。Xcode上的项目授权plist文件将inter+audio设置为YES+(默认)。有一次，我在developer.apple.com上更改了应用程序配置上的设置，以启用应用程序间音频。然后我的应用程序就会在我的设备上运行。我猜这是苹果的新规则，让你的应用程序设置在developer.apple.com和你的xcode项目设置上保持一致。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2774260|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 found out the problem. The app I created on developer.apple.com does not include inter-app-audio. The project entitlements plist file on Xcode has inter-app-audio set to YES (by default). Once I changed the setting on my app configuration on developer.apple.com to enable the inter-app-audio. Then my app runs on my devices. I guess that is apple's new rule to make your app settings consistent on both developer.apple.com and your xcode project setting.

blocks|key|2987165|text|我在XCode+5中也遇到了同样的问题，这对我还是有帮助的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2987166|XCode+>+Preferences+>+Location+tab+>+DerivedData|code-block|syntax|javascript|2987167|按向左小箭头在查找器中打开DerivedData。移动到项目的回收站文件夹并重新构建。|2987168|​|2987169|📷|atomic|offset|length|2987170|2987171|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/cc9839fce9934bca4c81b1d0a6445b3a.png|imageAlt^0|0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|11|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|12|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|13|8|@]|9|@$N|14|O|15|1|16]]|A|$]]|$1|P|3|J|5|6|7|17|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X|Y|-4]]]]

I had the same problem in XCode 5. This helped me anyway. 

<pre><code>XCode &gt; Preferences &gt; Location tab &gt; DerivedData
</code></pre>

Press a little left arrow to open DerivedData in Finder. Move to trash folder of your project and rebuild. 

<img src="https://i.stack.imgur.com/M8UTv.png" alt="Screenshot">

blocks|key|2774327|text|我可以通过打开/关闭Xcode5中的"Game+Center“权限来解决这个问题:-)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2774328|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 was able to fix this by toggling on/off "Game Center" entitlement in Xcode 5 :-)

blocks|key|172424|text|重启Xcode对我来说很有效。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|172425|entityMap^0|0|7|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|$]]

Restarting Xcode was what worked for me.

blocks|key|2774397|text|我解决这个问题的方法是删除project.pbxproj中的所有"PROVISIONING_PROFILE=..."和"PROVISIONING_PROFILE[sdk=iphoneos*]"+=+...，重新启动Xcode并再次为目标设置配置文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|2774398|entityMap^0|D|F|W|Q|1N|17|0^^$0|@$1|2|3|4|5|6|7|I|8|@$9|J|A|K|B|C]|$9|L|A|M|B|D]|$9|N|A|O|B|D]]|E|@]|F|$]]|$1|G|3|-4|5|6|7|P|8|@]|E|@]|F|$]]]|H|$]]

I solve this by deleting all <code>"PROVISIONING_PROFILE=..."</code> and <code>"PROVISIONING_PROFILE[sdk=iphoneos*]" = ...</code> in project.pbxproj and restart Xcode and set provisioning profiles for the target again.

blocks|key|2774421|text|我必须在Xcode5中匹配应用程序的功能|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2774422|Capabilities+->+
In-App+purchase+->+ON
Game+Center+->+ON|code-block|syntax|javascript|2774423|在附带条件的档案里。|2774424|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I had to match the app's capabilities in Xcode5 under

<pre><code>Capabilities -&gt; 
In-App purchase -&gt; ON
Game Center -&gt; ON
</code></pre>

with that in the provisoning profile.

blocks|key|2987332|text|如果重启xcode不起作用，创建一个新的配置文件，并确保包含您的测试设备。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2987333|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|$]]

If restarting xcode doesn't work
make a new provision profile and be sure to include your test devices.

blocks|key|2987377|text|出了点问题。解决方法:转到right+target+->+capabilities+->+for+me有"In-App+Purchase“和按钮来修复它的问题。关闭-打开操作已修复问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2987378|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|$]]

Had some issue. Resolve: go to right target -> capabilities -> for me there was issue with "In-App Purchase" and button to fix it. Off-on operation fixed issue.

blocks|key|2987418|text|在我的案例中:我需要在中启用应用间音频|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2987419|Capabilities+->++Inter-App+Audio|offset|length|style|CODE|2987420|我想因为我使用的是Parse.com通知，所以它需要链接到AudioToolbox.framework|2987421|entityMap^0|0|0|W|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

In my case: I need enable Inter-App Audio in 

<code>Capabilities -&gt; Inter-App Audio</code>

I think because I use Parse.com Notification, it need link to AudioToolbox.framework

blocks|key|2987474|text|Xcode6.1+(HealthKit示例)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2987475|由于HealthKit集成，我收到了这个错误:我已经启用了应用内购买，游戏中心和Healkit解决了我的问题。与我在配置文件中启用的相同。|2987476|​|2987477|📷|atomic|offset|length|2987478|2987479|2987480|2987481|2987482|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/4cbc51a8f11517baacf9e8f5b914109d.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/de7134423d94fc4f14558f2be995793a.png^0|0|0|0|0|1|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|12|8|@]|9|@$I|13|J|14|1|15]]|A|$]]|$1|K|3|E|5|6|7|16|8|@]|9|@]|A|$]]|$1|L|3|E|5|6|7|17|8|@]|9|@]|A|$]]|$1|M|3|G|5|H|7|18|8|@]|9|@$I|19|J|1A|1|1B]]|A|$]]|$1|N|3|E|5|6|7|1C|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V|W|-4]]|X|$5|R|S|T|A|$U|Y|W|-4]]]]

xcode 6.1 (HealthKit sample)

I was getting this error due to HealthKit integration: I had enabled In-App Purchase, Game Center and Healkit solved my issue.. The same I have enabled in Provision profile.

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

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

blocks|key|2987531|text|(Xcode+6.1)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2987532|对我来说，问题出在我的构建设置中；当我试图部署到设备时，我将我的供应配置文件设置为App+Store生产配置文件。我把它切换到“自动”，它解决了我的问题。您也可以将其设置为您的开发人员配置文件。|2987533|我还有两个证书，所以我将我的第二个证书添加到了我的开发配置中。其他人可能不会有这个问题。|2987534|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|$]]

(Xcode 6.1) 

The problem for me was in my Build Settings; I had my Provisioning Profile set to an App Store Production Profile when trying to deploy to a device. I switched it to 'Automatic' and it resolved my issue. You could also set it to your Dev Provision Profile.

I also have 2 Certificates, so I added my second Certificate to my dev provision. Others probably won't have this problem.

blocks|key|172603|text|启用功能->应用间音频也为我修复了这个问题。我也在尝试通过解析发送推送通知|type|unstyled|depth|inlineStyleRanges|entityRanges|data|172604|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|$]]

Enabling Capabilities -> Inter-App Audio fixed this issue for me as well. I am also trying to send push notifications through parse

blocks|key|2987578|text|简单的干净和构建似乎为我解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2987579|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|$]]

Simple clean-and-build seemed to fix it for me.

blocks|key|2774957|text|最新的Xcode解决方案|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2774958|首先，您必须检查会员中心中为您的特定AppID启用了什么|2774959|​|2774960|📷|atomic|2774961|2774962|然后在Xcode中的适当目标中，您必须启用相同的功能:在本例中：App+Group，Game+Center，In-App+Purchase。在你的目标中，所有的都必须在Xcode中启用。|CODE|2774963|2774964|2774965|2774966|但是，对于调试模式，这并不重要：|2774967|2774968|2774969|2774970|这对您的RELEASE模式非常重要：|2774971|2774972|2774973|注意，Game+Center和In-App+Purchase在成员中心中默认是启用的，但在Xcode的目标中是禁用的。|2774974|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/3e7ab667eb474d5f281e082bcc004e64.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/3f1d897b9ba98822348a32f41bd85bae.png|2|https://ask.qcloudimg.com/http-save/yehe-900000/c8ddefe4cc4258ea7e7dd80f944f4816.png|3|https://ask.qcloudimg.com/http-save/yehe-900000/8d77868158cc9ea73b88f81ded7238b9.png^0|3|5|0|8|4|I|5|0|0|0|1|0|0|0|W|9|16|B|1I|F|0|0|0|1|1|0|0|5|2|0|0|0|1|2|0|0|4|7|0|0|1|3|0|0|3|B|F|F|V|4|0^^$0|@$1|2|3|4|5|6|7|1J|8|@$9|1K|A|1L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1M|8|@$9|1N|A|1O|B|C]|$9|1P|A|1Q|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1R|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1S|8|@]|D|@$9|1T|A|1U|1|1V]]|E|$]]|$1|M|3|I|5|6|7|1W|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1X|8|@$9|1Y|A|1Z|B|P]|$9|20|A|21|B|P]|$9|22|A|23|B|P]]|D|@]|E|$]]|$1|Q|3|I|5|6|7|24|8|@]|D|@]|E|$]]|$1|R|3|K|5|L|7|25|8|@]|D|@$9|26|A|27|1|28]]|E|$]]|$1|S|3|I|5|6|7|29|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|2A|8|@$9|2B|A|2C|B|C]]|D|@]|E|$]]|$1|V|3|I|5|6|7|2D|8|@]|D|@]|E|$]]|$1|W|3|K|5|L|7|2E|8|@]|D|@$9|2F|A|2G|1|2H]]|E|$]]|$1|X|3|I|5|6|7|2I|8|@]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|2J|8|@$9|2K|A|2L|B|C]]|D|@]|E|$]]|$1|10|3|K|5|L|7|2M|8|@]|D|@$9|2N|A|2O|1|2P]]|E|$]]|$1|11|3|I|5|6|7|2Q|8|@]|D|@]|E|$]]|$1|12|3|13|5|6|7|2R|8|@$9|2S|A|2T|B|P]|$9|2U|A|2V|B|P]|$9|2W|A|2X|B|C]]|D|@]|E|$]]|$1|14|3|-4|5|6|7|2Y|8|@]|D|@]|E|$]]]|15|$16|$5|17|18|19|E|$1A|1B|1C|-4]]|1D|$5|17|18|19|E|$1A|1E|1C|-4]]|1F|$5|17|18|19|E|$1A|1G|1C|-4]]|1H|$5|17|18|19|E|$1A|1I|1C|-4]]]]

The solution for latest Xcode:

First you have to check what is enabled in your Member center for your specific AppID:

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

Then in your appropriate target in Xcode you have to enabled the same capabilities: In this case: <code>App Group</code>, <code>Game Center</code>, <code>In-App Purchase</code>. All of them have to be enabled in your target in Xcode.

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

However it doesn't matter for DEBUG mode:

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

it very matters for your RELEASE mode:
<img src="https://i.stack.imgur.com/j61RP.png" alt="enter image description here">

Note that <code>Game Center</code> and <code>In-App Purchase</code> are enabled by default in Member Center but are disabled in Xcode's target.

blocks|key|2987779|text|这似乎是Xcode内部的一个小bug。无论如何，尝试使用存档它，即使entitlements有问题。如果您的授权没有问题，则上传时不会出现任何问题。苹果接受它，你的应用程序就会发布到AppStore上。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|2987780|我做到了，并且成功了：)|2987781|entityMap^0|S|2|Y|C|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@$9|L|A|M|B|C]|$9|N|A|O|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|P|8|@]|E|@]|F|$]]|$1|I|3|-4|5|6|7|Q|8|@]|E|@]|F|$]]]|J|$]]

It seems to be a little bug inside Xcode. Try to archive it anyway, even there is a problem with <code>entitlements</code>. If your entitlements are fine, it will be uploaded without any problem. Apple accept it, and your app will be published to the AppStore. 

I did it, and it worked:)

blocks|key|172693|text|这里的答案似乎不够充分，所以我补充了我的两点意见：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|172694|真正的解决方案是，您的配置文件中存储的内容通常不匹配(请查看developer.apple.com+->+members+->+certificates+->您正在使用的证书[请务必检查开发/生产)和您的应用程序中启用的内容(双击项目名称)，在水平菜单下选择‘’Capabilities‘(功能)(位于’General‘(常规)旁边)。|172695|如果您最近更改了其中一个，请确保刷新XCode+->+Preferences+->+Accounts+->+Details+->+refresh图标下的证书并重新启动XCode。|172696|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|$]]

The answers here seem a bit inadequate so I'm adding my two cents:

The real solution is that there is generally a mismatch between what is stored in your provisioning profile (check at developer.apple.com -> members -> certificates -> the cert you're using [be sure to check if dev/production) and what is enabled in your app (double click project name), under horizontal menu select'Capabilities' (next to 'General').

If you've recently changed one of these, be sure to refresh your certificates under XCode -> Preferences -> Accounts -> Details -> Refresh Icon and restart XCode.

blocks|key|172698|text|在我的情况下，APNS证书已过期，请删除过期的证书并重新生成配置配置文件来解决此问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|172699|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|$]]

In my case APNS certificate is expired, remove the expired certificate and regenerate the provisioning profile fixes the issue.

blocks|key|2987844|text|在我的例子中，设备没有被添加。因此，我必须添加设备并生成新的配置配置文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2987845|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|$]]

In my case, the device wasn't added. So I had to add the device and generate a new provisioning profile.

blocks|key|2775176|text|我也面临着同样的问题。对我来说，解决方案是以下步骤。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2775177|在+Identifier.|2775178|Regenerate+provisioning+profile|ordered-list-item|2775179|中，我使用开发者帐户上传了推送证书|2775180|结论:如果有任何服务已启用但未配置，则禁用或配置该服务可能会解决问题|2775181|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|P|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|Q|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|L|$]]

I faced same issue. For me solution was below steps.

<ol>
<li>I went on developer account i uploaded push certificate in App Identifier.</li>
<li>Regenerate provisioning profile</li>
</ol>

Conclusion: If there is any service enabled but it's not configured then eigther disabling or configuring that service might solve the problem

blocks|key|171945|text|如果这里列出的其他好答案对你不起作用，尝试打开Keychain+Access并删除所有'iPhone+Developer...‘。用于代码签名的主证书以外的证书。我发现我有几个被吊销的证书，以及来自其他队友的证书需要删除。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|171946|entityMap^0|J|1G|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|$]]

If the other good answers listed here aren't working for you, try opening Keychain Access and removing all 'iPhone Developer...' certificates other than the primary one you're using for code signing. I found that I had several revoked certificates, and certificates from my other teammates that needed to be deleted.

blocks|key|2987893|text|(Xcode+7.3.1)我只在一个设备上遇到了这个问题。对我来说，解决这个问题的方法是从同事的电脑上(成功地)运行这个应用程序，之后我的电脑上就不再出现这个错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2987894|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|$]]

(Xcode 7.3.1)
I had this issue with only one device in particular.
What fixed it for me was to run the app from a colleague's computer(successfully) and after that I stopped getting this error on my computer.

blocks|key|2775224|text|在我的例子中，我不得不接受Apple开发者许可协议。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2775225|登录到苹果开发者账号，观察如下所示的通知消息。|2775226|“Apple+Developer+Program许可协议已更新。为了访问某些成员资源，*必须在2016年6月28日之前接受最新的许可协议。”|2775227|早些时候，我无法将iCloud容器添加/编辑到应用程序ID中，尽管我更改/检查了功能、配置文件、证书等。在同意合同后，事情开始顺利运行。|2775228|希望这能节省一些人的宝贵时间。|2775229|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

In my Case, i had to accept the Apple Developer License Agreement. 

Login to apple developer account and observe the notification message similar to below. 

"The Apple Developer Program License Agreement has been updated. In order to access certain membership resources,**** must accept the latest license agreement by June 28, 2016." 

Earlier, i was not able to add/edit iCloud Containers to the App ID though i changed/checked Capabilities, Provisioning Profiles, Certificates etc. After agreement to the contract, things started working smoothly.

Hopefully, it would save someone's valuable time.

blocks|key|2775238|text|首先也是最重要的是，如果您手动设置了配置配置文件，请确保为您在构建之前选择的配置选择了正确的配置配置文件。如果您已经将automatic设置为您的配置文件，请确保Xcode在构建时选择了正确的配置文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2775239|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|$]]

First and foremost make sure the correct provisioning profile is selected for the configuration that you have selected before building if you have manually set the provisioning profile. If you have set automatic as your provisioning profile make sure the correct provisioning profile is being picked up by Xcode while building.

blocks|key|2987964|text|另一件需要检查的事情--确保在和中都选择了正确的实体|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2987965|2987966|+Targets+->+Your+Target+->生成设置->签名|blockquote|2987967|2987968|2987969|和|2987970|2987971|项目->您的项目->生成设置->代码签名实体|2987972|2987973|2987974|当我在一个应用程序中选择了完整的开发人员配置文件，而在另一个应用程序中选择了不同的(非开发人员)+Apple+ID时，我收到了这条消息，即使在应用程序中没有请求授权。|2987975|entityMap^0|F|1|0|0|0|0|0|0|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|10|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|11|8|@]|D|@]|E|$]]|$1|K|3|-4|5|6|7|12|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|N|3|-4|5|6|7|16|8|@]|D|@]|E|$]]|$1|O|3|P|5|I|7|17|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|18|8|@]|D|@]|E|$]]|$1|R|3|-4|5|6|7|19|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|1A|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]]|V|$]]

Another thing to check - make sure you have the correct entities selected in both

<blockquote>
 Targets -> Your Target -> Build Settings -> Signing
</blockquote>

and

<blockquote>
 Project -> Your Project -> Build Settings -> Code Signing Entity
</blockquote>

I got this message when I had a full dev profile selected in one and a different (non-developer) Apple ID selected in the other, even with no entitlements requested in the app.

blocks|key|170770|text|我最近遇到了完全相同的问题。在阅读了许多不同的建议后，我终于找到了问题的根本原因。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|170771|移动配置文件实际上与Xcode.生成的授权文件不匹配|offset|length|style|BOLD|170772|尽管所有的文件都是由Apple工具自动更新的，但它们并不正确。|170773|如果您从Apple+portal下载配置文件并将其打开(您可以打开它，因为它只是由您的证书签名的plist文件，所以它可以通过文本编辑器读取)，并将其与您的授权文件(由Xcode自动生成并驻留在项目文件中)进行比较(因此，它再次是plist+XML文件，可通过文本编辑器读取)。然后你就可以看到不同之处。|170774|在我的案例中，它是游戏中心授权。它在门户上显示为选中(默认情况下选中)，但实际上此授权不包括在移动配置文件中。所以这是从授权文件中删除的问题。|170775|，因此结果是-移动配置文件的内容有时与应用程序ID配置页面上显示的内容不匹配。|170776|entityMap^0|0|0|G|0|0|0|0|0|13|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@$D|Z|E|10|F|G]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|Q|$]]

I came across exactly the same issue quite recently. After reading many different advices which none of them worked for me, I finally went under the hood and found the root cause of the issue.

Mobile provisioning file actually DOESN'T match with the Entitlements file generated by Xcode. 

Although all files are anaged automatically by Apple tool, they are not correct.

If you download provisioning file from Apple portal and open it (you can open it because it's just plist file signed by your certificate, so it's readable by text editor) and compare it with your Entitlements file (automatically generated by Xcode and residing in project files (so it's again plist XML file readable by text editor). Then you can see the difference.

In my case it was Game Center entitlement. It was displayed on the portal as checked (checked by default) but actually this entitlement was not included in mobile provisioning file. So it was matter of deleting it from Entitlements file.

So the result is - content of mobile provisioning profile sometimes doesn't match with what is displayed on the APP ID configuration page.

blocks|key|174464|text|在我检查应用程序测试目标并将其设置为与主应用程序相同的配置文件之前，没有任何解决方案对我起作用。或者，如果您使用的是自动演唱，请确保在测试目标中选择了相同的团队。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|174465|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|$]]

No solution worked for me until I've checked and set app Tests target to same provisioning profile as main app. Or if you are using automatic singing make sure you have same team selected in Tests target.

blocks|key|2988036|text|我花了一个小时来解决这个问题，终于找到了解决方法。事实证明，在ProjectTarget和ProjectTests中，开发团队是不同的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2988037|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 grappled with this issue for an hour, and finally found a fix. Turned out the Development Team was different in ProjectTarget and ProjectTests.

blocks|key|172059|text|上面所说的都是正确的，特别是由Bartłomiej+Semańczyk:重新检查开发人员中心和您的项目中的授权设置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|172060|我对Xcode9/+iOS+11的两点看法..|offset|length|style|BOLD|172061|如果您为NFC添加新的权限(仅对iOS11+/Xcode9有效)，并且您还有一个Xcode8项目，那么Xcode8将失败。|172062|因此，如果您使用具有相同基础代码(使用条件编译)的多个项目共享相同的非代码文件，请确保区分不同Xcode版本之间的授权文件。|172063|entityMap^0|0|2|L|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

All said above is correct, especially by Bartłomiej Semańczyk:
re-recheck entitlements settings in Dev Center AND in your project.

my two cents for Xcode 9/ iOS 11..

If You add new entitlements for NFC (valid only for iOS11 / Xcode 9) in your repo where you also have an Xcode 8 project, Xcode 8 WILL fail.

So in case you use multiple projects with the same base code (with conditional compilation) sharing the same non-code files, be SURE to differentiate entitlements files between different Xcode version.

blocks|key|172925|text|我在Xcode8.3.2中得到了一个类似的错误。在我的例子中，我发现从~/Library/MobileDevice/Provisioning+profiles中删除缓存的配置文件会使Xcode再次从开发人员门户下载正确的配置文件，此后它会第一次工作。希望这对其他人有帮助！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|172926|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 was getting a similar error in Xcode 8.3.2. In my case, I found that removing the cached provisioning profiles from ~/Library/MobileDevice/Provisioning Profiles made Xcode download the correct one from the Developer Portal again and thereafter it worked first time. Hope this helps someone else!

blocks|key|170837|text|对于那些在目标构建设置中自动预配配置文件时遇到相同问题的用户：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|170838|编辑目标授权文件时要非常小心！这可能会中断与自动生成的配置配置文件的对应关系，您将收到此错误。|offset|length|style|BOLD|170839|在我的例子中，我不得不在调试版本中临时使用iCloud生产容器。为此，我插入了|170840|<key>com.apple.developer.icloud-container-environment</key>
<string>Production</string>++|code-block|syntax|javascript|170841|在授权文件中，这是有效的！|170842|为了提醒我以后必须删除这些行，我又插入了以下注释：|170843|<key>TODO</key>
<string>The+entry+below+must+be+out+commented+or+deleted+to+use+the+iCloud+development+environment.</string>++|170844|这破坏了对应关系，并创建了错误。|170845|entityMap^0|0|0|1B|0|0|0|0|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]]|9|@]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|13|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|15|8|@]|9|@]|A|$]]|$1|S|3|T|5|L|7|16|8|@]|9|@]|A|$M|N]]|$1|U|3|V|5|6|7|17|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

For those who have the same problem with Provisioning Profile Automatic in the targets Build Settings: 

Be very careful when you edit your targets entitlements file! This might break the correspondence to the automatically generated provisioning profile, and you will get this error. 

In my case, I had to use temporarily the iCloud production containers with debug builds. To do so, I inserted 

<pre><code>&lt;key&gt;com.apple.developer.icloud-container-environment&lt;/key&gt;
&lt;string&gt;Production&lt;/string&gt; 
</code></pre>

in the entitlements file and this worked! 
To remind me that I had later to remove these lines, I further inserted simply the following comment: 

<pre><code>&lt;key&gt;TODO&lt;/key&gt;
&lt;string&gt;The entry below must be out commented or deleted to use the iCloud development environment.&lt;/string&gt; 
</code></pre>

And this broke the correspondence, and created the error.

blocks|key|174547|text|对于XCode+10，可能需要使用旧的构建系统|type|unstyled|depth|inlineStyleRanges|entityRanges|data|174548|可以从文件/项目设置中进行更改。ERROR+ITMS-90174:+"Missing+Provisioning+Profile+-+iOS+Apps+must+contain+a+provisioning+profile+in+a+file+named+embedded.mobileprovision."|offset|length|174549|科尔多瓦/离子公告：https://github.com/apache/cordova-ios/issues/407|174550|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/30972472/error-itms-90174-missing-provisioning-profile-ios-apps-must-contain-a-provis/52605878#52605878|1|https://github.com/apache/cordova-ios/issues/407^0|0|G|3T|0|0|A|1C|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

For XCode 10, one may need to use the legacy build system

Change can be made from File/Project Settings. <a href="https://stackoverflow.com/questions/30972472/error-itms-90174-missing-provisioning-profile-ios-apps-must-contain-a-provis/52605878#52605878">ERROR ITMS-90174: &quot;Missing Provisioning Profile - iOS Apps must contain a provisioning profile in a file named embedded.mobileprovision.&quot;</a>

A cordova / ionic annoucement: <a href="https://github.com/apache/cordova-ios/issues/407" rel="noreferrer">https://github.com/apache/cordova-ios/issues/407</a>

blocks|key|2988207|text|当我更新到Xcode10时，我遇到了类似的问题，我解决了这个问题，转到文件>项目设置，在“新构建系统”选项中选择“遗留构建系统”。这对我来说很有用，我希望这对某些人有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2988208|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 a similar issue when I updated to Xcode 10, I solved the issue going to File > Project Setting, in the "New Build System" option select "Legacy Build System". This made the trick for me, I hope this helps to someone.

blocks|key|2988222|text|我只是去了苹果开发门户网站，下载了适当的配置文件并重新安装(Xcode10.1)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2988223|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 simply went to apple dev portal, downloaded the appropriate provisioning profile and reinstalled it (xcode 10.1)

blocks|key|172168|text|如果这个问题，同样的me.You，可能忘记了在你的目标项目中设置团队单元测试，试着做这个图片|type|unstyled|depth|inlineStyleRanges|entityRanges|data|172169|​|172170|📷|atomic|offset|length|172171|172172|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/b1687487f130e96548378fd7926b011b.jpeg|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]]]]

If this problem same me.You maybe forget set team in unittest in your target project
try do this picture

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

blocks|key|2988269|text|这也可能是因为运行了错误的方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2988270|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 could be due running wrong scheme as well.

blocks|key|2775621|text|我正在我的应用程序中使用推送通知，在开发完成后，我正在尝试测试release+configuration的推送通知。在那时，我得到了这个错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2775622|我正在使用Production+Provisioning+Profile运行for+release。因此，我能够通过使用Adhoc+Provisioning+Profile来解决此错误。|2775623|entityMap^0|C|4|V|L|0|5|A|12|B|1O|5|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$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]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|I|$]]

I'm using Push notification in my app and after development completed i was try to test push notification for release configuration. At that time i got this error.

I was using Production Provisioning Profile to run for release. 
So i was able to solve this error by using Adhoc Provisioning Profile.

blocks|key|2988346|text|这可能是由于运行分发/发布方案造成的。将方案更改为debug对我来说是有效的。我们可以在这里检查方案。希望这对某些人有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2988347|​|2988348|📷|atomic|offset|length|2988349|2988350|2988351|2988352|2988353|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/912f8db160c548c4caf6a52da7470cd2.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/07e46790d52c2de5723fdd50c1bbb2c9.png^0|0|0|0|1|0|0|0|0|0|1|1|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|F|7|Z|8|@]|9|@$G|10|H|11|1|12]]|A|$]]|$1|I|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|J|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|K|3|E|5|F|7|15|8|@]|9|@$G|16|H|17|1|18]]|A|$]]|$1|L|3|C|5|6|7|19|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T|U|-4]]|V|$5|P|Q|R|A|$S|W|U|-4]]]]

This could be due to running distribution/release scheme. Changing the scheme to debug works for me. We can check the scheme here. Hope this helps someone. 

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

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

blocks|key|2988370|text|尽管这个问题看起来很容易解决，但我在更新iphone的ios版本时解决了这个问题。因为下投票而编辑:我看到的所有答案都只讨论xcode更新。这很奇怪，因为我的旧ios版本是iOS13.3.3，它可以在另一部iOS13.6的iphone上运行。在更新到iOS13.7之后，它工作了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2988371|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|$]]

Even if it could seems an easy fix, i solved it updating my iphone' s ios version.
EDIT because of downvote: all answers i have seen talk only about xcode update. It was strange because of my old ios version was ios 13.3.3 and it worked on another iphone with ios 13.6. After updating to ios 13.7 it worked.

blocks|key|2988386|text|有时来自xcode应用程序安装的错误消息可能会非常具有误导性，我已经多次对齐了授权，但根本原因并不是这样，而是因为我更改了证书，并且我的构建管道脚本使用了错误的证书SHA值：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2988387|/usr/bin/codesign+--force+--sign+701BB03735D5960C855D6E79223414F93F40065E+--entitlements+$workspace/xxx.app.xcent+--timestamp=none+$workspace/xxxx.app|code-block|syntax|javascript|2988388|就我的情况而言，我的授权文件没有问题，这是因为701BB03735D5960C855D6E79223414F93F40065E错误，但错误消息总是以The+executable+was+signed+with+invalid+entitlements格式打印出来。为了这个浪费了我一整天。|offset|length|style|CODE|2988389|entityMap^0|0|0|N|14|22|1F|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]|$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

The error message from xcode app installation sometime can be very misleading, I have aligned the entitlements many times, but the root cause is not because of that, it is because I have changed the certificate and my build pipeline script was using wrong certificate SHA value:
<pre><code>/usr/bin/codesign --force --sign 701BB03735D5960C855D6E79223414F93F40065E --entitlements $workspace/xxx.app.xcent --timestamp=none $workspace/xxxx.app
</code></pre>
for my case, nothing's wrong with my entitlement file, it is because <code>701BB03735D5960C855D6E79223414F93F40065E</code> is wrong, but the error message always print out as <code>The executable was signed with invalid entitlements</code>. Wasted my whole day for this.

blocks|key|174676|text|将我的目标设备从物理phone更改为模拟器为我解决了这个问题！|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|174677|entityMap^0|3|4|A|5|I|3|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|$]]

Changing my target device from my physical phone to a simulator fixed it for me!

I got this error with Xcode 5 when I try to run the app on my device.

<blockquote>
 The executable was signed with invalid entitlement
</blockquote>

It worked fine with Xcode 4.x. Anyone knows how to get rid of the error?

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

The executable gets signed with invalid entitlements in Xcode

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

当我尝试在我的设备上运行这个应用程序时，我在Xcode5上得到了这个错误。可执行文件的签名权限无效它在Xcode 4.x上工作得很好。有人知道如何消除这个错误吗？​​

问可执行文件在Xcode中使用无效的权利进行签名
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问可执行文件在Xcode中使用无效的权利进行签名EN