realm / realm/SwiftLint

Error: No lintable files found at paths: ''

Open
#5,850 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

help
Dominant language
Swift
Stars
19.7k
Forks
2.3k
Avg merge
1d 1h
Merged PRs (30d)
11

Description

New Issue Checklist
Bug Description

I have followed the installation instructions from the github readMe, and when I run swiftlint form the terminal, it correctly outputs the field with linting warnings/errors in them. However, when I add the build script to the Build Phase as 'SwiftLint'm using the bash code found in the ReadME, I consistently get this error:

Linting Swift files in current working directory
Error: No lintable files found at paths: ''
Command PhaseScriptExecution failed with a nonzero exit code

Mention the command or other SwiftLint integration method that caused the issue. Include stack traces or command output.

Linting Swift files in current working directory
Error: No lintable files found at paths: ''
Command PhaseScriptExecution failed with a nonzero exit code

Environment
  • SwiftLint version (run swiftlint version to be sure)
  • 0.57.0
  • Xcode version (run xcodebuild -version to be sure)
  • Xcode 16.1
  • Build version 16B40
  • Installation method used (Homebrew, CocoaPods, building from source, etc)
  • I used HomeBrew to install swiftlint
  • Configuration file:
I do not have a yml file set-up for configurations since I am just installing swiftlint for the first time.```

Are you using [nested configurations](https://github.com/realm/SwiftLint#nested-configurations)? If so, paste their
relative paths and respective contents.
I am not using nested configurations - i am just starting a swift project for the first time and am surprised that Swift does not have a plugin like 'Prettier' for VSCode.

Contributor guide

Open the contributing guide

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.

Research direction

Start with the SwiftLint README build-phase integration script and reproduce it in an Xcode Build Phase using the reported SwiftLint 0.57.0 and Xcode 16.1 environment. Check why the script receives an empty lint path; done means the build phase runs without the “No lintable files found” error and lints the project’s Swift files.

Written by the indexing model from the issue text.

Assessment

Tech stack
bash, swift
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.