Xcode “Build input file cannot be found”
Locate the missing path in the build phase or generated-file step instead of creating an empty placeholder file.
Locate the missing path in the build phase or generated-file step instead of creating an empty placeholder file.
Try these fixes in order
Record the exact path
Read the build error and determine whether the file is checked into the project or generated during a previous phase.
Inspect target phases
In Build Phases, find a stale Compile Sources, Copy Files, or Run Script input referring to the old path.
Check generation order
If a script creates the file, confirm it runs before the consuming phase and declares its inputs and outputs correctly.
Correct the project reference
Restore or regenerate the real file, or remove an obsolete reference, then build the same configuration.
Interpret what you see
The missing path was renamed in Git
What it suggests: The project still references the old file location.
Next check: Update the build phase or file reference to the real path and review case-sensitive spelling.
The missing input is generated by a script
What it suggests: Its producer may not run before the consumer or may declare the wrong output.
Next check: Inspect script order and declared input/output paths; fix the generator rather than adding a placeholder.
Only CI fails
What it suggests: An ignored or uncommitted input may exist only on a developer Mac.
Next check: Check whether the file is tracked and available at the CI commit.
Why this happens
- A project reference points to a renamed or deleted file.
- A generator did not create its declared output before the build consumed it.
Still not working?
A temporary empty file can hide the real issue and produce a broken archive. Check the source control history for renamed assets.
Official sources
These steps are based on the linked documentation and general diagnostics. BugMedic has not independently tested every product and system configuration. Review commands before running them.