fastlane: Scan hangs on touching .xctests

New Issue Checklist

Issue Description

Sometimes my bamboo CI hangs when executing scan on touching the .xctests files. Don’t know what the real problem is here 😦

Complete output when running fastlane, including the stack trace and command used
08-Aug-2016 15:13:43    [15:13:43]: ▸ Compiling PriceTests.swift
08-Aug-2016 15:13:43    [15:13:43]: ▸ Linking MyProject_Tests
08-Aug-2016 15:13:43    [15:13:43]: ▸ ⚠️  ld: directory not found for option '-F/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.3.sdk/Developer/Library/Frameworks'
08-Aug-2016 15:13:43    [15:13:43]: ▸ Generating 'MyProject_tests.xctest.dSYM'
08-Aug-2016 15:13:43    [15:13:43]: ▸ Running script '[CP] Embed Pods Frameworks'
08-Aug-2016 15:13:45    [15:13:45]: ▸ Running script '[CP] Copy Pods Resources'
08-Aug-2016 15:13:45    [15:13:45]: Running Tests: ▸ Touching MyProject_tests.xctest

Configuration Files

Please copy the complete content of your Fastfile and any other configuration files you use below:

Fastfile:

scan \
    --workspace PATH_TO_WORKSPACE \
    --scheme MyProject-Tests \
    --xcargs "-derivedDataPath ../build" \
    --buildlog_path ../logs/scan \
    --output_directory ../test-reports \
    --device "iPhone 6s 9.3" \
    --sdk iphonesimulator \
    --code_coverage \
    -r

Environment

fastlane version (run fastlane -v): scan 0.10.1

Do you use bundler to execute fastlane (i.e. bundle exec fastlane)? nope

Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)? nope

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 28 (5 by maintainers)

Most upvoted comments

Newest input from me here. This seems not a problem from scan. Just right now I got the same issue directly in Xcode. It’s hanging right at the touch .xctest. Don’t know exactly why.

I cleaned my build folder and it’s working again like a charm. Maybe we need to clean the project before?

Am 06.09.2016 um 20:32 schrieb Todd Burner notifications@github.com:

Hi @pawelus Can you try removing the output_types parameter from your first scanfile? Thanks!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.