axiom-build-debugging

To resolve the "No such module" Xcode build error, you must diagnose dependency resolution failures by checking lockfiles, cache states, and environment settings. This Skill provides a structured diagnostic plan to identify the root cause and apply deterministic remediation steps.

iOS CI vs local build discrepancies usually stem from dependency resolution drift. You can fix this by enforcing environment reproducibility checks to align lockfiles, cache states, and Xcode settings across both environments, ensuring deterministic dependency resolution.

The best way to debug "Multiple commands produce" Xcode errors is through systematic dependency analysis. By verifying your Package.resolved or Podfile.lock and inspecting cache states, you can isolate the conflicting dependency targets and apply guided remediation steps.

Yes, you can use this approach for both SwiftPM and CocoaPods. The systematic debugging process analyzes lockfiles, environment settings, and cache states across package managers to diagnose iOS build failures and suggest deterministic remediation strategies.

To diagnose an iOS dependency build failure, you need to provide the failing Xcode build logs, the relevant Podfile.lock or Package.resolved file, and the exact error message. This allows the Skill to generate a structured diagnostic plan and recommend targeted fixes.