blocks|key|2994804|text|解决方案在于Xcode5中的新选项，即provisioning+profile。只需将项目目标的配置文件设置为正确的配置文件，它就会正常工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2994805|​|2994806|📷|atomic|offset|length|2994807|2994808|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/389ab84763089396bc1df6a7d6d817a1.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

The solution lies in the new option in Xcode 5 which says provisioning profile. Just set the project target's provisioning profile to the right one and it'll work.

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

blocks|key|2782728|text|如果你像我一样，你认为你尝试了EVERYTHING，存档你的项目超过十次，你的头撞在键盘上，仍然得到这个错误。请帮你自己一个忙，简单地重新启动XCode，它对我很有效。有时苹果公司。我讨厌你。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2782729|entityMap^0|F|A|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 you are like me and you think you tried EVERYTHING, archived your project over ten times, banged your head on the keyboard and still get this error. Please do yourself a favor and simply Restart XCode, it worked for me. Sometime Apple... I hate you.

blocks|key|176304|text|我经历了上面的许多步骤，但最终对我起作用的是在Xcode中刷新我的个人资料。不知道为什么有必要，因为我的应用程序的分发配置文件已经显示在列表中了。以下是步骤：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|176305|176306|Xcode+Preferences+|ordered-list-item|176307|Accounts选项卡|176308|选择您的苹果ID+|176309|在苹果ID详细信息面板|176310|点击左下角的刷新按钮|176311|176312|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|T|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|U|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|V|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|W|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

I went through many of the steps above but what finally worked for me was refreshing my profiles in Xcode. Not sure why it was necessary since my app's distribution profile was showing up in the list already. Here are the steps:

<ol>
<li>Xcode Preferences </li>
<li>Accounts tab</li>
<li>Select your Apple ID</li>
<li>Hit the View Details button in the Apple ID detail panel</li>
<li>Hit the Refresh button in the lower left corner</li>
</ol>

blocks|key|174506|text|在我的例子中，我在Xcode中激活了与在developer.apple.com中的应用程序服务中相同的功能。这对我很管用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|174507|​|174508|📷|atomic|offset|length|174509|174510|174511|174512|174513|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/b5744bcba4b38d3fd9110c3d93ab49e9.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/7f23ff127b986acf839bc4bfde65c5e4.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]]]]

In my case, i activated the same capabilities in Xcode that in Application services in developer.apple.com. Thats works for me

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

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

blocks|key|176521|text|在我的情况下(对不起)，我在->通用->标识中将"Team“切换为"None”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|176522|在另一种情况下，我需要将此身份从“无”切换到管理身份和配置文件的开发人员帐户。|176523|Xcode有时似乎会在代码签名方面搞得一团糟。或者，当然，我们这些凡人根本不够聪明，无法理解它在做什么。不要放弃，我们都时不时地经历一些代码签名的折磨！|176524|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|$]]

In my case (sorry) I switched "Team" to "None" in -> General -> Identity

In another case I needed to switch this identity from "None" to the developer account managing the identities and profiles.

Xcode sometimes messes up greatly with code signing, it seems. Or, we mere mortals simply aren't clever enough to understand what it is doing, of course. Don't give up, we're all going through some code signing torture at times!

blocks|key|2782319|text|在我的例子中，我必须为版本设置正确的配置文件，然后必须重新启动Xcode。在重新启动之前，它具有相同的配置文件，并且不起作用。因此，有时重启可以创造奇迹。也许这对某些人有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2782320|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, I had to set correct Provision Profile for Release, and then had to restart Xcode. Before restarting, it had same provision profile, and didn't work. So, sometimes a restart can do miracles. Maybe this helps somebody.

blocks|key|178024|text|如果有人使用GameCenter，那么在你的目标中检查这一部分。我使用了一些旧项目，有两个错误(但一切都很好)。禁用并重新启用它解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|178025|📷|atomic|offset|length|178026|​|178027|此操作很可能会将游戏中心权限添加到应用程序ID，并自行处理它。|178028|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/7183dca2641568641644ec427a4859ed.png|imageAlt^0|0|0|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|U|8|@]|9|@$E|V|F|W|1|X]]|A|$]]|$1|G|3|H|5|6|7|Y|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R|S|-4]]]]

If someone uses a GameCenter then check this section in your target. I worked with some old project and there were 2 errors (but everything worked fine). Disabling and enabling it back solved this problem.<img src="https://i.stack.imgur.com/8J0ww.png" alt="enter image description here">

Most likely this action adds Game Center entitlement to App ID and and handle it itself.

blocks|key|178398|text|1.转到项目文件夹，删除*.entitlements文件。2.然后转到xcode项目目标->构建设置->代码签名授权-删除值3.清理4.运行|type|unstyled|depth|inlineStyleRanges|entityRanges|data|178399|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|$]]

1.Go to project folder, delete *.entitlements files. 
2.Then go yo in xcode project target -> build settings -> code signing entitlements - delete values
3.Clean
4.Run

blocks|key|175906|text|啊，这个光荣的错误。对于我来说，每当我看到这个错误时，我都会检查以下内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|175907|1.允许XCode始终访问您的预配配置文件信息-如果XCode不断询问您何时启动它才能访问您计算机的私有文件，以便它可以获得预配配置文件信息，并且可以选择始终允许访问、现在不允许访问或只允许一次访问-请将其设置为始终允许访问|offset|length|style|BOLD|175908|2.如果您的项目中有任何旧的授权文件，请将其删除，并将其标记为-如果您在项目中看到一个.entitlements文件将其删除(或者，如果您不确定是否准备彻底删除它，则至少删除对它的引用)，然后确保构建设置中“代码签名”部分下的“代码签名授权”行为空|175909|3.在线检查您的应用程序服务并将其与应用程序的XCode中的服务进行匹配-转到苹果会员中心并检查您的应用程序的应用程序ID，单击应用程序查看应用程序服务并查看您选中的内容，然后转到XCode并检查您的‘功能’部分以确保这两个应用程序上的苹果服务列表相同|175910|4.确保在验证之前为你的应用程序分配了有效的配置文件-在苹果会员中心仔细检查你的应用程序的配置文件，确保其未过期，具有正确的应用程序ID和正确的捆绑包id和分发。下载并单击新的配置配置文件以确保XCode具有该配置文件，或者转到XCode+>首选项>帐户>单击您的帐户并查看详细信息，然后单击下角按钮以将所有配置文件同步到XCode。您现在应该可以在“Code+Signing”部分中选择配置文件。一旦您拥有正确的配给配置文件，您就可以将“Code+Signing+Identity”行设置为该配给配置文件的正确选项。|175911|注意-如果要进行分发证书，将所有“Code+Signing+identity”行设置为您用于分发的标识(包括调试行)会有所帮助|175912|5.如果其他方法都失败了--清理项目并重新启动XCode，下次打开项目并尝试验证时，一些苹果魔法可能会很好地工作|175913|entityMap^0|0|0|N|0|0|V|0|0|M|0|0|7|0|0|0|14|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@$D|V|E|W|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@$D|11|E|12|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@$D|14|E|15|F|G]]|9|@]|A|$]]|$1|N|3|O|5|6|7|16|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|17|8|@$D|18|E|19|F|G]]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|S|$]]

Ah, this glorious error. For me whenever I see this error I check the following things:

1. Allow XCode to access your provisioning profile info all the time - If XCode keeps asking when you start it up to have access to your computer's private files so that it can get provisioning profile information with the options to allow access always, not now, or just one time - set it to ALWAYS ALLOW access

2. If you have any old entitlement files kicking around your project get rid of them and any sign of them - if you see a .entitlements file in your project delete it (or at least remove the reference to it if you aren't sure you are ready to outright delete it), then make sure the 'Code Signing Entitlements' line under the 'Code Signing' section in Build Settings is empty

3. Check your Application Services online and match them up with your Services in XCode for the app - Go to the Apple Member Center and check the App ID for your app, click on the app to see its 'Application Services' and see what you have checked, then go to XCode and check your 'Capabilities' section to make sure the two have the same list of Apple services on both

4. Make sure you assign a valid Provisioning Profile to your app before validating - double check your provisioning profile for your app in the Apple Member Center, make sure it isn't expired, has the right App ID with the correct bundle id and distribution. Download and click on the new provisioning profile to make sure XCode has it, or go to XCode > Preferences > Accounts > click on your account and 'View Details' then click the bottom corner button to Sync all the profiles to XCode. You should have the profile available to select now in the 'Code Signing' section. Once you have the correct provisioning profile then you can set the 'Code Signing Identity' lines to the correct option for that provisioning profile.

Note - if doing a distribution certificate it can help to set all the 'Code Signing Identity' lines to the identity you use for distribution including the debug lines

5. IF ALL ELSE FAILS - Clean your project and Restart XCode and some Apple magic may just work fine the next time you open your project and try to Validate

blocks|key|2782386|text|如果你正在构建一个旧的3.1.5项目，Xcode5有一些错误，不幸的是，这使得本杰明的回答是不可能的，因为没有配置配置文件可供选择。在对Xcode项目文件痛苦地阅读了很长时间后，我想出了这个对我有效的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2782387|2782388|实用程序窗格(右侧)在Xcode5的项目文档下，从Xcode3.1-compatible更改为Xcode3.2+compatible.|unordered-list-item|2782389|Enter您的组织名称。|2782390|关闭项目。|2782391|打开您的项目文件，例如open+-a+TextEdit+path/to/name.xcodeproj/project.pbxproj+|offset|length|style|CODE|2782392|删除buildConfiguration中的两行分发子句(一行在D14中，一行在D15中|2782393|2782394|2782395|​|2782396|现在你准备好重新打开，存档并提交到应用商店-瞧！它又能工作了！|2782397|我认为它是如何工作的|2782398|我认为这是可行的，因为苹果决定放弃任何单独的发行版配置，这是一件好事。当我归档时，Xcode会自动对signs进行编码以进行分发。这是它一开始就应该实现的方式，苹果不能让自动迁移成为IDE的一部分，这是一种遗憾；相反，他们迫使我们开发人员花费数十年的时间来实现这一功能。|2782399|entityMap^0|0|0|0|0|0|B|1J|1|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|15|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|16|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|17|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|18|8|@$L|19|M|1A|N|O]]|9|@]|A|$]]|$1|P|3|Q|5|E|7|1B|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1E|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1F|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1G|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1H|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|12|$]]

If you're building an old 3.1.5 project, Xcode 5 has some bugs which unfortunately makes Benjamin's answer impossible, as there are no Provisioning profiles to pick from. After many a late hour of tormented reading of Xcode project files I came up with this solution that worked for me:

<ul>
<li>In the Utilities pane (to the right) in Xcode 5, under project Document, change from Xcode 3.1-compatible to Xcode 3.2 compatible.</li>
<li>Enter your organization name.</li>
<li>Close project.</li>
<li>Open your project file, e.g. <code>open -a TextEdit path/to/name.xcodeproj/project.pbxproj</code>
<ul>
<li>Remove the two Distribution clauses (<code>isa=XCBuildConfiguration</code>).</li>
<li>Remove the two accompanying lines in buildConfiguration (one in <code>PBXNativeTarget</code> and one in <code>PBXProject</code> <code>XCConfigurationLists</code>)</li>
</ul></li>
</ul>

Now you're ready to re-open, archive and submit to App store - voilà! It works again!

<h3>How I think it works</h3>

I assume this works because Apple somewhere along the line decided to drop the need for any separate distribution config, which is a good thing. When I archive, Xcode automatically code signs for distribution. That's the way it should have been implemented in the first place, it's just a shame that Apple can't make auto-migration part of the IDE; instead they force us developers to spend man-decades to make this stuff work.

blocks|key|178106|text|我已经在这个问题上挣扎了一天多，尝试了这里和互联网上其他地方提出的各种解决方案。什么都不管用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|178107|但是，我终于设法解决了这个问题！|178108|我遇到的问题是一个我三年多没碰过的旧应用程序，现在我要发布一个期待已久的更新。自从我发布这款应用以来，苹果一直在更新证书和应用Id的工作方式。他们引入了团队Id的概念，这似乎是推荐使用的。特别是，苹果的“证书，标识符和档案”网站，从那时起就有了很大的变化。|178109|在那里，我意识到我用于App+Store+Distribution的配置配置文件连接到了应用程序Id+ED8xxxxxxx.com.rostsolutions.*，但是查看我即将提交的游戏的应用程序Id时，我注意到应用程序Id是ATMxxxxxxx.com.rostsolutions.Swisch。所以App+Id前缀不匹配！这似乎是问题的根源。因此，我所做的是创建一个连接到应用程序Id+ATMxxxxxxx.com.rostsolutions.Swisch的新配置文件。使用这个配置配置文件，我成功地将我的应用程序提交到了app+Store，现在我只能祈祷其他一切都能在Apple这边正常工作。|offset|length|style|CODE|178110|(我首先尝试将新的配置配置文件连接到通配符Id+ATMxxxxxxx.com.rostsolutions.*，但似乎不起作用)。|178111|但令我困惑的是，当我在iTunes连接中查看旧的应用程序并转到二进制详细信息时，它显示应用程序Id是ED8xxxxxxx.com.rostsolutions.Swisch。那么为什么“证书、标识符和配置文件”页面列出的应用程序Id是ATMxxxxxxx.com.rostsolutions.Swisch呢？|178112|entityMap^0|0|0|0|1F|U|36|Z|5G|Z|0|O|U|0|1E|Z|38|Z|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|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@$H|V|I|W|J|K]|$H|X|I|Y|J|K]|$H|Z|I|10|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|11|8|@$H|12|I|13|J|K]]|9|@]|A|$]]|$1|N|3|O|5|6|7|14|8|@$H|15|I|16|J|K]|$H|17|I|18|J|K]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|Q|$]]

I have been struggling with this problem for more than a day now, trying all kinds of solutions suggested here and elsewhere on the internet. Nothing worked...

But, I finally managed to solve the problem!

The problem I had was with an old app that I haven't touched in over 3 years, and now I was about to release a long awaited update. Since the time I released the app, Apple has been updating how the certificates and App Id works. They have introduced the concept of Team Id which seems to be recommended to use.
In particular, the Apple's "Certificates, Identifiers &amp; Profiles" site, has seen a lot of changes since then.

There I realized that the Provisioning Profile I was using for App Store Distribution were connected to the App Id <code>ED8xxxxxxx.com.rostsolutions.*</code> but looking at the App Id for the game I was about to submit I notice that the App Id was <code>ATMxxxxxxx.com.rostsolutions.Swisch</code>. So the App Id prefix did not match!
That seemed to be the root of the problem. So what I did was to create a new Provisioning Profile connected to the App Id <code>ATMxxxxxxx.com.rostsolutions.Swisch</code> instead. Using that Provisioning Profile I successfully submitted my app to App Store and now I just keep my fingers crossed that everything else works fine at Apple's side.

(I first tried to connect to new Provisioning profile to the wildcard Id <code>ATMxxxxxxx.com.rostsolutions.*</code> instead, but that didn't seem to work).

But what puzzles me is that when I look at the old App in iTunes Connects and goes to Binary Details, it says that the App Id is <code>ED8xxxxxxx.com.rostsolutions.Swisch</code>. So why is the "Certificates, Identifiers &amp; Profiles" page listing the App Id as <code>ATMxxxxxxx.com.rostsolutions.Swisch</code>?

blocks|key|2995287|text|通过从Preferences->Accounts中删除我的Apple+ID，然后重新添加它，我的问题就解决了。然后，我的所有配置配置文件都会显示在View+Details实用程序面板上。我错误地选择了"Mac+Team+Provisioning+Profile:*“，而不是项目的实际发行版配置文件，因为我认为这是一个通用的选择。置备文件必须特定于项目。顺便说一句，请确保您的配置配置文件具有正确的授权(例如，地图)。我设法在没有授权的情况下发布了一个带有OSX+Maps的应用程序，Apple批准了它--但是没有Maps出现在生产版本上！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2995288|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|$]]

My problem was solved by removing my Apple ID from Preferences->Accounts and then adding it back again. Then all my provisioning profile files showed up on the View Details utility panel. I was mistakenly choosing "Mac Team Provisioning Profile:*" instead of the actual distribution provisioning profile for the project thinking that it was a generic selection. Provisioning files must be specific to the project. Oh, and BTW, make sure your provisioning profile has the correct entitlements (for example, Maps). I managed to release an app with OSX Maps without the entitlement and Apple approved it -- but no Maps showed up on the production version!

blocks|key|2994817|text|在我的案例中，我遇到了同样的问题，我的解决方案是在进行存档之前更改Build+Settings中的“Release+Provisioning+Profile”。我这样做了两次，一次是为了App+Store分发，另一次是为了Ad+Hoc分发。我还在我的档案上添加了一条评论。我的结论是，“存档重签名”中有一些东西被打破了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2994818|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, I had the same problem, my solution was to change the 'Release Provisioning Profile' in the Build Settings before doing Archive. I do this twice, once for App Store distribution, and another one for Ad Hoc distribution. I also add a comment on my archives. My conclusion is that there is something broken about the "archive re-signature".

blocks|key|175704|text|在this网站上有一个非常好的教程来解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|175705|它指出，当您的项目包标识符与您在iTunes+Connect+Website上输入的不同时，可能会出现此问题。|175706|entityMap|0|LINK|mutability|MUTABLE|url|http://anthonytietjen.blogspot.de/2012/08/overcoming-trouble-validating-your.html|1|http://itunesconnect.apple.com/^0|1|4|0|0|G|M|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]]]]

There is a very good tutorial for solving that problem on <a href="http://anthonytietjen.blogspot.de/2012/08/overcoming-trouble-validating-your.html" rel="nofollow">this</a> website.

It says that this problem can occur when your Projects Bundle Identifier is different to the one you entered on the <a href="http://itunesconnect.apple.com" rel="nofollow">iTunes Connect Website</a>.

blocks|key|2782833|text|我认为Xcode5使用的是"release“而不是您自己创建的”发行版“。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2782834|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 think xcode 5 uses "release" instead of "distribution" that you may created yourself.

blocks|key|2995474|text|如果所有这些都不起作用(在我的例子中，几天后就不行了，什么都试过了)，我只有一个Mac应用程序。在撤销时要小心！|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2995475|1)手动撤销所有"Mac+App+Distribution“和"Mac+Installer+Distribution”|2995476|2)清理密钥链中的相关证书和打开密钥(警告:删除前导出)|2995477|3)重启Xcode+4)进入(在Safari中)+developer.apple.com+->+certificates+etc.+5)在钥匙链中创建CertificateSigningRequest.certSigningRequest+->证书助手|2995478|6)使用您的*.certSigningRequest在developer.apple.com上手动创建"Mac应用程序分发版“和"Mac安装程序分发版”|2995479|7)+Provisioning+profile+->+Distribution+->创建/修复AppStore的自定义配置(我特别将其命名为"Mac+provision+profile->+AppStore“|2995480|8)+Xcode+->设置->+Account+->+Your+account+->刷新9)+Xcode清理->归档->验证|2995481|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/account/mac/certificate/certificateList.action^0|M|5|1C|8|0|0|J|6|0|P|14|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|14|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|15|8|@$9|16|A|17|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|18|8|@]|D|@$9|19|A|1A|1|1B]]|E|$]]|$1|L|3|M|5|6|7|1C|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1D|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1E|8|@]|D|@]|E|$]]|$1|R|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|S|$T|$5|U|V|W|E|$X|Y]]]]

If all above didn't work (in my case after couple of days no luck trying everything) I have only one Mac application. BE CAREFULL WITH REVOKE!

1) Revoke by hand all "Mac App Distribution" &amp; "Mac Installer Distribution" 
2) Clean relevant certificates and open-keys in Keychain (Warning: export before delete) 
3) Restart Xcode
4) Go to (in Safari) <a href="https://developer.apple.com/account/mac/certificate/certificateList.action" rel="nofollow">developer.apple.com -> certificates etc.</a>
5) Create CertificateSigningRequest.certSigningRequest in Keychain->Certificate assistant 
6) Create by hand on developer.apple.com both "Mac App Distribution" &amp; "Mac Installer Distribution" with your *.certSigningRequest 
7) Provisioning Profiles -> Distribution -> create/fix custom provision for AppStore (I'm specially named it as "Mac provision profile for AppStore" 
8) Xcode -> Settings -> Account -> Your account -> Refresh
9) Xcode Clean -> Archive -> Validate

blocks|key|2995530|text|我一直在为类似的问题而苦苦挣扎(我正在为Ad-Hoc发行版而构建)。自上次成功部署以来，唯一更改的是将两个设备添加到配置文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2995531|在两次和三次检查所有构建设置后，I重新生成了配置配置文件(没有更改任何内容)，重新下载，它工作正常。|offset|length|style|BOLD|2995532|因此，请注意:如果没有逻辑上的解释，你可以随时尝试好的旧的IT巫毒。|2995533|我还推荐使用iPhone+Configuration+Utility，尽管它名为iPhone+Configuration+Utility，但在检查您的计算机上有哪些配置配置文件时非常有用。|2995534|entityMap|0|LINK|mutability|MUTABLE|url|http://support.apple.com/kb/DL1465|1^0|0|G|C|0|0|6|S|0|14|S|1|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Z|8|@]|9|@$D|10|E|11|1|12]|$D|13|E|14|1|15]]|A|$]]|$1|L|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|S]]]]

I have been struggling with similar problem (I was building for Ad-Hoc distribution). Only thing that has changed since last successful deploy, was adding two devices to provisioning profile. 

After double- and triple- checking all build settings, I regenerated provisioning profile (without changing anything), re-downloaded and it worked fine.

So note to self: if there is no logic explanation, you can always try good old IT voodoo.

I also recommend <a href="http://support.apple.com/kb/DL1465" rel="nofollow" title="iPhone Configuration Utility">iPhone Configuration Utility</a>, which despite its name, is useful for checking what provisioning profiles you have on computer.

blocks|key|176586|text|错误ITMS-9000：“此捆绑包无效。提交到应用商店的新应用和应用更新必须使用公共(GM)版本的XCode+5.1.1或更高版本和iOS+7SDK构建。不要提交使用测试版软件构建的应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|176587|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|$]]

ERROR ITMS-9000: “This bundle is invalid. New apps and app updates submitted to the App Store must be built with public (GM) versions of XCode 5.1.1 or higher and iOS 7 SDK. Do not submit apps built with beta software.

blocks|key|175915|text|如果多个开发者使用同一个会员中心账号。其中一人无法使用其他人创建的证书，因为他们使用了使用自己的计算机创建的证书申请。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|175916|175917|您需要使用您创建的证书(使用您的计算机创建的证书请求)。|blockquote|175918|175919|175920|另一种选择，告诉他们给你发送开发人员资料。不确定是什么名字。若要使用在其他计算机上创建的证书，请执行以下操作。|175921|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|M|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|N|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|O|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|P|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Q|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|K|$]]

If multiple developers are using the same member center account. One of them can't use a certificate created by others cause they used a certificate request created using their computers.

<blockquote>
 You need to use a certificate created by you (certificate request
 created using your computer).
</blockquote>

Alternative, told them to send you the Developer Profile. not sure of the name. to use a certificate created on another computer.

blocks|key|175923|text|代码签名权限的发生是因为您的资源不包含资源中的权限文件，只需转到生成设置并搜索代码签名权限删除条目以进行调试和发布，再次生成项目您将看到没有错误。干杯|type|unstyled|depth|inlineStyleRanges|entityRanges|data|175924|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|$]]

Code signing Entitlements occur because of your resource does not contain Entitlements file in resources,Just go to build setting and search code signing Entitlements delete entry for debug and release, build project again you will see there is no error. Cheers

blocks|key|2995549|text|我也有同样的问题，但是这里写的东西对我来说都不起作用。然而，我发现了一种对我有效的简单方法。下面是如何做的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2995550|1)在您的项目和目标构建设置中，为所有预配配置文件选择“无”，并为所有代码签名标识选择“不要代码签名”。|2995551|2)现在，选择您的Target并转到build+settings。在代码签名标识发布设置中，对“任意iOS+iOS”选择"iOS分发“。然后，在Provisioning+Profile+Release+setting中，为"Any+iOS+SDK“选择您的分发配置文件。在此之后，您的代码签名标识发布设置应自动更改为"iPhone分发“。|2995552|3)存档您的构建并验证。现在它应该可以正常工作了。就这样!|2995553|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|$]]

I had the same problem, but nothing written here worked for me. However, I found a simple way that worked for me. Here's how to do it:

1) In your Project and your Target(s) build settings, choose "None" for all Provisioning profiles, and choose "Don't Code Sign" for all Code Signing Identities.

2) Now, choose your Target and go to build settings. In Code Signing Identity Release setting, choose "iOS Distribution" for "Any iOS SDK". And then, in Provisioning Profile Release setting, choose your distribution profile for "Any iOS SDK". After that your Code Signing Identity Release setting should automatically change to "iPhone Distribution".

3) Archive your build and validate. Now it should work fine. That's it!

I've build a new application which is going to support IOS 7. I got the new XCode 5 GM and tried to sign my apps using my fresh provisioning profile and distribution certificate, but i'm having trouble with distribution. I constantly get the following error:

<blockquote>
 "Invalid Code Signing Entitlements. The entitlements in your app
 bundle signature do not match the ones that are contained in the
 provisioning profile. According to the provisioning profile, the
 bundle contains a key value that is not allowed:
 '[XXXX.com.sample.company ]' for the key 'keychain-access-groups".
</blockquote>

Also the same error for a key value called <code>application-identifier</code>.

Screenshot of the errror: 

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

Xcode 5: Code signing entitlement errors

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我已经构建了一个新的应用程序来支持iOS7。我得到了新的XCode 5 GM，并试图使用我的新配置文件和分发证书来签署我的应用程序，但我在分发方面遇到了问题。我经常收到以下错误：“无效的代码签名权利。应用程序捆绑包签名中的权利与设置配置文件中包含的权利不匹配。根据设置配置文件，捆绑包包含不允许的密钥值:密钥”“keychain-access-groups”“的”“XXXX.com.sample.c

问Xcode 5:代码签名授权错误
EN

回答 21

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Xcode 5:代码签名授权错误EN

回答 21

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Xcode 5:代码签名授权错误
EN