blocks|key|219661|text|如果您正在将项目与第三方动态框架集成，则可能需要在构建设置中添加路径。查找->Build设置->“运行路径搜索路径”，并确保它包含到框架的路径。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|219662|在建立了一个项目，使用我的团队一直在研究的框架之后，我自己也看到了这个问题。在更新此特定设置后，问题就消失了。在我的例子中，路径与我已经为“框架搜索路径”设置设置的路径相同。|219663|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|$]]

If you are integrating your project with a 3rd party dynamic framework, you may need to add a path in your build settings. Look for ->Build Settings->"Runpath search paths" and make sure it includes the path to the framework. 

I was just seeing this exact issue myself after setting up my a project to use a framework my team has been working on. After updating this specific setting, the problem went away. In my case, the path was identical to one I already had to set for the "Framework search paths" setting.

blocks|key|686461|text|我解决了这个问题，就像我解决了大多数XCode问题一样：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|686462|删除DerivedData中的项目文件(Xcode>Preferences>Locations>DerivedData→跳转到查找器中)|ordered-list-item|offset|length|style|CODE|686463|Product>Clean|686464|(按下alt按钮)+Product>Clean+Build+Folder|686465|退出XCode|686466|重启XCode|686467|将应用程序从设备/模拟器中删除|686468|再试试。如果它仍然不能工作，使用另一个模拟器/设备运行几次。它迟早会再次在原来的一个上工作。|686469|entityMap^0|0|2|B|K|14|0|0|D|0|A|Q|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@$E|Y|F|Z|G|H]|$E|10|F|11|G|H]]|9|@]|A|$]]|$1|I|3|J|5|D|7|12|8|@$E|13|F|14|G|H]]|9|@]|A|$]]|$1|K|3|L|5|D|7|15|8|@$E|16|F|17|G|H]]|9|@]|A|$]]|$1|M|3|N|5|D|7|18|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|19|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1A|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1B|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|V|$]]

I solved this problem, just like I solve most of those XCode Problems:

<ol>
<li>delete your projects files in your <code>DerivedData</code> (<code>Xcode&gt;Preferences&gt;Locations&gt;DerivedData→</code> to jump there in finder)</li>
<li><code>Product&gt;Clean</code></li>
<li>(keep alt-Button pressed) <code>Product&gt;Clean Build Folder</code></li>
<li>Quit XCode</li>
<li>Restart XCode</li>
<li>Remove your app from your device / simulator</li>
</ol>

Try again. 
In case it still doesn't work, use another simulator / device for a few runs. Sooner or later it will work again on the original one again.

blocks|key|686539|text|如果使用可可荚，请检查Cocoapods存储库上的线程：https://github.com/CocoaPods/CocoaPods/issues/5385#issuecomment-226269847|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|686540|这解决了我的问题：|686541|复制@dfleming回复：|686542|由于某些原因，在生成项目工作区时，CocoaPods似乎没有将"CP+Embed框架“构建阶段添加到UI测试目标中。
我手动添加了这个，UI测试再次运行。
此构建阶段应运行以下脚本：(用项目名称替换{YourProject}+)
"${SRCROOT}/Pods/Target+Support+++Files/Pods-{YourProject}UITests/Pods-{YourProject}UITests-frameworks.sh"|blockquote|style|CODE|686543|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/CocoaPods/CocoaPods/issues/5385#issuecomment-226269847^0|S|21|0|0|0|0|37|2Y|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|10|8|@$A|11|B|12|K|L]]|9|@]|C|$]]|$1|M|3|-4|5|6|7|13|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

If you are using cocoa pods, check this thread on the Cocoapods repository:
<a href="https://github.com/CocoaPods/CocoaPods/issues/5385#issuecomment-226269847">https://github.com/CocoaPods/CocoaPods/issues/5385#issuecomment-226269847</a>

This fixed my problem:

Copying @dfleming response: 

<blockquote>
 For some reason, it appears that CocoaPods is not adding the "[CP]
 Embed Pods Frameworks" build phase to the UI Tests target when
 generating the project workspace.
 
 I manually added this in and the UI Tests were runnable again.
 
 This build phase should run the following script: (Replace
 {YourProject} with your project name)
 
 <code>"${SRCROOT}/Pods/Target Support
 Files/Pods-{YourProject}UITests/Pods-{YourProject}UITests-frameworks.sh"</code>
</blockquote>

blocks|key|219483|text|我经历了完全相同的错误，并最终使它发挥作用，这是我采取的步骤。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|219484|试着重新启动Xcode和模拟器，在清理和删除应用程序后，这是行不通的。|ordered-list-item|219485|然后，我按照建议重新启动了Mac，但仍然没有起作用。|219486|然后我选择了一个新的设备在模拟器上进行测试，之前我使用了5s，然后切换到了6，这起作用了。|219487|有趣的是，当我切换到iPhone+6模拟器时，它在运行应用程序和工作之前显示了带有加载条的苹果徽标。|219488|当切换回5s模拟器时，它对苹果的加载条做了完全相同的操作，这是它以前没有做过的，然后5s就开始工作了。|219489|因此，这似乎是一个模拟器问题，切换到不同的设备工作。重置内容和设置可能是非工作设备的解决方案。|219490|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|S|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|T|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|U|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|V|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|W|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|P|$]]

I experienced exactly the same error and eventually got it working, these are the steps I took.

<ol>
<li>Tried restarting Xcode and the simulator, after cleaning and deleting the app, that never worked.</li>
<li>Then I restarted the Mac as suggested, but that still didn't work.</li>
<li>Then I chose a new device to test against in the simulator, was previously using 5s and switched to 6, and that worked. </li>
</ol>

Interestingly, when I switched to the iPhone 6 simulator, it showed the Apple logo with a loading bar, before running the app and working.

When switching back to the 5s simulator it did exactly the same, with the Apple loading bar, which it hadn't done before, and then the 5s worked.

So it looks to be a simulator issue, and switching to a different device worked. Resetting the content and settings may be the solution for a non-working device.

blocks|key|219567|text|Cocoapods+link_with方法会导致这个问题！|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|219568|在xcode+7.2上，我得到了完全相同的错误--没有多少模拟器或设备重置似乎可以清除它。但是，在完全重建了我的UITest目标之后，一切都很顺利。在花费大量时间处理.pbxproj文件的大量差异之后，我为我的项目找到了一个解决方案。我不确定它是否解决了每个看到这个错误的人的根本原因，但它确实为我清除了一切。|219569|在“部署目标”下面的项目信息中，“配置”将列出应用程序的所有可能配置。展开要运行的配置，您应该会看到所有目标的列表。在我的例子中，cocoapods自动为UITest目标添加了一个基本配置：|219570|​|219571|📷|atomic|219572|219573|在下拉列表中将其设置为none。|219574|接下来，在菜单左侧选择UITest目标，然后选择build+phases，您将需要删除check+pods+manifest.lock、link+binary+with+libraries、emebd+pods+frameworks和copy+pods+resources。|219575|最后，转到您的pod文件，检查是否有任何提到您的UITest目标或目标。在我的例子中，我一直在我的podfile顶部指定：|219576|platform+:ios,+'8.4'
use_frameworks!

link_with+'My+App',+'My+UITesting+Target'+

pod+'A+Pod',+'~>+1.0'|code-block|syntax|javascript|219577|相反，podfile应该列出每个目标的特定依赖项：|219578|platform+:ios,+'8.4'
use_frameworks!

target+'My+App',+:exclusive+=>+true+do
++++pod+'A+Pod+I+want+to+use+in+my+app',+'~>+1.0'
end|219579|假设您没有在UITests中使用任何豆荚，那么目标应该再次构建，而不会出现错误，并且测试将运行！|219580|我对这个问题根源的理解是，每个UITest目标构建两个单独的包，一个用于应用程序，一个用于UITest控制器。不幸的是，cocoapods+link_with逻辑修改了所有指定的目标，以期待其包中的pods.framework。构建阶段脚本将框架添加到app包，而不是UITest控制器包，因此当您启动测试时，UITest控制器包似乎缺少框架，xcode中止了安装。|219581|如果您在UITests中使用豆荚，您应该能够以相同的方式指定它们：|219582|target+'My+UITesting+Target',+:exclusive+=>+true+do
++++pod+'Another+Pod+I+want+only+for+UITesting',+'~>+1.0'
end|219583|当您运行pod+install时，一切都应该正确地连接起来。|219584|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/691649120bf6da2fa53c8598f946203d.png|imageAlt^0|A|9|0|2B|8|0|0|0|0|1|0|0|0|B|4|0|O|C|17|O|1W|Q|2N|L|39|J|0|0|0|0|0|0|1Y|9|0|0|0|4|B|0^^$0|@$1|2|3|4|5|6|7|1N|8|@$9|1O|A|1P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1Q|8|@$9|1R|A|1S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1T|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|1U|8|@]|D|@]|E|$]]|$1|L|3|M|5|N|7|1V|8|@]|D|@$9|1W|A|1X|1|1Y]]|E|$]]|$1|O|3|K|5|6|7|1Z|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|20|8|@$9|21|A|22|B|C]]|D|@]|E|$]]|$1|R|3|S|5|6|7|23|8|@$9|24|A|25|B|C]|$9|26|A|27|B|C]|$9|28|A|29|B|C]|$9|2A|A|2B|B|C]|$9|2C|A|2D|B|C]]|D|@]|E|$]]|$1|T|3|U|5|6|7|2E|8|@]|D|@]|E|$]]|$1|V|3|W|5|X|7|2F|8|@]|D|@]|E|$Y|Z]]|$1|10|3|11|5|6|7|2G|8|@]|D|@]|E|$]]|$1|12|3|13|5|X|7|2H|8|@]|D|@]|E|$Y|Z]]|$1|14|3|15|5|6|7|2I|8|@]|D|@]|E|$]]|$1|16|3|17|5|6|7|2J|8|@$9|2K|A|2L|B|C]]|D|@]|E|$]]|$1|18|3|19|5|6|7|2M|8|@]|D|@]|E|$]]|$1|1A|3|1B|5|X|7|2N|8|@]|D|@]|E|$Y|Z]]|$1|1C|3|1D|5|6|7|2O|8|@$9|2P|A|2Q|B|C]]|D|@]|E|$]]|$1|1E|3|-4|5|6|7|2R|8|@]|D|@]|E|$]]]|1F|$1G|$5|1H|1I|1J|E|$1K|1L|1M|-4]]]]

Cocoapods <code>link_with</code> method can cause this issue!

I was getting the exact same error on xcode 7.2 - no number of simulator or device resets seemed to clear it up. After completely rebuilding my UITest targets though things worked fine. After spending a lot of time in a massive git diff of the <code>.pbxproj</code> file I found a solution for my project. Im not sure if it addresses the root cause for everyone who is seeing this error but it definitely clears things up for me. 

From the project info below "deployment target", "Configurations" will list all the possible configurations for your application. Expand the configuration you are trying to run and you should see a list of all your targets. In my case cocoapods had automatically added a base configuration for the UITest target:

<a href="https://i.stack.imgur.com/2NUNV.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/2NUNV.png" alt="enter image description here"></a>

Set this to <code>none</code> in the dropdown. 
Next in the menu to the left select your UITest target then <code>build phases</code> You will need to remove <code>check pods manifest.lock</code> <code>link binary with libraries</code> <code>emebd pods frameworks</code> and <code>copy pods resources</code>. 

Finally go to your pod file and check for any mentions of your UITest target or targets. In my case I had been specifying at the top of my podfile: 

<pre><code>platform :ios, '8.4'
use_frameworks!

link_with 'My App', 'My UITesting Target' 

pod 'A Pod', '~&gt; 1.0'
</code></pre>

Instead the podfile should list specific dependencies for each target:

<pre><code>platform :ios, '8.4'
use_frameworks!

target 'My App', :exclusive =&gt; true do
 pod 'A Pod I want to use in my app', '~&gt; 1.0'
end
</code></pre>

Assuming you weren't using any pods in your UITests the target should build again without errors and tests will run!

My understanding of root of this problem is that each UITest target builds two separate bundles, one for the app and one for the UITest controller. Unfortunately cocoapods <code>link_with</code> logic modifies all the specified targets to expect the pods.framework in their bundle. The build phase scripts add the framework to the app bundle but not the UITest controller bundle, so then when you launch your tests that UITest controller bundle appears to be missing frameworks and xcode aborts the installation.

If you were using pods in your UITests you should be able to specify these in the same way:

<pre><code>target 'My UITesting Target', :exclusive =&gt; true do
 pod 'Another Pod I want only for UITesting', '~&gt; 1.0'
end
</code></pre>

And when you run <code>pod install</code> everything should link up correctly.

blocks|key|219830|text|当您将Cocoapods与缺少某些依赖项的框架一起使用时，也会出现此问题。例如，如果您使用的是Framework，并且此框架依赖于framework，但是在Framework的Podspec中没有声明依赖项。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|219831|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|$]]

This problem can also appears when you use Cocoapods with a framework where some dependencies are missing.
For example if you are using Framework A, and this framework depends of Framework B but in the Podspec of Framework A the dependency is not declared.

blocks|key|686665|text|出现这种情况的原因之一是如果测试目标所在的主机应用程序没有链接到正确的依赖项。例如，如果您正在测试一个框架，请确保主机应用程序链接到这些框架并嵌入其中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|686666|📷|atomic|offset|length|686667|​|686668|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/01b690686cb5341d4f736de15f10785f.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]]]]

One of the reasons this can happen is if the host application that the test target is testing is not linked to the right dependencies. For example, if you have are testing a framework, make sure the host app is linked to those frameworks and also embedded. <a href="https://i.stack.imgur.com/PkN7D.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/PkN7D.png" alt="enter image description here"></a>

blocks|key|219843|text|我的问题是由于单元测试目标的部署版本不正确造成的。经过测试的为7.0，但单元测试的部署版本没有自动正确设置。它被设置为10.0，而我的模拟器版本为8.4。在构建设置中将UT目标的部署版本更改为8.0，然后所有问题都消失了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|219844|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 caused by incorrect deployment version of unittest target. Tested App deployment version was 7.0, but the unittest's was not set up correctly automatically. It was set to 10.0, while my simulator's version was 8.4. Change the UT target's deployment version to 8.0 in build settings and then all the problems disappeared.

blocks|key|300667|text|我尝试了一堆这样的解决方案，但没有运气。我在“计划”的“测试”部分中关闭了“代码覆盖”选项，该选项禁止错误，但测试无法运行。然后，我注意到NSLog控制台中有很多东西。在其中的某个地方，它提到了对我不再使用并试图加载的框架的引用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|300668|我搜索了这个应用程序，并构建了设置->+--其他链接标志试图加载不再存在的框架。|300669|我删除了：-framework+3rd_party_libname|300670|然后测试又起作用了。这是令人困惑的，但请检查NSLog消息。我用的是XCode+8.3|300671|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 tried a bunch of these solutions with no luck. I turned off the Code Coverage option in my Scheme's Test section, which suppressed the error but Tests would not run. Then I noticed quite a bit of stuff in NSLog console. Somewhere in there, it mentioned reference to a framework that I was no longer using and trying to load.

I searched the app for it, and Build Settings -> Other Linker Flags was trying to load the framework that wasn't there anymore. 

I removed:
-framework 3rd_party_libname

Then tests worked again. This was confusing, but please check for NSLog msgs. I was using XCode 8.3

blocks|key|219535|text|你的一个或多个模拟器卡住了。唯一能为我解决这个问题的方法就是从模拟器菜单中重置模拟器的内容和设置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|219536|​|219537|📷|atomic|offset|length|219538|219539|注意:这将删除模拟器中的所有应用程序数据。|219540|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/49ad4d3f1e9377c2f32ebfa60e58798f.png|imageAlt^0|0|0|0|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@$G|X|H|Y|1|Z]]|A|$]]|$1|I|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S|T|-4]]]]

One or more of your simulators has gotten stuck. The only thing that always works to fix this for me is to reset the simulator content and settings from the Simulator menu.

<a href="https://i.stack.imgur.com/HBkaI.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/HBkaI.png" alt="Reset Content and Settings..."></a>

Note: this will delete all app data from the simulator.

blocks|key|292423|text|在我的例子中，我将Swift文件添加到了一个框架中，这个框架(在此之前)是纯粹的目标-C。测试包中没有任何Swift代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|292424|一旦我向测试包添加了一个Swift文件，Xcode就会自动更新一些项目设置，错误就消失了。|292425|您应该将Swift文件保存在测试包中，即使它可能不包含任何代码。Xcode或Cocoapods显然使用测试包中Swift文件的存在来确定是否以“快速模式”运行测试。|292426|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, I had added Swift files to a framework that was (until then) purely Objective-C. The test bundle did not have any Swift code in it.

Once I added a Swift file to the test bundle, Xcode automatically updated some project settings and the error went away.

You should keep the Swift file in the test bundle, even though it may not contain any code. Either Xcode or Cocoapods evidently use the existence of Swift files in the test bundle to determine whether to run the tests in "swift mode".

blocks|key|292172|text|根本原因可能是模拟器故障。模拟器的问题很常见，特别是在第一次发射时。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|292173|如果在模拟器成功启动和连接后出现问题，请张贴错误的详细信息。|292174|为了让模拟器启动，我通常不得不取消第一次运行(在干净地启动Xcode之后)，并尝试重新运行几次。|292175|如果这是可重复的，发生在多个项目上，并且在项目重新启动和清理后仍然存在，如果Stack溢出社区无法帮助，请考虑向Apple提交一个缺陷。|292176|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|$]]

The root cause is probably the simulator failure. Issues with the simulator are common, especially on first launch.

If the problem occurs even after successful simulator launch and connect, please post the details of the error.

To get the simulator to launch, I often have to cancel the first run (after launching Xcode cleanly), and try re-running a few times.

If this is repeatable, happens on multiple projects, and persists after relaunch and cleaning of the projects, consider submitting a defect to Apple if the Stack Overflow community cannot help.

blocks|key|300588|text|我也有同样的问题，但这是由于有一个测试目标和重命名应用程序的目标。确保您有一个有效的主机应用程序集。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|300589|在项目页面上选择测试目标|unordered-list-item|300590|在“常规”选项卡下，应该有“主机应用程序”复选框|300591|选择要对其进行测试的目标|300592|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|M|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|N|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|O|8|@]|9|@]|A|$]]]|J|$]]

I had this same problem but it was due to having a test target and renaming the application's target. Make sure you have a valid Host Application set.

<ul>
<li>Choose the test target on the project page</li>
<li>Under the General tab there should be a Host Application select box</li>
<li>Choose the target you want to test against</li>
</ul>

blocks|key|686740|text|我也面临着同样的问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|686741|为不同的项目尝试了以下内容：|686742|1.对于我有一些第三方框架的项目，问题是测试包无法在运行时找到框架。对于此更新测试目标的运行路径搜索路径，通过添加$(PROJECT_DIR)/Frameworks构建设置(假设您将框架保存在该位置)。它解决了这个项目的问题，您可以在下面的位置查找：|offset|length|style|CODE|686743|Project+file+->+Test+target+->+Build+Settings+->+Runpath+Search+Paths|code-block|syntax|javascript|686744|在其他工作区中，当我将测试设备更改为其他模拟器或更改设备本身时。这很有帮助。|ordered-list-item|686745|重新启动xcode或mac系统。|686746|希望它对你有帮助|686747|entityMap^0|0|0|1L|P|0|0|0|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|6|7|Z|8|@$F|10|G|11|H|I]]|9|@]|A|$]]|$1|J|3|K|5|L|7|12|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|Q|7|13|8|@]|9|@]|A|$]]|$1|R|3|S|5|Q|7|14|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|15|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|W|$]]

I also faced same issue :

Tried following things for different projects :

1.For project where i had some third party frameworks, The problem was that test bundle can't find the framework at runtime. For this update test target's Runpath Search Paths build settings by adding <code>$(PROJECT_DIR)/Frameworks</code> (assuming you keep your frameworks at that location)., It fixed my problem for this project
You can look for it at below location :

<pre><code>Project file -&gt; Test target -&gt; Build Settings -&gt; Runpath Search Paths
</code></pre>

<ol start="2">
<li>In other workspace, When I changed my testing device to some other simulator or change the device itself. it helped.</li>
<li>Restart the xcode or your mac system.</li>
</ol>

hope it will help u

blocks|key|292452|text|迦太基用户：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|292453|在我向Cartfile添加了一个新框架之后，我就遇到了这种情况。|292454|我运行了carthage+update，但忘了将.framework文件从Finder拖到应用程序目标的嵌入式二进制文件部分！|CODE|292455|一旦我这么做了，问题就解决了。|292456|(请注意，这是上面@Mustafa提到的一般性问题的一个具体案例。)|292457|entityMap^0|0|6|0|0|4|F|O|A|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|U|8|@$9|V|A|W|B|J]|$9|X|A|Y|B|J]]|D|@]|E|$]]|$1|K|3|L|5|6|7|Z|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|10|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|P|$]]

Carthage users: 

This happened to me after I added a new framework to my Cartfile.

I ran <code>carthage update</code> but forgot to drag the <code>.framework</code> file from Finder into the Embedded Binaries section of my app target!

Once I did that, the problem went away.

(Note this is a specific case of the general problem mentioned by @Mustafa above.)

blocks|key|219960|text|我在塞拉利昂10.12.4的Xcode+8.3上遇到了这个问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|219961|我在Mac上打开了密钥链访问应用程序。|219962|几秒钟后，我有几个系统弹出请求我的密码，以授予对密钥链项目的权限。|219963|我在弹出窗口中输入了密码，然后测试开始工作。|219964|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 was having this problem on Xcode 8.3 on Sierra 10.12.4

I opened the Keychain Access application on my Mac

After a few seconds, I got several system pop-ups asking for my password, to grant permissions to Keychain items.

I entered my password into the pop-ups, and then my tests starting working.

blocks|key|300713|text|在我的例子中起作用的步骤，删除该方案，然后单击Manage+>自动生成方案解决了我的情况下的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|300714|问题是在模拟器和密钥链中安装证书引起的。|300715|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|$]]

Steps that worked in my case
Delete the scheme and clicking Manage Scheme->Auto generate scheme resolved the issue in my case.

Issue was caused by installing the certificate in the simulator and in the keychain

blocks|key|686992|text|使用带有多个构建目标和标准编译器的Xcode+9.1，我们正在进行UI测试，我开始看到这个问题。所以，你可能会讨厌我的这个答案，我完全希望它会被否决，但这实际上对我有效:我必须把Xcode和我的项目从我的机器上完全删除，以使这个错误消失。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|686993|我多次尝试这个线程中的每一个建议，多次尝试清除缓存文件、删除派生数据、修改构建设置、更新podfile、每次尝试后清理、重建、清理模拟器、手动在“管理设备”中重新创建模拟器。在经历了几个小时的挫折之后，这台机器为什么无法构建我们的UI测试仍然是一个完全的谜。它似乎在其他机器和我们的CI上工作得很好。除了这个线程中的项之外，我还手动修改了pbxproj文件，将与代码覆盖率相关的所有选项设置为"NO“。|686994|最后，我离改造整台机器只有一步之遥。我决定按照以下建议完全删除Xcode：Stackoverflow:+How+to+completely+uninstall+Xcode。|offset|length|686995|具体来说，我破坏了我们的工作空间，退出了所有程序，删除了模拟器中列出的所有文件，清除了内容和设置，删除了模拟器，关闭了机器20分钟，返回，重新安装了Xcode，克隆了存储库，瞧！没有错误。|686996|希望这能为某人解决问题。这是‘核’选项，你永远不应该这样做，但就像我说的，这是唯一对我有用的东西。|686997|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/31011062/how-to-completely-uninstall-xcode-and-clear-all-settings^0|0|0|11|1C|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|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$F|W|G|X|1|Y]]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

Using Xcode 9.1 with multiple build targets and standard compiler we were working on UI tests and I started seeing this problem. So, you will probably hate me for this answer, and I fully expect it to be downvoted, BUT this actually worked for me: I had to completely remove Xcode and my project from my machine to make this error disappear.

I tried every single suggestion in this thread, some multiple times, tried clearing cache files, deleting derived data, tinkering with build settings, updating podfiles, cleaning, rebuilding after each attempt, cleaning the simulator, manually recreating the simulators in 'manage devices'. After hours and hours of frustration it was still a complete mystery why this machine was failing to build our UI test. It seemed to work fine on other machines and on our CI. In addition to the items in this thread I manually modified the pbxproj file to set all options related to code coverage to "NO".

Finally, I was 1 step away from reformatting the entire machine. I decided to completely remove Xcode following the suggestions here: <a href="https://stackoverflow.com/questions/31011062/how-to-completely-uninstall-xcode-and-clear-all-settings">Stackoverflow: How to completely uninstall Xcode</a>. 

Specifically, I trashed our workspace, quit all programs, deleted all of the files listed, cleared content and settings from the simulator, deleted the simulator, turned the machine off for 20 minutes, came back, reinstalled Xcode, cloned the repository, and voila! No error.

Hope that solves the issue for someone. It's the 'nuclear' option, and you should never ever have to do this, but like I said, this is the only thing that worked for me.

When I run my tests I get an error:

<blockquote>
 Code coverage data generation failed. 
 Unable to retrieve the profile data files from 'UIDevice'.
</blockquote>

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

On console was printed warning:

<blockquote>
 Timed out waiting 120 seconds for simulator to boot, current state is 1.
</blockquote>

What is the reason?

Xcode 7 - Code coverage data generation failed

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

当我运行测试时，我会得到一个错误：代码覆盖率数据生成失败。无法从“UIDevice”检索概要数据文件。​​在控制台上打印了警告：超时等待120秒模拟器启动，目前的状态是1。原因何在？

问Xcode 7-代码覆盖率数据生成失败
EN

回答 18

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Xcode 7-代码覆盖率数据生成失败EN

回答 18

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Xcode 7-代码覆盖率数据生成失败
EN