fastlane: Scan cannot find simulators

New Issue Checklist

Issue Description

Scan cannot find simulators

Complete output when running fastlane, including the stack trace and command used
bundle exec scan --device "iPhone 6s"
[17:01:54]: Ignoring 'iPhone 6s', couldn't find matching simulator
[17:01:54]: Couldn't find any matching simulators for '["iPhone 6s"]' - falling back to default simulator
+-----------------------+--------------------------------------------------------------------------+
|                                     Summary for scan 0.11.2                                      |
+-----------------------+--------------------------------------------------------------------------+
| device                | iPhone 6s                                                                |
| workspace             | ./Foobar.xcworkspace                                                   |
| scheme                | Foobar                                                                 |
| derived_data_path     | .../DerivedData/Foobar-... |
| clean                 | false                                                                    |
| code_coverage         | false                                                                    |
| address_sanitizer     | false                                                                    |
| skip_build            | false                                                                    |
| output_directory      | ./fastlane/test_output                                                   |
| output_types          | html,junit                                                               |
| buildlog_path         | ~/Library/Logs/scan                                                      |
| open_report           | false                                                                    |
| skip_slack            | false                                                                    |
| slack_only_on_failure | false                                                                    |
| use_clang_report_name | false                                                                    |
+-----------------------+--------------------------------------------------------------------------+

[17:05:15]: $ set -o pipefail && env NSUnbufferedIO=YES xcodebuild -workspace ./Foobar.xcworkspace -scheme Foobar -destination 'platform=iOS Simulator,id=2732721F-BB19-4019-8594-56B1F1EE4981' -derivedDataPath '/Users/ragecode/Library/Developer/Xcode/DerivedData/Foobar-byiivdizifwfoqejwrhhgjtcjuly' build test | tee '/Users/ragecode/Library/Logs/scan/Foobar-Foobar.log' | xcpretty 

Output of instruments -s:

instruments -s
Known Devices:
ragebookpro [F7FFE450-8C45-56F6-8AC9-2FD8768657F5]
Apple TV 1080p (9.2) [5FB0ABEA-9B96-4AB0-B85E-E65EFA3E17CF] (Simulator)
iPad 2 (9.3) [8D9B2FA3-95EE-41F8-92C6-C35C765C9242] (Simulator)
iPad Air (9.3) [76486C39-4F1F-437B-A8F7-40A29FB1BC4E] (Simulator)
iPad Air 2 (9.3) [4B07F52F-D02C-4DB9-A35A-09F93639BF52] (Simulator)
iPad Pro (9.3) [B813E2BE-E780-496D-AB3A-B75FA0AC8D93] (Simulator)
iPad Retina (9.3) [FF1CB7C6-60B3-4C96-BCF0-E8717590C6AD] (Simulator)
iPhone 4s (9.3) [4A0C9D6C-35B9-4161-B67D-FCFDAEFDE583] (Simulator)
iPhone 5 (9.3) [290A73D6-2334-4B19-B22C-6DF0023549E2] (Simulator)
iPhone 5s (9.3) [2732721F-BB19-4019-8594-56B1F1EE4981] (Simulator)
iPhone 6 (9.3) [60ED7DD2-EA31-43E9-BA72-F2A960F9CA6E] (Simulator)
iPhone 6 Plus (9.3) [4CE88860-2EC2-4A0B-9794-310E9D8B25D4] (Simulator)
iPhone 6s (9.3) [3F5C6BBB-96BB-4A75-AF61-6AE993F04289] (Simulator)
iPhone 6s (9.3) + Apple Watch - 38mm (2.2) [C1D65072-E256-4438-98C6-17996190C888] (Simulator)
iPhone 6s Plus (9.3) [B3DF44A4-D531-4FF7-9ACA-C82BEF01E2DC] (Simulator)
iPhone 6s Plus (9.3) + Apple Watch - 42mm (2.2) [EE2BEDA7-700D-4366-97D9-DFF59AE6BDBA] (Simulator)
Known Templates:
"Activity Monitor"
"Allocations"
"Automation"
"Blank"
"Cocoa Layout"
"Core Animation"
"Core Data"
"Counters"
"Energy Log"
"File Activity"
"GPU Driver"
"Leaks"
"Metal System Trace"
"Network"
"OpenGL ES Analysis"
"System Trace"
"System Usage"
"Time Profiler"
"Zombies"
"~/Library/Application Support/Instruments/Templates/MyTemplate.tracetemplate"

Configuration Files

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

N/A

Environment

scan version (run scan -v):

0.11.2

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

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

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Reactions: 1
  • Comments: 25 (10 by maintainers)

Most upvoted comments

The biggest problem, of which this one is a small but significant symptom, is that almost every new version of these tools breaks existing workflows.

@SandyChapman thanks it works now, it used to work using the device name in that way.

@KrauseFx : Works for me.

Short update on this, I just reviewed and merged https://github.com/fastlane/fastlane/pull/5746 (thanks @jdhealy for providing this PR 👍) and published a follow-up PR with https://github.com/fastlane/fastlane/pull/6054.

Please give the latest version from the master branch a try and let me know if that works for you. Once I get a +1 I’ll do a new release for this 🚀

Hey everyone, really sorry there is some difficulties with scan. I’m looking into https://github.com/fastlane/fastlane/pull/5746 right now, and make sure all edge cases are covered.

Thanks for your feedback @postmechanical, I can understand your frustration. The goal with fastlane is to never do any breaking changes, unless there is a major version bump involved. We haven’t done any breaking release since the 1.0 release of each of the tools, however things might go wrong, especially for more advanced setups, where some features or tools are used differently than originally intended.

For this scan issue, the error was caused by an Xcode update, changing the way simulators are printed to the terminal, and therefore breaking the simulator selection of scan. We’re usually really fast updating the tools to work with the latest releases of Apple (both Xcode, and web services like iTunes Connect), however for some reason we misjudged the priority of this issue and put it aside initially.

I’m really sorry this happened, and we’re working hard to provide a new release with a fix as soon as possible 👍