# Xcode Test for iOS v2.1.0 **URL:** \ **Category:** Changelog\ **Created:** [January 10, 2019, 12:54pm UTC](https://discuss.bitrise.io/t/xcode-test-for-ios-v2-1-0/7601 "2019-01-10T12:54:36Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)\ **Post date:** [January 10, 2019, 12:54pm UTC](https://discuss.bitrise.io/t/xcode-test-for-ios-v2-1-0/7601/1 "2019-01-10T12:54:36Z")
Fixed an issue, where exporting screenshots did not succeed in case of failing UI tests, with the error message: `Failed to update screenshot names, error: screenshot not exists`. Exported screenshots have a different format, which now contains the test identifier, `ios_simple_objcUITests-testExample_2019-01-10_11-05-49_screenshot_A0E6A26C-40C4-49E0-BBCB-47C9D023E772.png` instead of the previously used `2019-01-10_11-02-59_Screenshot of main screen (ID 1)_1_F970609B-056A-4F4F-A337-FB586A03EDE5.png`. Failing tests’ screenshots are now placed under the `Failures` directory. Fixed an issue occurring in a development environment, in the case if the XCode DerivedData directory contained different builds of the same project: `Failed to export UI test artifacts, error more than 1 project derived data dir found`. > **[bitrise-io/steps-xcode-test](https://github.com/bitrise-io/steps-xcode-test/releases/2.1.0)** > > Xcode Test step. Contribute to bitrise-io/steps-xcode-test development by creating an account on GitHub. ---
**Author:** ![rwalberg](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/rwalberg/32/751_2.png) [@rwalberg](https://discuss.bitrise.io/u/rwalberg)\ **Post date:** [January 23, 2019, 3:49pm UTC](https://discuss.bitrise.io/t/xcode-test-for-ios-v2-1-0/7601/2 "2019-01-23T15:49:29Z")
Just a heads up to anyone using 2.1.0, this caused an error exporting the coverage information to downstream steps. See [https://github.com/bitrise-io/steps-xcode-test/issues/103](https://github.com/bitrise-io/steps-xcode-test/issues/103) and [https://github.com/bitrise-io/steps-xcode-test/issues/104](https://github.com/bitrise-io/steps-xcode-test/issues/104). ---
**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\ **Post date:** [February 15, 2019, 12:46pm UTC](https://discuss.bitrise.io/t/xcode-test-for-ios-v2-1-0/7601/3 "2019-02-15T12:46:12Z")
Was fixed in 2.1.1 ( [Xcode Test for iOS v2.1.1](http://discuss.bitrise.io/t/xcode-test-for-ios-v2-1-1/7814) ) right @rwalberg? ---
**Author:** ![rwalberg](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/rwalberg/32/751_2.png) [@rwalberg](https://discuss.bitrise.io/u/rwalberg)\ **Post date:** [February 16, 2019, 11:09pm UTC](https://discuss.bitrise.io/t/xcode-test-for-ios-v2-1-0/7601/4 "2019-02-16T23:09:48Z")
Hi Viktor, I’d gone back to 2.0.0 so I wasn’t using 2.1.1 yet. I tried 2.1.1 just now and it is still broken: ``` [15:06:54]: $ xcodebuild -showBuildSettings -workspace PagerDuty.xcworkspace -scheme PagerDuty [15:06:57]: Command timed out after 3 seconds on try 1 of 4, trying again with a 6 second timeout... [15:07:01]: Unable to find any .xccoverage file. [15:07:01]: Make sure you have enabled 'Gather code coverage' setting on your scheme settings. [15:07:01]: Alternatively you can provide the full path to your .xccoverage file. [!] The exception involves the following plugins: - danger-xcov /usr/local/lib/ruby/gems/2.5.0/gems/xcov-1.5.0/lib/xcov/error_handler.rb:20:in `handle_error': (Danger::DSLError) [!] Invalid `Dangerfile` file: Error creating your coverage report - see the log above. Updating the Danger gem might fix the issue. Your Danger version: 5.11.1, latest Danger version: 5.14.0 # from Dangerfile:11 # ------------------------------------------- # > xcov.report( # scheme: 'PagerDuty', # ------------------------------------------- from /usr/local/lib/ruby/gems/2.5.0/gems/xcov-1.5.0/lib/xcov/manager.rb:45:in `parse_xccoverage' from /usr/local/lib/ruby/gems/2.5.0/gems/danger-xcov-0.4.1/lib/danger_plugin.rb:64:in `produce_report' from /usr/local/lib/ruby/gems/2.5.0/gems/danger-xcov-0.4.1/lib/danger_plugin.rb:36:in `report' from Dangerfile:11:in `eval_file' ``` Thanks for your efforts! ---
**Author:** ![fehersanyi-bitrise](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/fehersanyi-bitrise/32/1912_2.png) [@fehersanyi-bitrise](https://discuss.bitrise.io/u/fehersanyi-bitrise)\ **Post date:** [February 18, 2019, 9:13am UTC](https://discuss.bitrise.io/t/xcode-test-for-ios-v2-1-0/7601/5 "2019-02-18T09:13:08Z")
Hy @rwalberg So is it working with 2.0 and fails with 2.1 and up? ---
**Author:** ![rwalberg](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/rwalberg/32/751_2.png) [@rwalberg](https://discuss.bitrise.io/u/rwalberg)\ **Post date:** [February 18, 2019, 2:46pm UTC](https://discuss.bitrise.io/t/xcode-test-for-ios-v2-1-0/7601/6 "2019-02-18T14:46:29Z")
Yep, it works with 2.0.0, fails on 2.1.0, fails on 2.1.1. ---
**Author:** ![fehersanyi-bitrise](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/fehersanyi-bitrise/32/1912_2.png) [@fehersanyi-bitrise](https://discuss.bitrise.io/u/fehersanyi-bitrise)\ **Post date:** [February 19, 2019, 9:33am UTC](https://discuss.bitrise.io/t/xcode-test-for-ios-v2-1-0/7601/7 "2019-02-19T09:33:05Z")
Thank you for confirming! ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)\ **Post date:** [April 10, 2019, 12:54pm UTC](https://discuss.bitrise.io/t/xcode-test-for-ios-v2-1-0/7601/8 "2019-04-10T12:54:36Z")
This topic was automatically closed after 90 days. New replies are no longer allowed.