MobileNativeFoundation / MobileNativeFoundation/rules_xcodeproj
Bug: Indexing issues with Explicit Module Builds
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 626
- Forks
- 124
- PR merge metrics
- No merged PRs in 30d
Description
Description
BwB builds are successful with explicit module feature enabled but indexing fails. When I make the paths in the explicit module map.json absolute, the indexing is successful. Looks like the working directory is not being respected.
Note: this is an index file job.
Reproduction steps
bazel run :xcodeproj && xed StressTester.xcodeproj
index_repro-lat.zip
Expected behavior
Successful index builds.
rules_xcodeproj version
1.7.1
Xcode version
14.3.1
Bazel version
6.2.1
rules_apple version
No response
rules_swift version
No response
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Run bazel run :xcodeproj && xed StressTester.xcodeproj with the attached index_repro-lat.zip, then inspect how the explicit module map.json paths are resolved during the index file job. Compare relative and absolute paths and verify that the generated project completes indexing successfully with the listed Bazel and Xcode versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100