I'm trying to distribute a new version of the app (it can be installed OTA) and I got the error:
我正在尝试发布一个新版本的应用程序(它可以安装OTA),我得到了错误:
"Code Sign error: No matching provisioning profile found: Your build settings specify a provisioning profile with the UUID “AdHocProfile”, however, no such provisioning profile was found. " and Xcode gets stuck in the process of automatically fix the error:
“代码签名错误:没有找到匹配的配置文件:您的构建设置使用UUID“AdHocProfile”指定配置文件,但是没有找到这样的配置文件。Xcode被卡在自动修正错误的过程中:
I have spent a lot of hours in the weekend looking for a solution here and on the internet, only to get rid of one of the two errors I got when I tried to archive the app to distribute it "Ad Hoc".
我在周末花了很多时间在这里和互联网上寻找解决方案,只是为了摆脱我在试图将应用程序发布到“临时”时所犯的两个错误之一。
I made some capture screens to clarify what I've done:
我做了一些截图来澄清我所做的事情:
Provisioning profile at Developer site:
开发人员站点的配置文件:
My account: certificates and profiles:
我的账户:证书和档案:
Project Settings:
项目设置:
Target Settings (Xcode changed them when I deleted the line PROVISIONING_PROFILE in project.pbxproj):
目标设置(当我删除project.pbxproj中的line PROVISIONING_PROFILE时,Xcode更改了它们):
I deleted the line containing PROVISIONING_PROFILE in project.pbxproj, following the directions found in posts similar to this
我删除了项目中包含PROVISIONING_PROFILE的行。pbxproj,按照与此类似的文章中的指示。
I also removed both the stable and the beta versions of Xcode and reinstalled it from the App Store. Don't know if it's important, but I removed the beta 5.1.3 with App Cleaner, deleting all the files associated to it.
我还删除了Xcode的稳定版和beta版,并从App Store中重新安装。不知道这是否重要,但我用应用程序清除器删除了测试版5.1.3,删除了与之相关的所有文件。
Since Xcode does not longer show the values on the popup to choose certificates, I am not sure if I choose the correct ones.
由于Xcode不再显示弹出窗口中的值来选择证书,所以我不确定是否选择了正确的证书。
Could you please help me to solve this issue?
你能帮我解决这个问题吗?
13 个解决方案
#1
36
This took me a long time to figure out. I wasn't keen to redo all my profiles and certificates like some of the people suggested. My error message was saying ""Code Sign error: No matching provisioning profile found: Your build settings specify a provisioning profile with the UUID “6278e001-8887-4fe4-a95c-a722c896792f”" but then when I went into ~/Library/MobileDevice/Provisioning\ Profiles
and printed out all the files using ls -la
I could clearly see the profile there.
我花了很长时间才弄明白。我不喜欢重新做我的个人资料和证书,就像一些人建议的那样。我的错误信息是“代码签名错误:没有找到匹配的配置文件:您的构建设置指定了UUID”6278e001-8887-4fe4-a95c-a722c896792f的配置文件”,但是当我进入~/Library/MobileDevice/ provisioning \ Profiles并使用ls -la打印出所有文件时,我可以清楚地看到那里的配置文件。
I tried doing a Clean
and Clean Build Folder...
. I then tried to remove derived data. None of this worked.
我试着做一个干净和清洁....建立文件夹然后我试图删除派生的数据。这并不奏效。
But then when I simply quit Xcode and opened it again it worked
但是当我简单地退出Xcode并再次打开它时,它就成功了。
Xcode must be storing a cache somewhere when it opens up. This seems crazy to me. But what can we do.
Xcode必须在打开时存储缓存。这对我来说太疯狂了。但我们能做什么呢?
I hope this helps someone.
我希望这能帮助别人。
#2
15
I had the same issue this morning, and wasted about two hours desperately trying to fix it.
我今天早上也遇到了同样的问题,浪费了两个小时,拼命想要解决它。
"Code Sign error: No matching provisioning profile found: Your build settings specify a provisioning profile with the UUID "0C60982A-9F45-4737-8135-505126A6DC2E", however, no such provisioning profile was found. "
“代码签名错误:没有找到匹配的配置文件:您的构建设置使用UUID“0C60982A-9F45-4737-8135-505126A6DC2E”来指定配置文件,但是没有找到这样的配置文件。”
What I learned is this:
我学到的是:
If XCode ever reports that it can't find a Provisioning Profile, but just quotes the GUID, then give up trying to use your initiative, create new Profiles or Certificates, and get ready to hack.
如果XCode曾经报告说它不能找到配置文件,但是只需引用GUID,然后放弃使用您的计划,创建新的配置文件或证书,并准备进行黑客攻击。
The only way I could stop this error from happening (even after adding valid Provisioning Profiles) was to manually edit the .pbxproj file within the *.xcodeproj package.
我能够阻止这个错误发生的唯一方法(甚至在添加了有效的配置文件之后)是在*中手动编辑.pbxproj文件。xcodeproj包。
Do a search for the GUID within this file, strip it out, and finally - finally - XCode will stop complaining.
在这个文件中搜索GUID,去掉它,最后——最后——XCode将停止抱怨。
Seriously, this is 2014, why is Apple's development environment such a dinosaur ?
说真的,这是2014年,为什么苹果公司的开发环境会像恐龙一样?
Year after year, it's just bad... and they prefer to add a second programming language to it, rather than actually improve its usability.
年复一年,一切都很糟糕……而且他们更愿意将第二种编程语言添加到其中,而不是真正提高其可用性。
(Sorry.. I'm in a bad mood after wasting my morning on this...)
(抱歉. .我今天早上浪费了这么多时间,心情很不好。
#3
4
Well, I solved this issue going back to a previous version stored in Time Machine, deleting all certificates and profiles both on Developer website and computer, deleted files in ~Library/MobileDevice/Provisioning Profiles and the certificates stored in Keychain Access. Also checked in project.pbxproj that no PROVISIONING_PROFILE was set.
嗯,我解决了这个问题,回到了以前的版本存储在时间机器上,删除了开发者网站和计算机上的所有证书和配置文件,删除了~Library/MobileDevice/Provisioning配置文件中的文件和存储在Keychain访问中的证书。也检查项目。pbxproj没有设置PROVISIONING_PROFILE。
Then, I loaded the old version in Xcode and I was able to build and archive it.
然后,我在Xcode中加载了旧版本,并且我能够构建和归档它。
After that, the newest version worked again.
在那之后,最新的版本又开始工作了。
By the way, if you try to distribute an app to a device running iOS 7.1, read this
顺便说一下,如果你试图将一个应用程序发布到运行iOS 7.1的设备上,请阅读这篇文章。
#4
3
Quit Xcode and re-open, this worked for me. Would try first before spending too long attempting to fix it.
退出Xcode重新打开,这对我很有效。在花费太长时间试图修复它之前,先尝试一下。
#5
0
Egad… try this first: Our team encountered this exact issue trying to open an updated app with newly download Xcode 5.1 on iOS 7.1 device with a one day tardy profile. Hours later:
第一个尝试:我们的团队遇到了这个问题,试图打开一个更新的应用程序,在iOS 7.1设备上新下载Xcode 5.1,有一天的延迟。小时后:
Download and install a new profile (as necessary) then:
下载并安装一个新的配置文件(必要时):
Make sure the BUNDLE IDENTIFIER in your project's Xcode’s GENERAL view matches verbatim what the profile reads on your Developer WEB portal, and then be sure THAT profile is downloaded & installed in Xcode. Select that profile in your BUILD setting, and you could be solved by now (the App then installed on devices without issue), but we also noticed we could to go back to GENERAL view and the FIX button actually worked: it fixed the "not found" profile
在您的项目的Xcode的常规视图中,确保包标识符与您的开发WEB门户上的概要文件相匹配,然后确保在Xcode中下载并安装了概要文件。在您的构建设置中选择这个概要文件,现在可以解决这个问题(应用程序在没有问题的设备上安装),但是我们也注意到我们可以回到一般的视图,而FIX按钮实际上是有效的:它修复了“未找到”的概要文件。
#6
0
If anyone still has this issue - and happens to have setup a workspace with individual projects, I'd suggest you from the root folder do a:
如果任何人仍然有这个问题——并且碰巧已经为每个项目设置了一个工作空间,我建议您从根文件夹中执行以下操作:
egrep -R "INPUT_THE_ID_MISSING" *
and remove directly the PROVISIONING_PROFILE = "*****"
line from the file in my case, it ended happening that an old xcodeproject has a bad provisioning but I was attempting to archive from within the workspace
在我的例子中,从文件中直接删除PROVISIONING_PROFILE = "**** "行,它结束了一个旧的xcodeproject有一个糟糕的配置,但我试图从工作区中归档。
#8
#9
0
I kept running into this issue with Xcode 7.1 and tried some of the solutions above but didn't have any success. What I found did solve the issue was going to Go > Go To Folder > ~/Library/MobileDevice/Provisioning Profiles and deleting all of the provisioning profiles.
我一直使用Xcode 7.1来解决这个问题,并尝试了上面的一些解决方案,但是没有成功。我发现解决这个问题的方法是将>转到> ~/Library/MobileDevice/Provisioning配置文件,并删除所有配置文件。
From there I added back the provisioning profiles on an as needed basis and it seemed fix the issue. I'll post back if I find that it doesn't permanently fix the issue, but so far so good.
在那里,我在必要的基础上添加了配置文件,似乎解决了这个问题。如果我发现它并不能永久地解决问题,我就会回复,但到目前为止还不错。
#10
0
I was able to get a fix done just by doing the following:
我可以通过以下方式解决问题:
- Xcode -> Preferences
- Xcode - >首选项
- Accounts
- 账户
- Select your Apple ID and remove it by clicking the '-' button at the bottom
- 选择你的苹果ID,并通过点击底部的“-”按钮删除它。
- Click the '+' button at bottom -> Add Apple ID
- 点击底部的“+”按钮->添加苹果ID。
- Login with your Apple ID
- 用你的苹果账号登录。
- Download all certificates again
- 再次下载所有证书
- Specify your profiles in your Build Settings
- 在构建设置中指定概要文件。
- Build
- 构建
#11
0
Considering everything you set properly still facing issue. Then Just delete all derived data for your project , quit XCode then open your project again.
考虑到你所设置的一切,仍然面临着问题。然后只需删除项目的所有派生数据,退出XCode,然后再次打开项目。
It workes for me.
这对我来说附件。
#12
0
I got this issue running Xcode 7.2.1 and found out that I had multiple provisioning profiles with the same name (The name on the developer portal).
我得到了运行Xcode 7.2.1的这个问题,并发现我有多个配置文件,名称相同(开发人员门户上的名称)。
By navigating to ~/Library/MobileDevice/Provisioning Profiles and removing all old provisioning profiles with the same name I was able to solve this problem.
通过导航到~/Library/MobileDevice/Provisioning配置文件,并删除具有相同名称的所有旧配置文件,我可以解决这个问题。
In the terminal, navigate to the provisioning profile folder:
在终端,导航到配置文件文件夹:
cd ~/Library/MobileDevice/Provisioning\ Profiles
List all provisioning profiles with your name:
列出所有您的名字的配置文件:
grep -ar 'MyProvisioningProfileName' .
-a
means that we treat all files as ASCII text.
-表示我们将所有文件视为ASCII文本。
-r
means that we will search all subdirectories listed.
-r意味着我们将搜索列出的所有子目录。
This should produce a list of all provisioning profiles with the same name, e.g.
这将生成具有相同名称的所有配置文件的列表。
./123ha32ba-b5df-abee-12yb-12a34b216ba8.mobileprovision: <string>MyProvisioningProfileName</string>
./214hj32cf-bdfh-1ebe-bba4-7ba32b2165ha.mobileprovision: <string>MyProvisioningProfileName</string>
./321habc2f-jk32-bbae-5tga-yha234b16lka.mobileprovision: <string>MyProvisioningProfileName</string>
By deleting every provisioning profile you don't want (or deleting all and downloading a new one from the developer profile.) this problem went away.
通过删除您不想要的所有配置文件(或删除所有的配置文件并从开发人员配置文件中下载一个新配置文件),这个问题就消失了。
#13
-1
I had this issue this morning. The only way to resolve it was removing all my provisioning profiles from
今天早上我有这个问题。解决它的唯一方法是删除所有的配置文件。
~Library/MobileDevice/Provisioning Profiles
~图书馆/ MobileDevice /配置概要文件
and downloading again all my provisioning profiles from
然后再次下载我的配置文件。
Xcode -> Preferences -> Accounts
Xcode ->偏好->帐户。
My project build and works now.
我的项目现在正在建设和工作。
#1
36
This took me a long time to figure out. I wasn't keen to redo all my profiles and certificates like some of the people suggested. My error message was saying ""Code Sign error: No matching provisioning profile found: Your build settings specify a provisioning profile with the UUID “6278e001-8887-4fe4-a95c-a722c896792f”" but then when I went into ~/Library/MobileDevice/Provisioning\ Profiles
and printed out all the files using ls -la
I could clearly see the profile there.
我花了很长时间才弄明白。我不喜欢重新做我的个人资料和证书,就像一些人建议的那样。我的错误信息是“代码签名错误:没有找到匹配的配置文件:您的构建设置指定了UUID”6278e001-8887-4fe4-a95c-a722c896792f的配置文件”,但是当我进入~/Library/MobileDevice/ provisioning \ Profiles并使用ls -la打印出所有文件时,我可以清楚地看到那里的配置文件。
I tried doing a Clean
and Clean Build Folder...
. I then tried to remove derived data. None of this worked.
我试着做一个干净和清洁....建立文件夹然后我试图删除派生的数据。这并不奏效。
But then when I simply quit Xcode and opened it again it worked
但是当我简单地退出Xcode并再次打开它时,它就成功了。
Xcode must be storing a cache somewhere when it opens up. This seems crazy to me. But what can we do.
Xcode必须在打开时存储缓存。这对我来说太疯狂了。但我们能做什么呢?
I hope this helps someone.
我希望这能帮助别人。
#2
15
I had the same issue this morning, and wasted about two hours desperately trying to fix it.
我今天早上也遇到了同样的问题,浪费了两个小时,拼命想要解决它。
"Code Sign error: No matching provisioning profile found: Your build settings specify a provisioning profile with the UUID "0C60982A-9F45-4737-8135-505126A6DC2E", however, no such provisioning profile was found. "
“代码签名错误:没有找到匹配的配置文件:您的构建设置使用UUID“0C60982A-9F45-4737-8135-505126A6DC2E”来指定配置文件,但是没有找到这样的配置文件。”
What I learned is this:
我学到的是:
If XCode ever reports that it can't find a Provisioning Profile, but just quotes the GUID, then give up trying to use your initiative, create new Profiles or Certificates, and get ready to hack.
如果XCode曾经报告说它不能找到配置文件,但是只需引用GUID,然后放弃使用您的计划,创建新的配置文件或证书,并准备进行黑客攻击。
The only way I could stop this error from happening (even after adding valid Provisioning Profiles) was to manually edit the .pbxproj file within the *.xcodeproj package.
我能够阻止这个错误发生的唯一方法(甚至在添加了有效的配置文件之后)是在*中手动编辑.pbxproj文件。xcodeproj包。
Do a search for the GUID within this file, strip it out, and finally - finally - XCode will stop complaining.
在这个文件中搜索GUID,去掉它,最后——最后——XCode将停止抱怨。
Seriously, this is 2014, why is Apple's development environment such a dinosaur ?
说真的,这是2014年,为什么苹果公司的开发环境会像恐龙一样?
Year after year, it's just bad... and they prefer to add a second programming language to it, rather than actually improve its usability.
年复一年,一切都很糟糕……而且他们更愿意将第二种编程语言添加到其中,而不是真正提高其可用性。
(Sorry.. I'm in a bad mood after wasting my morning on this...)
(抱歉. .我今天早上浪费了这么多时间,心情很不好。
#3
4
Well, I solved this issue going back to a previous version stored in Time Machine, deleting all certificates and profiles both on Developer website and computer, deleted files in ~Library/MobileDevice/Provisioning Profiles and the certificates stored in Keychain Access. Also checked in project.pbxproj that no PROVISIONING_PROFILE was set.
嗯,我解决了这个问题,回到了以前的版本存储在时间机器上,删除了开发者网站和计算机上的所有证书和配置文件,删除了~Library/MobileDevice/Provisioning配置文件中的文件和存储在Keychain访问中的证书。也检查项目。pbxproj没有设置PROVISIONING_PROFILE。
Then, I loaded the old version in Xcode and I was able to build and archive it.
然后,我在Xcode中加载了旧版本,并且我能够构建和归档它。
After that, the newest version worked again.
在那之后,最新的版本又开始工作了。
By the way, if you try to distribute an app to a device running iOS 7.1, read this
顺便说一下,如果你试图将一个应用程序发布到运行iOS 7.1的设备上,请阅读这篇文章。
#4
3
Quit Xcode and re-open, this worked for me. Would try first before spending too long attempting to fix it.
退出Xcode重新打开,这对我很有效。在花费太长时间试图修复它之前,先尝试一下。
#5
0
Egad… try this first: Our team encountered this exact issue trying to open an updated app with newly download Xcode 5.1 on iOS 7.1 device with a one day tardy profile. Hours later:
第一个尝试:我们的团队遇到了这个问题,试图打开一个更新的应用程序,在iOS 7.1设备上新下载Xcode 5.1,有一天的延迟。小时后:
Download and install a new profile (as necessary) then:
下载并安装一个新的配置文件(必要时):
Make sure the BUNDLE IDENTIFIER in your project's Xcode’s GENERAL view matches verbatim what the profile reads on your Developer WEB portal, and then be sure THAT profile is downloaded & installed in Xcode. Select that profile in your BUILD setting, and you could be solved by now (the App then installed on devices without issue), but we also noticed we could to go back to GENERAL view and the FIX button actually worked: it fixed the "not found" profile
在您的项目的Xcode的常规视图中,确保包标识符与您的开发WEB门户上的概要文件相匹配,然后确保在Xcode中下载并安装了概要文件。在您的构建设置中选择这个概要文件,现在可以解决这个问题(应用程序在没有问题的设备上安装),但是我们也注意到我们可以回到一般的视图,而FIX按钮实际上是有效的:它修复了“未找到”的概要文件。
#6
0
If anyone still has this issue - and happens to have setup a workspace with individual projects, I'd suggest you from the root folder do a:
如果任何人仍然有这个问题——并且碰巧已经为每个项目设置了一个工作空间,我建议您从根文件夹中执行以下操作:
egrep -R "INPUT_THE_ID_MISSING" *
and remove directly the PROVISIONING_PROFILE = "*****"
line from the file in my case, it ended happening that an old xcodeproject has a bad provisioning but I was attempting to archive from within the workspace
在我的例子中,从文件中直接删除PROVISIONING_PROFILE = "**** "行,它结束了一个旧的xcodeproject有一个糟糕的配置,但我试图从工作区中归档。
#7
#8
0
Below is what worked for me in XCode 7.
下面是XCode 7中为我工作的内容。
I had to change provision profile in XXXXTests too...
我也不得不在xxxxtest中更改供应配置文件……
#9
0
I kept running into this issue with Xcode 7.1 and tried some of the solutions above but didn't have any success. What I found did solve the issue was going to Go > Go To Folder > ~/Library/MobileDevice/Provisioning Profiles and deleting all of the provisioning profiles.
我一直使用Xcode 7.1来解决这个问题,并尝试了上面的一些解决方案,但是没有成功。我发现解决这个问题的方法是将>转到> ~/Library/MobileDevice/Provisioning配置文件,并删除所有配置文件。
From there I added back the provisioning profiles on an as needed basis and it seemed fix the issue. I'll post back if I find that it doesn't permanently fix the issue, but so far so good.
在那里,我在必要的基础上添加了配置文件,似乎解决了这个问题。如果我发现它并不能永久地解决问题,我就会回复,但到目前为止还不错。
#10
0
I was able to get a fix done just by doing the following:
我可以通过以下方式解决问题:
- Xcode -> Preferences
- Xcode - >首选项
- Accounts
- 账户
- Select your Apple ID and remove it by clicking the '-' button at the bottom
- 选择你的苹果ID,并通过点击底部的“-”按钮删除它。
- Click the '+' button at bottom -> Add Apple ID
- 点击底部的“+”按钮->添加苹果ID。
- Login with your Apple ID
- 用你的苹果账号登录。
- Download all certificates again
- 再次下载所有证书
- Specify your profiles in your Build Settings
- 在构建设置中指定概要文件。
- Build
- 构建
#11
0
Considering everything you set properly still facing issue. Then Just delete all derived data for your project , quit XCode then open your project again.
考虑到你所设置的一切,仍然面临着问题。然后只需删除项目的所有派生数据,退出XCode,然后再次打开项目。
It workes for me.
这对我来说附件。
#12
0
I got this issue running Xcode 7.2.1 and found out that I had multiple provisioning profiles with the same name (The name on the developer portal).
我得到了运行Xcode 7.2.1的这个问题,并发现我有多个配置文件,名称相同(开发人员门户上的名称)。
By navigating to ~/Library/MobileDevice/Provisioning Profiles and removing all old provisioning profiles with the same name I was able to solve this problem.
通过导航到~/Library/MobileDevice/Provisioning配置文件,并删除具有相同名称的所有旧配置文件,我可以解决这个问题。
In the terminal, navigate to the provisioning profile folder:
在终端,导航到配置文件文件夹:
cd ~/Library/MobileDevice/Provisioning\ Profiles
List all provisioning profiles with your name:
列出所有您的名字的配置文件:
grep -ar 'MyProvisioningProfileName' .
-a
means that we treat all files as ASCII text.
-表示我们将所有文件视为ASCII文本。
-r
means that we will search all subdirectories listed.
-r意味着我们将搜索列出的所有子目录。
This should produce a list of all provisioning profiles with the same name, e.g.
这将生成具有相同名称的所有配置文件的列表。
./123ha32ba-b5df-abee-12yb-12a34b216ba8.mobileprovision: <string>MyProvisioningProfileName</string>
./214hj32cf-bdfh-1ebe-bba4-7ba32b2165ha.mobileprovision: <string>MyProvisioningProfileName</string>
./321habc2f-jk32-bbae-5tga-yha234b16lka.mobileprovision: <string>MyProvisioningProfileName</string>
By deleting every provisioning profile you don't want (or deleting all and downloading a new one from the developer profile.) this problem went away.
通过删除您不想要的所有配置文件(或删除所有的配置文件并从开发人员配置文件中下载一个新配置文件),这个问题就消失了。
#13
-1
I had this issue this morning. The only way to resolve it was removing all my provisioning profiles from
今天早上我有这个问题。解决它的唯一方法是删除所有的配置文件。
~Library/MobileDevice/Provisioning Profiles
~图书馆/ MobileDevice /配置概要文件
and downloading again all my provisioning profiles from
然后再次下载我的配置文件。
Xcode -> Preferences -> Accounts
Xcode ->偏好->帐户。
My project build and works now.
我的项目现在正在建设和工作。