scan hangs after running tests (process doesn't exit; I'm not returned to the shell) about scan HOT 7 CLOSED

I have exactly same problem with scan, process just hangs

from scan.

Hi @alex-hunsley-zonal,

I'm trying to reproduce this error, so, could you share basic info about your environment. More precisely, version info:

1 - Ruby
2 - Mac OS X
3 - iOS simulator
4 - Xcode
5 - Fastlane

In addition, could you share the relevant output when running scan on your machine with command of the xcode?

from scan.

I had the same problem. And below are my details:
Ruby ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-darwin15]
Mac OS 10.11.2
iOS simulator: iPhone 6s
Xcode: 7.2 (7C68)
Fastlane: 1.53.0
Scan: 0.4.1 (Same problem when I updated to 0.4.2)

| Summary for scan 0.4.1 |
+-----------------------+------------------------------------------------+
| workspace | ./guardian.xcworkspace |
| device | iPhone 6s |
| scheme | guardian-qa |
| clean | true |
| code_coverage | false |
| output_directory | ./fastlane/test_output |
| output_types | html,junit |
| buildlog_path | ~/Library/Logs/scan |
| open_report | false |
| xcargs | -derivedDataPath build -enableCodeCoverage YES |
| skip_slack | false |
| slack_only_on_failure | false |

from scan.

I am seeing the same behavior as described above.

1. Ruby: ruby-2.0.0-p576 (I used RVM to set it up)
2. Mac OS: 10.11.2
3. iOS Simulator: iPhone 6s
4. Xcode 7.2.1
5. fastlane_core (0.36.1)
6. scan 0.4.2

from scan.

running into the same issue. details of my setup below

1. Ruby
2. Mac OS: 10.11.4
3. iOS Simulator: iPhone 6s
4. Xcode 7.2.1
5. Fastlane: 1.53.0
6. Scan: 0.4.2

Scan summary

+-----------------------+----------------------------+
|               Summary for scan 0.4.2               |
+-----------------------+----------------------------+
| workspace             | ./App.xcworkspace |
| device                | iPhone 6s                  |
| scheme                | Disneyland                 |
| clean                 | true                       |
| code_coverage         | false                      |
| output_directory      | ./test_output              |
| output_types          | html                       |
| buildlog_path         | ~/Library/Logs/scan        |
| open_report           | false                      |
| skip_slack            | false                      |
| slack_only_on_failure | false                      |
+-----------------------+----------------------------+

from scan.

I had the same problem when my scheme is containing (activated for testing) a test target that is empty (no test classes at all).

And by the way, the Xcode CI has the same problem as well.

from scan.

This issue was migrated to fastlane/fastlane#1939. Please post all further comments there.

fastlane is now a mono repo, you can read more about the change in our blog post. All tools are now available in the fastlane main repo 🚀

from scan.