ios Xcode 7：应用程序安装失败：找不到此可执行文件的有效配置文件
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/33126849/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Xcode 7: App installation failed: A valid provisioning profile for this executable was not found
提问by Sandy
I have already searched and almost implemented max solution but it's not installing any app even though if I am creating just sample single view app.
我已经搜索并几乎实现了最大解决方案，但即使我只是创建示例单视图应用程序，它也没有安装任何应用程序。
App installation failed
A valid provisioning profile for this executable was not found.
应用程序安装失败
找不到此可执行文件的有效配置文件。
回答by take
============== update====================
I fixed this issue today.
First, go to ~/Library/MobileDevice/Provisioning Profiles.
Make sure Xcode isn't running.
Then, delete all provisioning files (like xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.mobileprovision).
Start Xcode.
You will see something like "Fix this issue" in your Target's General tab.
Click it.
Xcode will now load new provisioning profile.
That's it.
==============更新====================
我今天解决了这个问题。
首先，前往~/Library/MobileDevice/Provisioning Profiles。确保 Xcode 没有运行。然后，删除所有配置文件（如 xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.mobileprovision）。
启动Xcode。
您将在 Target 的常规选项卡中看到类似“修复此问题”的内容。点击它。
Xcode 现在将加载新的配置文件。
就是这样。
----------- OLD Answer -------------
----------- 旧答案 -------------
I have same problem now.
I've checked my provisioning profile using https://github.com/chockenberry/Provisioning/releases.
In my case, my provisioning profile had the wrong UDIDs but right machine count.
I've registered machines, and Apple Developer Center listed right UDIDs for those machines.
However, whenever I downloaded new provisioning profile, it contained wrong UDIDs.
I think Apple's system is outputting wrong provisioning profile.
I called Apple support for this issue today, but Apple only emailed me with their knowledge base links(forums,documents,etc).
我现在有同样的问题。
我已经使用https://github.com/chockenberry/Provisioning/releases检查了我的配置文件。
就我而言，我的配置文件的 UDID 错误，但机器数量正确。
我已经注册了机器，Apple Developer Center 为这些机器列出了正确的 UDID。
但是，每当我下载新的配置文件时，它都会包含错误的 UDID。
我认为 Apple 的系统正在输出错误的配置文件。
我今天就这个问题致电 Apple 支持，但 Apple 只通过电子邮件向我发送了他们的知识库链接（论坛、文档等）。
回答by Avijit Nagare
Possibly you are using App Store distribution provisioning profile. Use development or Ad-Hoc provisioning profile.
可能您正在使用 App Store 分发配置文件。使用开发或 Ad-Hoc 配置文件。
回答by tolbard
For Xcode 8 / Swift 3.0 In my case, for my app target and my extension in "General" I check "Automatically manage signing" and it work
对于 Xcode 8 / Swift 3.0 在我的情况下，对于我的应用程序目标和“常规”中的扩展，我选中“自动管理签名”并且它工作
回答by sga4
I was having this issue because the date/time on my iPhone was not the same as that on my Mac running Xcode ( i changed the date on my iPhone while testing some app).
On my iPhone, i went to Settings > General > Date & Time > Set Automatically
我遇到这个问题是因为我的 iPhone 上的日期/时间与运行 Xcode 的 Mac 上的日期/时间不同（我在测试某些应用程序时更改了我的 iPhone 上的日期）。在我的 iPhone 上，我去了Settings > General > Date & Time > Set Automatically
This fixed it
这修复了它
回答by Amit Tandel
Make sure you have added device UDID in your provisioning profile.
确保您已在配置文件中添加了设备 UDID。
- Go to provisioning portal.
- Edit provisioning profile.
- Make sure device is checked.
- Done, download
- Use new Profile
- 转到配置门户。
- 编辑配置文件。
- 确保设备已检查。
- 完成，下载
- 使用新配置文件
Another possible reason: Device date is set to later than the expiry of you provisioning profile.This is very weird but, it could happen.
另一个可能的原因：设备日期设置为晚于您配置文件的到期时间。这很奇怪，但它可能会发生。
回答by DeadRat
I could run on Simulator just fine, but trying to install the App on device was throwing this exact error.
我可以在模拟器上运行得很好，但是尝试在设备上安装应用程序会抛出这个确切的错误。
I had a test target in addition to the main target. The test target had signing set to a different team and profile. Setting the unit test target to match the main target settings for signing solved my issue.
除了主要目标之外，我还有一个测试目标。测试目标已将签名设置为不同的团队和个人资料。将单元测试目标设置为与签名的主要目标设置相匹配解决了我的问题。
Didn't notice it had been automatically changed over to a different team, was caused by being added to a new Enterprise team.
没有注意到它已自动转移到不同的团队，是由于被添加到新的企业团队所致。
回答by XIII
In my case it was that the running option in the building scheme was set to Release so it was trying to sign it using the appstore provisional profile not the development or the adhoc one. I had to set it to Debug to fix this!
在我的情况下，构建方案中的运行选项设置为发布，因此它试图使用 appstore 临时配置文件而不是开发或临时配置文件对其进行签名。我不得不将它设置为调试来解决这个问题！
回答by Gabriel Guedes
In my case, I went to the Apple Developer website and added the phone to the Provisioning Profile. Then I re-downloaded the Provisioning Profile and worked =)
就我而言，我访问了 Apple Developer 网站并将手机添加到了配置文件中。然后我重新下载了配置文件并开始工作 =)
回答by Matías González
In my case was The build system. I had to change the default build system in "File > Project / Workspace Settings" and change it to the Legacy Build system.
在我的情况下是构建系统。我必须在“文件 > 项目/工作区设置”中更改默认构建系统，并将其更改为旧版构建系统。
回答by Patrick Harrison
The following worked for me:
以下对我有用：
- Install the app using Personal provision profile (re-install after going into your phone settings and trusting the profile)
- Delete the app from ypur phone
- Switch back to registered developer profile and try again
- 使用个人配置文件安装应用程序（进入手机设置并信任配置文件后重新安装）
- 从 ypur 手机中删除应用程序
- 切换回已注册的开发者资料并重试
