XcodeGraph fails to parse Xcode projects with static linked library targets

[HeEAaD]

The XcodeGraph library fails to parse Xcode projects that contain statically linked library targets.

Steps to reproduce

1. Have a Xcode project (e.g. iOS app). Example project: Example.zip
2. Add a static library target
3. Link this static library target to the main project target (e.g. app)
4. Run tuist graph in the project root.

Expected result: A graph image file gets created in the project root.
Actual result: An error is thrown:

✖ Error 
  Missing or invalid file path for 'PBXBuildFile': Unknown. 

  Sorry this didn’t work. Here’s what to try next: 
   ▸ If the error is actionable, address it
   ▸ If the error is not actionable, let's discuss it in the Troubleshooting & how to
   ▸ If you are very certain it's a bug, file an issue
   ▸ Check out the logs at /Users/steffen/.local/state/tuist/logs/DC67880D-FF7A-42ED-9600-18A5273B981B.log

DC67880D-FF7A-42ED-9600-18A5273B981B.log

$ tuist version  
4.119.1

Probable Root Cause

PBXFrameworksBuildPhaseMapper.mapFrameworkDependency(:xcodeProj:projectNativeTargets:) tries to find project targets based on framework / library names.
For this, it replaces ".framework" from file refs:

XcodeGraph/Sources/XcodeGraphMapper/Mappers/Phases/PBXFrameworksBuildPhaseMapper.swift

Line 67 in f080015

let name = path.replacingOccurrences(of: ".framework", with: "")

It doesn't do the same for static library product file refs (e.g. libFoo.a). Thats why it tries to search for a target libFoo.a instead of Foo.

[dosubot]

Hi @HeEAaD! I'm Dosu and I’m helping the XcodeGraph team.

This is a confirmed bug in XcodeGraph: when parsing Xcode projects with statically linked library targets, the PBXFrameworksBuildPhaseMapper only strips the .framework suffix from file references and does not handle static library references like libFoo.a. As a result, it tries to resolve a target named libFoo.a instead of Foo, which fails and leads to the "Missing or invalid file path for PBXBuildFile" error during graph generation. This matches your root cause analysis and is visible in the current implementation of PBXFrameworksBuildPhaseMapper.swift (source).

There are no existing issues, documentation, or merged pull requests that address or fix this bug. Recent changes in the repository have focused on static frameworks and resource support, but not on static library dependency resolution.

There is no official workaround at the moment. As a code-level workaround, you could try modifying PBXFrameworksBuildPhaseMapper to also strip the lib prefix and .a suffix when resolving static library targets. Otherwise, monitoring the repository for updates or contributing a fix would be the best path forward.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}