In-depth Analysis and Solutions for Multiple Commands Produce Error in Xcode 10

Error Phenomenon and Background

In Xcode 10 environments, developers frequently encounter compilation errors similar to the following:

error: Multiple commands produce '/Users/uesr/Library/Developer/Xcode/DerivedData/OptimalLive-fxatvygbofczeyhjsawtebkimvwx/Build/Products/Debug-iphoneos/OptimalLive.app/Info.plist':
1) Target 'OptimalLive' has copy command from '/Users/uesr/Desktop/workSpace/SEALIVE/SeaLive1.1/OptimalLive/Info.plist' to '/Users/uesr/Library/Developer/Xcode/DerivedData/OptimalLive-fxatvygbofczeyhjsawtebkimvwx/Build/Products/Debug-iphoneos/OptimalLive.app/Info.plist'
2) Target 'OptimalLive' has copy command from '/Users/uesr/Desktop/workSpace/SEALIVE/SeaLive1.1/OptimalLive/Server/Masonry/Info.plist' to '/Users/uesr/Library/Developer/Xcode/DerivedData/OptimalLive-fxatvygbofczeyhjsawtebkimvwx/Build/Products/Debug-iphoneos/OptimalLive.app/Info.plist'
3) Target 'OptimalLive' has process command with input '/Users/uesr/Desktop/workSpace/SEALIVE/SeaLive1.1/OptimalLive/Info.plist'

Root Cause Analysis

The essence of this error lies in multiple commands within the Xcode build system attempting to generate the same output file. In Xcode 10's new build system, the system strictly checks for command conflicts, whereas duplicate commands that might have been ignored in older versions now trigger errors.

Specifically for Info.plist files, common causes include:

• Info.plist files being incorrectly added to the Copy Bundle Resources phase in project configuration
• Multiple targets or subprojects containing Info.plist files with the same name
• Duplicate file references introduced during third-party library or framework integration

Primary Solution

According to the high-scoring Stack Overflow answer, the most effective solution is to inspect and clean up file references in build phases:

1. Open the project in Xcode and select the corresponding target
2. Navigate to the Build Phases tab
3. Locate the Copy Bundle Resources phase
4. Check for and remove any Info.plist files contained within

Here is a specific operational code example:

// In Xcode project configuration, proper Info.plist handling should only be configured
// through the Info.plist File path in Build Settings, not duplicated in Copy Bundle Resources

Build System Differences Analysis

Xcode 10 introduced a new build system that differs significantly from Xcode 9's legacy system in file processing logic. The new system employs stricter dependency checking and conflict detection mechanisms, explaining why projects that compiled successfully in Xcode 9 encounter errors in Xcode 10.

From a technical implementation perspective, the new build system uses graph-based dependency management to more precisely track file input-output relationships. When multiple commands producing the same output are detected, the system immediately reports an error to prevent potential data inconsistency issues.

Extended Scenarios and Considerations

In practical development, similar Multiple commands produce errors can occur in various scenarios:

Multi-target Projects: When projects include Watch apps or extensions, ensure duplicate Info.plist file references are removed from the Copy Bundle Resources of each target.

Third-party Integration: As mentioned in reference articles, similar bundle file conflicts can occur when integrating Google Utilities or other third-party frameworks. The solution is similar, requiring inspection and cleanup of duplicate file references.

Flutter Projects: As shown in reference articles, Flutter projects may encounter multiple command conflicts with framework files during archiving, typically related to CocoaPods integration and build phase configuration.

Preventive Measures and Best Practices

To prevent such errors, the following best practices are recommended:

• Regularly inspect project Build Phases configuration to ensure no unnecessary file references
• When using third-party libraries, carefully read integration documentation to understand potential file conflicts
• When upgrading or migrating projects, prioritize testing under the new build system
• Establish standard project templates to avoid duplicate file configuration errors

Technical Deep Dive

From the perspective of Xcode build system evolution, the strict checking of Multiple commands produce errors reflects Apple's emphasis on build reliability. The new build system ensures build correctness through the following mechanisms:

• Precise Dependency Tracking: The system maintains a complete file dependency graph, capable of detecting potential conflicts
• Parallel Build Optimization: The new system supports better parallel builds but requires stricter conflict detection
• Incremental Build Improvements: Improved accuracy of incremental builds reduces unnecessary recompilation

Understanding these underlying mechanisms helps developers better diagnose and resolve build issues, rather than just applying superficial solutions.