Xcode 7 - Code coverage data generation failed

When I run my tests I get an error:

Code coverage data generation failed.
Unable to retrieve the profile data files from 'UIDevice'.

On console was printed warning:

Timed out waiting 120 seconds for simulator to boot, current state is 1.

What is the reason?

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.

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

1. delete your projects files in your DerivedData (Xcode>Preferences>Locations>DerivedData→ to jump there in finder)
2. Product>Clean
3. (keep alt-Button pressed) Product>Clean Build Folder
4. Quit XCode
5. Restart XCode
6. Remove your app from your device / simulator

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.

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

This fixed my problem:

Copying @dfleming response:

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)

"${SRCROOT}/Pods/Target Support Files/Pods-{YourProject}UITests/Pods-{YourProject}UITests-frameworks.sh"

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

1. Tried restarting Xcode and the simulator, after cleaning and deleting the app, that never worked.

2. Then I restarted the Mac as suggested, but that still didn't work.

3. Then I chose a new device to test against in the simulator, was previously using 5s and switched to 6, and that worked.

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.

Cocoapods link_with 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 .pbxproj 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:

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

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:

platform :ios, '8.4'
use_frameworks!

link_with 'My App', 'My UITesting Target' 

pod 'A Pod', '~> 1.0'

Instead the podfile should list specific dependencies for each target:

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

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 link_with 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:

target 'My UITesting Target', :exclusive => true do
    pod 'Another Pod I want only for UITesting', '~> 1.0'
end

And when you run pod install everything should link up correctly.