Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

No scheme named 'MyScheme' found (Xcode 15.4)

Open
#569 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
devtools, testing

Research direction

Start at lib/slather/project.rb, around find_binary_files (line 517 in the reported stack trace), and trace how the project and scheme configuration are read. Reproduce with the supplied Slather YAML and Xcode 15.4 setup, then check how shared schemes are discovered. Done means slather coverage recognizes the existing MyScheme and proceeds without this error.

Written by the indexing model from the issue text.

Description

Hi, we are currently trying to generate reports with Slather using macOS 14 and Xcode 15.4. We added ruby and installed slather. This is our yml in our root directory:

coverage_service: gutter_json
xcodeproj: ./MyProject.xcodeproj
scheme: MyScheme
build_directory: ./Build
configuration: TestDebug
workspace: ./MyWorkspace.xcworkspace
verbose: true
output_directory: slather-report
ignore:
  - Pods/*
  - Carthage/*

We then execute the command slather coverage in our CI. Also, we plan to upload the report to Codecov.
But when trying this, it gives us this error always:

/Users/runner/hostedtoolcache/Ruby/3.0.7/arm64/lib/ruby/gems/3.0.0/gems/slather-2.8.3/lib/slather/project.rb:517:in `find_binary_files': No scheme named 'MyScheme' found in /Users/runner/work/ios-app/ios-app/MyProject.xcodeproj (StandardError)

I'm sure the scheme exists and its being shared, and I'm not sure what else to do. Thanks in advance.

Dominant language
Ruby
Stars
1.6k
Forks
239
Avg merge
10h 19m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SlatherOrg/slather

All issues in SlatherOrg/slather

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.