blocks|key|149195|text|我也搞不懂这一点--在提交给AppStore时，它默认使用通配符配置文件，这让我吃了一惊。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|149196|我最终在Xcode6中构建，然后返回到Xcode5的组织窗口进行提交。这样的话，它会提示你选择一个配置文件来登录。|149197|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I couldn't figure this out either - got bit by it when submitting to the AppStore, where it defaulted to a wildcard profile.

I ended up building in Xcode 6, then going back to Xcode 5's Organizer window for the submission. That way it'll prompt you to pick a profile to sign with.

blocks|key|153308|text|在提交到App+Store时，我遇到了类似的问题。我创建了一个归档文件，然后单击“提交”，Xcode希望自动使用默认的“xccom.*”通配符配置文件进行签名，而不是使用已有的显式配置文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|153309|为了解决这个问题，我刚刚在Apple开发者门户上重新生成了这个配置文件：|153310|1)转到developer.apple.com并找到您要使用的分发设置配置文件。|153311|2)选中，点击[编辑]，重命名配置文件，点击[生成]。|153312|3)将配置配置文件下载到桌面，并将其拖到Xcode+6图标上。|153313|4)重启Xcode+6。|153314|5)打开管理器窗口，在您创建的归档文件上单击[提交]。Xcode将自动选择您的显式配置文件，而不是通用配置文件。|153315|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|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|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 a similar issue when submitting to The App Store. I created an archive, then clicked "submit" and Xcode wanted to automatically sign with the default "XC com.*" wildcard provisioning profile instead of the explicit profile that already had.

To fix this, I just re-generated the profile on the Apple Developer Portal:

1) Go to developer.apple.com and find the distribution provisioning profile you want to use. 
2) Select it, click "Edit", re-name the profile, and click "Generate". 
3) Download the provisioning profile to the Desktop and drag it onto the Xcode 6 icon. 
4) Re-start Xcode 6. 
5) Open the organizer window and click "Submit" on the archive you built. Xcode will automatically pick your explicit profile instead of the generic one.

blocks|key|2946256|text|这对我来说很管用：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2946257|2946258|单击“查看帐户..”在"..select+a+Development+Team..“对话框。|ordered-list-item|2946259|单击“查看详细信息..”然后找到XC即席配置文件。苹果右键单击该配置文件并选择"Show+in+Finder".|2946260|delete+selected+profile。|2946261|返回到步骤1中的对话框。|2946262|单击配置文件旁边的箭头以打开配置文件，再次打开通用配置文件，如步骤4所示。|2946263|从"Send+application+name+to+|2946264|：“对话框中单击"Previous”按钮。|2946265|再次选择"Save+for+Ad+Hoc+Deployment“|2946266|再次单击"choose”按钮。|2946267|2946268|现在，您应该会看到正确的配置配置文件名称。|2946269|entityMap^0|0|9|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|17|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|18|8|@]|D|@]|E|$]]|$1|J|3|K|5|I|7|19|8|@]|D|@]|E|$]]|$1|L|3|M|5|I|7|1A|8|@]|D|@]|E|$]]|$1|N|3|O|5|I|7|1B|8|@]|D|@]|E|$]]|$1|P|3|Q|5|I|7|1C|8|@]|D|@]|E|$]]|$1|R|3|S|5|I|7|1D|8|@]|D|@]|E|$]]|$1|T|3|U|5|I|7|1E|8|@]|D|@]|E|$]]|$1|V|3|W|5|I|7|1F|8|@]|D|@]|E|$]]|$1|X|3|Y|5|I|7|1G|8|@]|D|@]|E|$]]|$1|Z|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]|$1|10|3|11|5|6|7|1I|8|@]|D|@]|E|$]]|$1|12|3|-4|5|6|7|1J|8|@]|D|@]|E|$]]]|13|$]]

This worked for me:

<ol>
<li>click "View Accounts.." within the "..select a Development Team.."
dialog.</li>
<li>click "View Details.." and find the XC Ad Hoc provisioning profile.</li>
<li>right click on that profile and chose "Show in Finder".</li>
<li>delete the selected profile.</li>
<li>go back to the dialog in step 1.</li>
<li>click "Chose".</li>
<li>click the arrow near provisioning profile to open the provisioning
profiles directory.</li>
<li>delete again the generic profile like in step 4.</li>
<li>click "Previous" button from the "Send [application name] to Apple:" dialog. </li>
<li>select again "Save for Ad Hoc Deployment" </li>
<li>click again the "choose" button.</li>
</ol>

now you should see the right provisioning profile name.

blocks|key|152078|text|实际上，您需要创建一个新的分发配置文件，专门用于Ad+Hoc部署。这可以在经典的会员中心找到，但它是一种新类型的证书。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|152079|然后，你可以选择哪些设备可以用来测试应用程序，就像你对开发人员配置文件所做的那样。|152080|新创建的证书将在您按常规方式从管理器导出您的包时可用。|152081|或者，您可以在iOS+8中使用苹果提供的TestFlight解决方案，以使您的用户能够访问预发布。|152082|​|152083|📷|atomic|offset|length|152084|152085|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/db19f76158023994a85c75e4d93ba2e4.png|imageAlt^0|0|0|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|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|11|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|13|8|@]|9|@$M|14|N|15|1|16]]|A|$]]|$1|O|3|I|5|6|7|17|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W|X|-4]]]]

In fact, you need to create a new Distribution profile, specific for Ad Hoc Deployment. This can be found in the classic member center, but it is a new type of certificate.

You can then select which devices can be used to test the app as ou would do with a developer profile.

And the newly created certificate will be available when you export your package from the Organizer the usual way.

Alternatively you can use the TestFlight solution provided by Apple with iOS 8 to enable your user to have access to prerelease.

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

blocks|key|2946314|text|似乎最后生成的配给配置文件现在成功了。所以你只需要重新生成你想要的配置文件，然后下载它，Xcode就可以使用它了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2946315|一种稍微好一点的方法:在目标中设置所需的prov配置文件，并使用命令行来构建ipa，这也是可行的。|2946316|下面是我正在使用的脚本：|2946317|#!/bin/sh

#+Current+as+working+as+of+2014/09/22
#+Xcode+6

OUTPUTDIR="$HOME/build"
APPNAME="your-app"
SCHEME="your-app"
APP_WORKSPACE="$HOME/Path/To/your-app.xcworkspace"

rm+"$OUTPUTDIR/$APPNAME.ipa"+#deletes+previous+ipa
xcodebuild+-workspace+"$APP_WORKSPACE"+-scheme+"$SCHEME"+archive+-archivePath+"$OUTPUTDIR/$APPNAME.xcarchive"
xcodebuild+-exportArchive+-exportFormat+ipa+-archivePath+"$OUTPUTDIR/$APPNAME.xcarchive"+-exportPath+"$OUTPUTDIR/$APPNAME.ipa"+|code-block|syntax|javascript|2946318|和我的设置：|2946319|​|2946320|📷|atomic|offset|length|2946321|2946322|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/60e6dcdbbf25152bb7d1b617b204adaf.png|imageAlt^0|0|0|0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|15|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|16|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|17|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|18|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|19|8|@]|9|@$R|1A|S|1B|1|1C]]|A|$]]|$1|T|3|N|5|6|7|1D|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11|12|-4]]]]

It seems the last generated provisioning profile wins right now. So you can just re-generate the profile you want and download it and Xcode will use it.

A slightly better approach: set the desired prov profile in your target and use the command line to build your ipa, that works, too.

Here is the script, I'm using:

<pre><code>#!/bin/sh

# Current as working as of 2014/09/22
# Xcode 6

OUTPUTDIR="$HOME/build"
APPNAME="your-app"
SCHEME="your-app"
APP_WORKSPACE="$HOME/Path/To/your-app.xcworkspace"

rm "$OUTPUTDIR/$APPNAME.ipa" #deletes previous ipa
xcodebuild -workspace "$APP_WORKSPACE" -scheme "$SCHEME" archive -archivePath "$OUTPUTDIR/$APPNAME.xcarchive"
xcodebuild -exportArchive -exportFormat ipa -archivePath "$OUTPUTDIR/$APPNAME.xcarchive" -exportPath "$OUTPUTDIR/$APPNAME.ipa" 
</code></pre>

and my settings:

<img src="https://i.stack.imgur.com/kRbpL.png" alt="Xcode settings">

blocks|key|2733688|text|我有一个适用于我的变通方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2733689|我安装了Xcode6和Xcode5.1.1，Xcode6在应用程序中，Xcode5.1.1在另一个目录中。当我想进行构建时，我使用Xcode6来创建Archive。但是您还可以在Xcode5.1.1中看到创建的归档文件，因此我使用Xcode5.1.1通过我想使用的配置文件分发Ad+Hoc+.ipa。所以使用Xcode6构建，但使用Xcode5.1.1发布。|2733690|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I have a workaround for this that works for me.

I have both Xcode 6 and Xcode 5.1.1 installed, Xcode 6 is in Applications and Xcode 5.1.1 is in another directory. When I want to do a build I use Xcode 6 to create the Archive. But you can also see the created Archive in Xcode 5.1.1 so I use Xcode 5.1.1 to distribute the Ad Hoc .ipa using the provisioning profile that I want to use. So build using Xcode 6 but distribute using Xcode 5.1.1.

blocks|key|150649|text|我也遇到了同样的问题，使用命令行"xcodebuild“工具脚本解决了这个问题，这个脚本是随Xcode6预先安装的(不需要重新安装Xcode5)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|150650|http://www.thecave.com/2014/09/16/using-xcodebuild-to-export-a-ipa-from-an-archive/|offset|length|150651|终端中的脚本：|150652|xcodebuild+-exportArchive+-archivePath+$projectname.xcarchive+-exportPath+$projectname+-exportFormat+ipa+-exportProvisioningProfile+'Provisioning+Profile+Name'|code-block|syntax|javascript|150653|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|2B|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@$D|V|E|W|1|X]]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|Z|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|C]]]]

I was facing same issue, resolved using command line "xcodebuild" tool script, which is preinstalled with Xcode 6 (didn't need to re-install Xcode 5).

<a href="http://www.thecave.com/2014/09/16/using-xcodebuild-to-export-a-ipa-from-an-archive/" rel="nofollow noreferrer">http://www.thecave.com/2014/09/16/using-xcodebuild-to-export-a-ipa-from-an-archive/</a>

Script in terminal:

<pre><code>xcodebuild -exportArchive -archivePath $projectname.xcarchive -exportPath $projectname -exportFormat ipa -exportProvisioningProfile 'Provisioning Profile Name'
</code></pre>

blocks|key|150661|text|我有同样的问题，最后我解决了它重新生成我想在Xcode6中使用的配置文件，包括我在我的iOS开发人员帐户上注册的所有设备，这样做，当选择导出时，它显示正确的配置文件，我可以使用Xcode6进行即席导出，而不需要使用脚本。希望能有所帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|150662|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same problem, finally I solved it regenerating the profile that I wanted to use in Xcode 6 including all the devices that I have registered on my iOS Dev account, doing it that way, when selecting export it shows the correct profile and I can do the Ad Hoc export with Xcode 6 without using a script. Hope it helps.

blocks|key|2733737|text|在Xcode+6(我现在使用的最低6.1版本)中，当你为ad+hoc导出时，xcode+6会自动扫描是否有任何配置配置文件包含在开发人员帐户中注册的所有设备，同时匹配捆绑包ID。如果没有，它将使用XC配置文件。因此，如果你想使用你自己的配置文件，例如，为了推送通知的目的，你需要在苹果开发者门户上选择你配置文件中的所有设备。我想这就是为什么有些人可以重新创建个人资料，而有些人不能。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2733738|顺便说一句，使用脚本可以导出和上传到testflight，但设备就是无法下载它。可能是我弄错了。如果有人知道为什么，请让我知道。tks|2733739|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|$]]

In Xcode 6 (at least 6.1 I am using now)when you are doing the export for ad hoc, xcode 6 will automatically scan if there is any provisioning profile contains all devices registered in the developer account and at the same time match the bundle ID. If no, it will use XC provision profile. Therefore, if you want to use your own profile, for example, for the purpose of push notification, you will need to select all devices in your profile on apple developer portal. I guess that's the reason why some people recreate profile would work and some wouldn't.

btw,use script can export and upload to testflight, but device just can't download it. probably somewhere I got wrong. if anyone knows why it is, pls let me know. tks

blocks|key|153474|text|对于您的特定问题，没有办法选择要使用的配置配置文件。你想做什么？(例如，您希望选择的配置文件允许什么，而自动生成的配置文件不允许？)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|153475|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 answer to your specific question, no there is no way to select the provisioning profile to be used. What are you attempting to do? (i.e. what does the profile that you want to select allow that the automatically generated one doesn't?)

blocks|key|153500|text|一旦您在组织者中|type|unstyled|depth|inlineStyleRanges|entityRanges|data|153501|153502|选择ad-hoc构建，然后单击"Export...."|unordered-list-item|153503|Select+"Save+for+Ad+Hoc+Deployment“和Next|153504|，而不是从下拉菜单中选择一个组织选择"Use+local+signing+asset”->选择|153505|导出并像以前一样保存.ipa。|153506|153507|当然，您需要生成、下载并安装ad-hoc配置文件。|153508|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|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

Once you are in Organizer

<ul>
<li>Select the ad-hoc build and click "Export...."</li>
<li>Select "Save for Ad Hoc Deployment" -> Next</li>
<li>Instead of selecting an organisation from the drop down select "Use local signing asset" -> Choose</li>
<li>Export and save .ipa as before.</li>
</ul>

Of course you need to have generated, downloaded and installed the ad-hoc provisioning profile.

blocks|key|2733813|text|我已经被这个问题困扰了一段时间，但是使用Crashlytics解决了这个问题，在你的Xcode项目的构建设置中使用选定的概要文件构建分布式。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2733814|希望对某些人有帮助。|2733815|entityMap|0|LINK|mutability|MUTABLE|url|https://try.crashlytics.com/^0|K|B|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

I've been stuck for a while with this ,, but using <a href="https://try.crashlytics.com/" rel="nofollow">Crashlytics</a> solved it , build distributed using the selected profile in the build settings of your Xcode project .

hope it helps somebody .

blocks|key|2733848|text|几乎同样的问题。创建用于分发的归档文件(产品>归档)后，导出该归档文件(单击导出...)然后选择"Save+for+Enterprise+Deployment“，然后选择"Next”。然后选择“开发团队”默认值(例如，组织名称)并单击“选择”。最后，您将看到一个摘要视图，其中还列出了Xcode自动为您找到(可能是动态创建的)的配置概要文件。这可能是错误的配置文件(通常是通配符配置文件，如"XC：*")，可能是因为开发人员门户上已经有一个通配符配置文件。通配符配置文件可能会被其他较旧的项目使用，因此从开发人员门户中删除通配符配置文件可能不是明智之举。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2733849|我对此使用了支持票证，并且只得到了https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/ConfiguringPushNotifications/ConfiguringPushNotifications.html#//apple_ref/doc/uid/TP40012582-CH32-SW1的这个链接。帮不了什么大忙。|offset|length|2733850|我发现MrPatol的解决方案也适用于企业部署，并为我们解决了这个问题。我首先登录到开发人员门户，手动创建了一个适合我的应用程序的配置文件。然后下载并安装了新的手动创建的配置文件。|style|BOLD|2733851|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/ConfiguringPushNotifications/ConfiguringPushNotifications.html#//apple_ref/doc/uid/TP40012582-CH32-SW1^0|0|H|5D|0|0|3|7|J|4|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|@$D|X|E|Y|H|I]|$D|Z|E|10|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

Almost the same problem. After creating an archive for distribution (Product > Archive) you export the archive (click Export...) and choose "Save for Enterprise Deployment"; then "Next". You then select the "Development Team" default (e.g. organisation name) and click "Choose". Finally you will be presented with a summary view that also lists the provisioning profile that Xcode automatically has found (maybe created on-the-fly) for you. This MIGHT be the wrong provisioning profile (typically a wildcard provisioning profile, like "XC: *") and MIGHT be happening because there already is a wildcard provisioning profile on the developer portal. The wildcard provisioning profile MIGHT be used by other older project and maybe it is not wise to just remove the wildcard provisioning profile from the developer portal.

I used a support ticket for this and only got this link back <a href="https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/ConfiguringPushNotifications/ConfiguringPushNotifications.html#//apple_ref/doc/uid/TP40012582-CH32-SW1" rel="nofollow">https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/ConfiguringPushNotifications/ConfiguringPushNotifications.html#//apple_ref/doc/uid/TP40012582-CH32-SW1</a>. Not really a big help.

I have found that MrPatol's solution also works for Enterprise Deployment as well and solves the problem for us. I first logged into the developer portal and manually create a provisioning profile that suited my app. Then downloaded and installed the new manually created provisioning profile.

blocks|key|153521|text|这里有两个关键点为我解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|153522|153523|生成调配配置文件时，需要将其链接到使用与您的应用程序相同的捆绑标识符的显式应用程序ID。通配符App+ID将不起作用。|unordered-list-item|offset|length|style|BOLD|153524|导出应用程序以进行临时部署时，请在下拉列表中选择Use+local+signing+asset，然后单击Choose。|153525|153526|然后，Xcode将通过将应用程序ID与应用程序的捆绑标识符进行匹配来找到正确的配置配置文件。|153527|entityMap^0|0|0|Z|8|0|O|N|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|@$F|T|G|U|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|V|8|@$F|W|G|X|H|I]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|P|$]]

Here are the two key points that solved the problem for me. 

<ul>
<li>When you generate the provisioning profile, it needs to be linked to an Explicit App ID that uses the same bundle identifier as your app. A wildcard App ID will not work. </li>
<li>When you export the app for ad-hoc deployment, select Use local signing asset in the dropdown and click Choose. </li>
</ul>

Xcode will then find the correct provisioning profile by matching up the App ID with the bundle identifier of the app.

blocks|key|2946582|text|@MrPatol的回答对我不起作用。我的Xcode+6.3.2工作场景|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2946583|成员中心的+->+iOS+Provisioning+Profiles|offset|length|style|BOLD|2946584|2946585|删除在您尝试构建应用程序时默认设置的预配配置文件(例如"XC...")。使用短名称创建临时设置配置文件(而不是生产配置文件)。|unordered-list-item|2946586|2946587|iPhone配置实用程序中的+->预配配置文件|2946588|2946589|删除相同的预配配置文件(例如"XC...")|2946590|2946591|Xcode+->+Organizer中的|2946592|2946593|选择即席构建，然后单击“导出...”。选择"Save+for+Ad+Hoc+Deployment“->+Next|2946594|从下拉列表中选择一个组织并检查您的新的ad-hoc+provisioning+profile是否已选中，然后像以前一样保存.ipa。|2946595|2946596|entityMap^0|0|5|T|0|0|0|0|E|9|0|0|0|0|0|0|0|1K|0|0|1U|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@$D|14|E|15|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|17|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|19|8|@$D|1A|E|1B|F|G]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|P|3|Q|5|K|7|1D|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1F|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|V|3|W|5|K|7|1H|8|@$D|1I|E|1J|F|G]]|9|@]|A|$]]|$1|X|3|Y|5|K|7|1K|8|@$D|1L|E|1M|F|G]]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|11|$]]

The answer from @MrPatol did not work for me.
My working scenario for Xcode 6.3.2

In Member Centre -> iOS Provisioning Profiles

<ul>
<li>Delete provisioning profile which was set by default when you were trying to build the app (e.g. "XC..."). Create an ad-hoc provisioning profile (not production) with a short name.</li>
</ul>

In iPhone Configuration Utility -> Provisioning Profiles

<ul>
<li>Delete the same provisioning profile (e.g. "XC...")</li>
</ul>

In Xcode -> Organizer

<ul>
<li>Select the ad-hoc build and click "Export...."
Select "Save for Ad Hoc Deployment" -> Next</li>
<li>Select an organisation from the drop down</li>
<li>Check that your new ad-hoc provisioning profile is selected automatically</li>
<li>Export and save .ipa as before.</li>
</ul>

blocks|key|153532|text|在Xcode7中，我不能通过|type|unstyled|depth|inlineStyleRanges|entityRanges|data|153533|Organizer+->上传到应用商店&+Organizer+->验证|153534|但我可以通过Organizer+->导出进行选择|offset|length|style|BOLD|153535|编辑：|153536|在导出即席应用程序后将应用程序上传到testFlight的应用程序商店引发了另一个讨论here的问题。因此，这两个问题的解决方案是一个。创建AppStore+provisioning，以便能够通过组织者挑选它，并通过上载到应用程序存储来利用testFlight。|153537|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/28998478/apple-testflight-upload-warning-itms-90191-missing-beta-reports-active-entitl^0|0|0|6|E|0|0|3|0|1W|1R|17|4|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@$F|Y|G|Z|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@$F|11|G|12|H|I]]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@$F|14|G|15|H|I]]|9|@$F|16|G|17|1|18]]|A|$]]|$1|N|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

In xcode 7, I couldn't be able to pick adhoc provisioning via 

Organizer -> Upload to App Store &amp; Organizer -> Validate

But I could choose via Organizer -> Export

Edited:

Uploading the app after exporting for adhoc to app store for testFlight caused another issue discussed <a href="https://stackoverflow.com/questions/28998478/apple-testflight-upload-warning-itms-90191-missing-beta-reports-active-entitl">here</a>. So, solution to both these problem is one. Create AppStore provisioning to be able to pick it via organizer and utilize testFlight by uploading to appstore.

blocks|key|2946647|text|在导出时使用本地签名资源为我解决了这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2946648|📷|atomic|offset|length|2946649|​|2946650|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/d6be0946c76ff0efbe34c8a21a6d9a95.png|imageAlt^0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|S|8|@]|9|@$E|T|F|U|1|V]]|A|$]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P|Q|-4]]]]

Using local signing assets while exporting solved the issue for me:<a href="https://i.stack.imgur.com/LBKzW.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/LBKzW.png" alt="enter image description here"></a>

blocks|key|149415|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|149416|我认为在Xcode7之后指定-exportOptionsPlist选项是正确的方式。无论您在项目设置中指定什么，它都会像在图形用户界面导出中那样选择正确的配置文件。|ordered-list-item|149417|149418|149419|+xcodebuild+-exportArchive+-archivePath+$Archive_Path+-exportPath+$LOCAL_PACKAGE_DIR+-exportOptionsPlist+$Export_Plist_Path|blockquote|149420|149421|149422|optionPlist文件是这样的，|149423|<dict>
++<key>teamID</key>
++++++++<string>MYTEAMID123</string>
++++++++<key>+teamID+</key>
++++++++<string>app-store</string>
++++++++<key>uploadSymbols</key>
++++++++<true/>
</dict>


<plist>|code-block|syntax|javascript|149424|app-store、企业、ad-hoc、开发是可选的|149425|149426|，但在执行上述操作后，您可能会遇到另一个错误。|149427|149428|149429|+Error+Domain=IDEDistributionErrorDomain+Code=14“未找到适用的设备。”UserInfo={找到适用于NSLocalizedDescription=No的设备。}|149430|149431|149432|这是一个红宝石的问题。尝试使用这个外壳脚本xcbuild-safe.sh|offset|length|style|CODE|149433|xcbuild-safe.sh+xxxxNormalOptionsInXcodebuild+bla...|149434|149435|等待片刻，另一个奇怪的错误出现。|149436|149437|未找到命令xcbuild-+|149438|+.sh:第62行:+shell_session_update：|149439|149440|149441|见鬼的shell_session_update是什么？让我们绕过它。只需在真正的xcodebuild+cmd之前定义一个函数，即在第60或61行。|149442|function+shell_session_update()+{+:;+}|149443|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/fastlane/fastlane/blob/master/gym/lib/assets/wrap_xcodebuild/xcbuild-safe.sh^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|L|F|L|F|0|0|0|0|0|0|0|0|0|0|3|K|0|0^^$0|@$1|2|3|-4|4|5|6|1W|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|1X|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|1Y|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|1Z|7|@]|8|@]|9|$]]|$1|F|3|G|4|H|6|20|7|@]|8|@]|9|$]]|$1|I|3|-4|4|5|6|21|7|@]|8|@]|9|$]]|$1|J|3|-4|4|5|6|22|7|@]|8|@]|9|$]]|$1|K|3|L|4|5|6|23|7|@]|8|@]|9|$]]|$1|M|3|N|4|O|6|24|7|@]|8|@]|9|$P|Q]]|$1|R|3|S|4|5|6|25|7|@]|8|@]|9|$]]|$1|T|3|-4|4|5|6|26|7|@]|8|@]|9|$]]|$1|U|3|V|4|C|6|27|7|@]|8|@]|9|$]]|$1|W|3|-4|4|5|6|28|7|@]|8|@]|9|$]]|$1|X|3|-4|4|5|6|29|7|@]|8|@]|9|$]]|$1|Y|3|Z|4|H|6|2A|7|@]|8|@]|9|$]]|$1|10|3|-4|4|5|6|2B|7|@]|8|@]|9|$]]|$1|11|3|-4|4|5|6|2C|7|@]|8|@]|9|$]]|$1|12|3|13|4|5|6|2D|7|@$14|2E|15|2F|16|17]]|8|@$14|2G|15|2H|1|2I]]|9|$]]|$1|18|3|19|4|O|6|2J|7|@]|8|@]|9|$P|Q]]|$1|1A|3|-4|4|5|6|2K|7|@]|8|@]|9|$]]|$1|1B|3|1C|4|C|6|2L|7|@]|8|@]|9|$]]|$1|1D|3|-4|4|5|6|2M|7|@]|8|@]|9|$]]|$1|1E|3|1F|4|5|6|2N|7|@]|8|@]|9|$]]|$1|1G|3|1H|4|H|6|2O|7|@]|8|@]|9|$]]|$1|1I|3|-4|4|5|6|2P|7|@]|8|@]|9|$]]|$1|1J|3|-4|4|5|6|2Q|7|@]|8|@]|9|$]]|$1|1K|3|1L|4|5|6|2R|7|@$14|2S|15|2T|16|17]]|8|@]|9|$]]|$1|1M|3|1N|4|O|6|2U|7|@]|8|@]|9|$P|Q]]|$1|1O|3|-4|4|5|6|2V|7|@]|8|@]|9|$]]]|1P|$1Q|$4|1R|1S|1T|9|$1U|1V]]]]

<ol>
<li>I think it's a right way to specify a -exportOptionsPlist option after Xcode 7. It will choose the right provision files like in the GUI export no matter what you specify in project setting.</li>
</ol>

<blockquote>
 xcodebuild -exportArchive -archivePath $Archive_Path -exportPath
 $LOCAL_PACKAGE_DIR -exportOptionsPlist $Export_Plist_Path
</blockquote>

optionPlist file is like this,





<pre><code>&lt;dict&gt;
 &lt;key&gt;teamID&lt;/key&gt;
 &lt;string&gt;MYTEAMID123&lt;/string&gt;
 &lt;key&gt; teamID &lt;/key&gt;
 &lt;string&gt;app-store&lt;/string&gt;
 &lt;key&gt;uploadSymbols&lt;/key&gt;
 &lt;true/&gt;
&lt;/dict&gt;


&lt;plist&gt;
</code></pre>

app-store, enterprise, ad-hoc, development are alternative

<ol start="2">
<li>But you may meet another error after above.</li>
</ol>

<blockquote>
 Error Domain=IDEDistributionErrorDomain Code=14 "No applicable
 devices found." UserInfo={NSLocalizedDescription=No applicable devices
 found.}
</blockquote>

It's a ruby problem. Try this shell script, <a href="https://github.com/fastlane/fastlane/blob/master/gym/lib/assets/wrap_xcodebuild/xcbuild-safe.sh" rel="nofollow noreferrer"><code>xcbuild-safe.sh</code></a>

<pre><code>xcbuild-safe.sh xxxxNormalOptionsInXcodebuild bla...
</code></pre>

<ol start="3">
<li>Wait for a moment, another strange error comes.</li>
</ol>

<blockquote>
 xcbuild-safe.sh: line 62: shell_session_update: command not found
</blockquote>

What's the hell <code>shell_session_update</code> ? Let us work around it. Just define a function before the real xcodebuild cmd, namely at the line 60 or 61. 

<pre><code>function shell_session_update() { :; }
</code></pre>

To distribute the app to our testers we use Xcode, which we do using the following process:

<ul>
<li>Archive application</li>
<li>Distribute for Ad-Hoc</li>
<li>Choose provisioning profile</li>
<li>Save the .ipa to a folder</li>
</ul>

But with Xcode 6, this workflow was changed a bit. I can still select the Ad-Hoc distribution option, but I cannot select the provisioning profile I want. This gives us no control over which signing certificate is used and the provisioning profile configuration (we use push notifications).

By default <code>iPhone distribution</code> signing identity is used and some kind of <code>XC Ad Hoc</code> provisioning profile is generated, which can be seen on image below:<img src="https://i.stack.imgur.com/4ssU0.png" alt="Exporting IPA">
If you click the arrow near provisioning profile, it opens the folder with provisioning profiles.

So my question is:

Is there any way in Xcode 6 to select the provisioning profile used with Ad Hoc distribution?

Thanks!

Xcode 6 - How to pick signing certificate/provisioning profile for Ad-Hoc distribution?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

为了将应用程序分发给我们的测试人员，我们使用Xcode，我们使用以下过程：适用于点对点的归档文件选择provisioning profile将.ipa保存到文件夹但是在Xcode6中，这个工作流程发生了一些变化。我仍然可以选择即席分发选项，但不能选择我想要的配给配置文件。这使我们无法控制使用哪个签名证书和配置文件配置(...

问Xcode 6-如何为点对点分发挑选签名证书/配置文件？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Xcode 6-如何为点对点分发挑选签名证书/配置文件？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Xcode 6-如何为点对点分发挑选签名证书/配置文件？
EN