Xcode “Multiple commands produce” the same output
Find the duplicate build producers before removing a build phase or file membership.
Xcode found more than one build command claiming the same output path. Expand the issue to see both producers, then correct the duplicate resource, copy phase, or script output declaration that applies to your target.
Try these fixes in order
Read both producer lines
Open the full Issue navigator detail and note the output path and the two target or build-phase commands. A generic clean build will not explain why two producers exist.
Inspect the named target’s phases
Check Compile Sources, Copy Bundle Resources, Embed Frameworks, and Run Script phases. Look for a file or framework added twice, or a script that declares the same output as another phase.
Remove only the duplicate producer
If a resource was copied twice, remove its unintended target membership or duplicate phase entry. If a custom script creates the file, adjust its declared outputs and avoid writing into a path owned by another build command.
Rebuild and check packaging
Clean the build folder after correcting the configuration, then rebuild the affected scheme. Verify the resource or framework still appears once in the product and run the app or tests.
Interpret what you see
The log names Info.plist twice
What it suggests: Xcode may generate a plist and also copy a source plist to the same output.
Next check: Check Generate Info.plist File and Copy Bundle Resources; keep one intended producer.
A generated asset or source file is duplicated
What it suggests: Two build phases or targets may write to the same path.
Next check: Expand both producer lines and remove the stale duplicate reference, not the output file itself.
A package or build script is involved
What it suggests: Its declared output may collide with another build step.
Next check: Inspect script output declarations and target dependencies to give each producer a unique output.
Why this happens
- The same resource or framework is included twice in build phases.
- A custom script and Xcode phase declare the same output file.
Still not working?
Do not delete random DerivedData folders as the sole fix. If a dependency integration regenerated project settings, compare the project-file diff and its installation instructions.
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.