Xcode连续集成配置文件错误

I am trying to setup continuous integration in Xcode 5 on Mavericks. If I have a bot do a new clean project build, it completes with no errors. If I have the bot do the build on my actual project, I get the following error:

我正在尝试在Mavericks上的Xcode 5中建立连续集成。如果我让一个机器人做一个新的干净的项目构建，它会在没有错误的情况下完成。如果我让机器人在我的实际项目上进行构建，我会得到以下错误:

No matching provisioning profile found: Your build settings specify a provisioning profile with the UUID “XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX”, however, no such provisioning profile was found. CodeSign error: code signing is required for product type 'Application' in SDK 'iOS 7.0'

没有找到匹配的配置文件:您的构建设置使用UUID“xxxxxxxx - xxxx - xxxx - xxxx - xxxxxxxxxxxxxxxx”指定配置文件，但是没有找到这样的配置文件。CodeSign错误:SDK中的“iOS 7.0”产品类型“应用”需要代码签名

If I pull latest source on the server machine and build/archive it on the server it works as expected. All expected certificates and public keys are included in keychain. I have tried to update all provisioning profile settings in the project and build target the scheme points at. Does anyone have any ideas how to resolve this error?

如果我在服务器机器上提取最新的源代码并在服务器上构建/存档，它将按照预期工作。所有期望的证书和公钥都包含在keychain中。我尝试更新项目中的所有配置配置文件设置，并构建方案所指向的目标。有人知道怎么解决这个错误吗?

EDIT: After cracking open the project file and looking at the UUID, from what I can tell the UUID for the provisioning file it can't find does exist. Perhaps this is some kind of permission issue with the build not having access to the profile or keychain certificate?

编辑:打开项目文件并查看UUID之后，我可以从UUID中得知它找不到的供应文件是否存在。也许这是由于构建无法访问概要文件或密钥链证书而产生的某种权限问题?

11 个解决方案

#1

I had the same problem and finally managed to make it work.

我遇到了同样的问题，最终成功地解决了这个问题。

First of all, I added my server to my developer team but I had the same error as you.

首先，我将我的服务器添加到开发团队中，但是我有和您一样的错误。

Then I copied my key from user keychain to system keychain as indicated here but it was still not enough.

然后我将我的密钥从用户密钥链复制到系统密钥链，如这里所示，但这还不够。

And finally, I copied the provisioning profiles from ~/Library/MobileDevice/Provisioning\ Profiles/ to /Library/MobileDevice/Provisioning\ Profiles/ (in fact I copied all the MobileDevice directory because it didn't exist).

最后，我从~/Library/MobileDevice/ provisioning profiles / to /Library/MobileDevice/ provisioning \ profiles /(实际上，我复制了所有MobileDevice目录，因为它不存在)。

And now, I have a working continuous integration giving me an ipa which I can download on my Mac or install over the air on my devices.

现在，我有了一个持续的集成，提供了一个ipa，我可以在Mac上下载或者在我的设备上安装。

I don't know why I had to do this, but I hope it will work for you too.

我不知道为什么我要这么做，但我希望它对你也有用。

#2

I had the same problem since switching to Xcode 5. My solution was different.

自从切换到Xcode 5后，我遇到了同样的问题。我的解决方案是不同的。

Since the error message said "Your build settings specify a provisioning profile with the UUID xxxxxx", I checked the file containing my build setting (myproject.xcodeproj/projecjt.pbxproj).

由于错误消息说“您的构建设置指定了UUID xxxxxx的配置文件”，所以我检查了包含我的构建设置的文件(myproject.xcodeproj/projecjt.pbxproj)。

There I found a line with exactly that UUID. After deleting the line (of course a made a backup of the file first), everything worked again.

在那里，我找到了一条与UUID相同的直线。删除了行之后(当然a首先备份了文件)，一切又恢复了正常。

#3

Hi I had the same issue and the problem was I had the certificates in my login keychain and the build script was looking in System keychain. I copied the certificate in system key chain also and now Xcode was able to use the provisioning profile for the build

你好，我有同样的问题，问题是我的登录密钥链中的证书，构建脚本正在系统密钥链中查找。我还复制了系统密钥链中的证书，现在Xcode能够使用构建的配置文件。

#4

after searching how to solve this problem , after spending 1 whole day in front of my keyboard , looking through all pages and ideas how to solve this i actually found something interesting out.

在搜索了如何解决这个问题之后，在我的键盘前花了整整一天的时间，浏览了所有的页面和想法之后，我发现了一些有趣的东西。

Something came on my mind mentioned (edit YOU_APP.xcodeproj). So I SOLVED THIS:

我想到了一件事(编辑YOU_APP.xcodeproj)。我解决了这个:

1. Go to your project folder
2. 进入你的项目文件夹
3. Right click on YOU_APP.xcodeproj and choose Show Package Contents
4. 右键单击YOU_APP。xcodeproj并选择Show Package Contents
5. Edit project.pbxproj with (for example TextMate2 or somethig like this)
6. 编辑项目。pbxproj与(例如TextMate2或类似的什么)
7. NOW Attention. I found everything where this UUID (wrong UUID) will be displayed and just replaced with my i created and have been using for several time. I replaced 13 times.
8. 现在的注意力。我找到了这个UUID(错误的uid)将显示的所有内容，并将其替换为我创建的，并已使用了好几次。我取代了13倍。
9. done. Just compile and thats it.
10. 完成了。只要编译就行了。

You will not believe but it worked after spending a lot of time. =)

你不会相信，但在花了很多时间之后，它确实奏效了。=)

#5

I kept searching the net for the past few weeks trying to establish Continuous Integration through Jenkins & when failed through OS X Server Bots, both failed with the same exact issue.

在过去的几周里，我一直在网上搜索，试图通过Jenkins建立持续集成，当通过OS X服务器机器人失败时，两者都以同样的问题失败。

Copying the Provisioning Profiles from "~/Library/MobileDevice/Provisioning Profiles/" to "/Library/MobileDevice/Provisioning Profiles/" was the only key.

将配置文件从“~/Library/MobileDevice/Provisioning Profiles/”复制到“/Library/MobileDevice/Provisioning Profiles/”是惟一的关键。

Just two points to take care off :-

只有两点要注意:-。

1-If you are using OS X Lion, take care that your ~/Library folder will not appear in Finder as it is set as invisible; Please refer to http://www.macworld.com/article/1161156/view_library_folder_in_lion.html to see it.

1-如果您正在使用OS X Lion，请注意您的~/Library文件夹不会出现在Finder中，因为它设置为不可见;请参考http://www.macworld.com/article/1161156/view_library_folder_in_lion.html查看。

2-Don't bring the provisioning profile on your own (e.g. download it from MemberCenter or so, ... ) just copy the profiles exiting in your ~/Library/...; their naming is different; they are all named by the UUID, e.g.3D19E524-9E2A-45C2-942C-F30AC3ACF0CC*.mobileprovision*

2-不要自己携带配置文件(例如，从MemberCenter或其他网站下载该配置文件，…)只需复制您的~/库/…他们的命名是不同的;它们都由uuuid命名，例如:g3d19e524-9e2a - 45c2 - 942c - f30ac3acf0cc *. mobile条款*

#6

I was getting the same error and none of the above answers worked for me. I referenced This blog and copied my provisioning profiles from the ~/Library/MobileDevice/Provisioning Profiles/ directory to the /Library/Server/Xcode/Data/ProvisioningProfiles directory and I still got the same error.

我也犯了同样的错误，上面的答案对我都不起作用。我引用了这个博客，并将我的配置文件从~/Library/MobileDevice/ provisioning profiles / directory复制到/Library/Server/Xcode/Data/ provisionprofiles目录，我仍然得到相同的错误。

So I opened Xcode and synchronized my profiles with the provisioning portal. If you are unfamiliar, go to Preferences -> Accounts -> , highlight the developer team and click "View Details". Then highlight the distribution code signing identity in "Signing Identities" and click on the refresh button in the bottom left corner. I did this from the server, however, I'm sure you could refresh your provisioning profiles on your development mac and then copy them to the server.

因此，我打开了Xcode并将配置文件与供应门户同步。如果您不熟悉的话，请到Preferences ->帐户->，突出显示开发团队，点击“查看细节”。然后在“签名标识”中突出显示分发代码签名标识，并单击左下角的refresh按钮。我在服务器上做了这个，但是我相信您可以在开发mac上刷新您的配置文件，然后将它们复制到服务器上。

This process refreshes the provisioning profiles in the ~/Library/MobileDevice/Provisioning Profiles/ directory. I then reattempted the copy process to /Library/Server/Xcode/Data/ProvisioningProfiles from ~/Library/MobileDevice/Provisioning Profiles/ and the Xcode bot successfully found the provisioning profile during the next integration.

这个过程刷新了~/库/移动设备/配置文件/目录中的配置文件。然后，我重新尝试将流程复制到/Library/Server/Xcode/Data/ provisionprofiles from ~/Library/MobileDevice/Provisioning Profiles/， Xcode bot在下一次集成期间成功地找到了供应配置文件。

As a note, I tried signing out of the Xcode service's developer team and signing back in and that peculiarly did not work for me. Theoretically that should accomplish the same thing.

作为一个说明，我尝试签出Xcode服务的开发团队，并签回，这对我来说是不合适的。从理论上讲，它应该完成同样的事情。

Like others have mentioned, I would copy all of the profiles rather than finding only the Ad Hoc profile you are looking for. The reason is that maybe, like in my case, the Xcode bot was attempting to archive with the development profile and "Development Profile" is much easier to debug than "4F96F173-7EBE-4892-B283-52489DE2F409".

像其他人提到的那样，我将复制所有的概要文件，而不是只查找您正在查找的临时概要文件。原因是，就像我的例子一样，Xcode bot试图用开发概要文件进行归档，而“开发概要文件”要比“4F96F173-7EBE-4892-B283-52489DE2F409”容易调试。

If this still does not work, I suggest following the link above and go through the certificate process; you take the certificate from your developer computer and copy it into the system folder of the Keychain Access application on your server.

如果这仍然不能工作，我建议遵循上面的链接并通过证书过程;您从开发人员计算机获取证书并将其复制到服务器上的Keychain访问应用程序的系统文件夹中。

Just to add a note since this also gave me a big headache, the simulator for Xcode bots may be located at /var/_xcstest/Library/Application Support/iPhone Simulator/. That is where I found it on our server but I doubt it would be different for others. I had to find it because the Localizable.strings file was not being updated in the simulator and tests were failing. Hope this helps.

我要补充一点，因为这也让我很头疼，Xcode bots的模拟器可能位于/var/ _xcstestst / library/application Support/iPhone模拟器/。这就是我在我们的服务器上找到它的地方，但我怀疑它对其他人来说会有所不同。我必须找到它，因为它是可本地化的。字符串文件没有在模拟器中更新，测试失败。希望这个有帮助。

#7

Actually the solution is way simpler than copying provisioning profiles around or the like. All you need to do is setup Xcode Server correctly.

实际上，这个解决方案比复制配置文件要简单得多。您需要做的就是正确地设置Xcode服务器。

I am using Xcode 6.0.1 (6A317) with Xcode Server 3.2.1 (13S5179). While I thought that Xcode Server would use the provisioning profiles from my Xcode installation, it does not. It has its own folder at /Library/Developer/XcodeServer/ProvisioningProfiles/, whereas Xcode would use ~/Library/MobileDevice/Provisioning\ Profiles/.

我正在使用Xcode 6.0.1 (6A317)和Xcode Server 3.2.1 (13S5179)。虽然我认为Xcode服务器会使用来自我的Xcode安装的配置文件，但它不会。它在/Library/Developer/XcodeServer/提供概要文件/有自己的文件夹，而Xcode会使用~/Library/MobileDevice/Provisioning\概要文件/。

So the solution is: Add your developer accounts to Xcode Server. It will then automatically download all necessary provisioning profiles automagically so your CI builds finally have access to the provisioning profiles. You add an account by clicking that Edit... button in the Builds section of Xcode Server as you can see in the screenshot.

因此解决方案是:将开发人员帐户添加到Xcode服务器。然后，它将自动下载所有必要的配置文件，以便您的CI构建最终能够访问配置文件。您可以通过点击编辑添加一个帐户……在Xcode Server的build部分中的按钮，可以在屏幕截图中看到。

#8

I had the same problem: I've added the provisioning profiles to /Library/Server/Xcode/Data/ProvisioningProfiles but got this error. The solution is to change permissions for the provisioning profiles, so everyone in the system can read them.

我遇到了同样的问题:我已经将配置文件添加到/Library/Server/Xcode/Data/ provisionprofiles，但是出现了这个错误。解决方案是更改配置文件的权限，以便系统中的每个人都可以读取它们。

#9

I tried all of the answers here before sitting back and thinking that it couldn't be this hard. Searched again and found this Apple OS X Server (Xcode CI service) can't find provisioning profiles

我在这里试了所有的答案，然后坐下来想，这不可能这么难。再次搜索，发现苹果OS X服务器(Xcode CI服务)无法找到配置文件

I needed to use the correct team provisioning profiles. This page also links to a good tutorial as well.

我需要使用正确的团队配置文件。这个页面也链接到一个好的教程。

#10

Removing the whole ~/Library/Developer/XCode folder should fix the caching issue. Then the provisioning profiles located in ~/Library/MobileDevice/Provisioning Profiles/ should be found properly by xcode.

删除整个~/Library/Developer/XCode文件夹应该可以修复缓存问题。然后，xcode应该正确地找到位于~/Library/MobileDevice/ provisioning profiles /中的供应配置文件。

#11

@amrsd Thanks. I see now that a lot of people are copying the profiles manually from their "Provisioning Profiles" folder in "~/Library/MobileDevice" with success (including myself). If this is the route you're taking as well, quit copy+pasting and symlink it!

@amrsd谢谢。我现在看到，许多人正在成功地(包括我自己)从“~/Library/MobileDevice”的“供应配置文件”文件夹中手动复制配置文件。如果这也是你要走的路，停止拷贝+粘贴并标记它!

$ sudo -i

$ sudo -我

# mkdir /Library/MobileDevice; ln -s /Users/myuser/Library/MobileDevice/Provisioning\ Profiles/ /Library/MobileDevice/ -- where myuser is your username.

# mkdir /图书馆/ MobileDevice;ln -s /用户/myuser/Library/MobileDevice/Provisioning\ Profiles/ Library/MobileDevice/——myuser是您的用户名。