MobileNativeFoundation / MobileNativeFoundation/rules_xcodeproj
Bug: Target shows multiple targets when running custom configurations (Simulator, Device)
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 626
- Forks
- 124
- PR merge metrics
- No merged PRs in 30d
Description
Description
When employing custom configurations, the target name includes (Simulator, Device) when it should omit.
Reproduction steps
Create a top_level_target that is impacted by multiple configurations via xcode_configurations
Expected behavior
No (Simulator, Device)
rules_xcodeproj version
14.1
Xcode version
14.3
Bazel version
6.2
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
Reproduce the issue by creating a top_level_target affected by multiple xcode_configurations, then inspect the generated Xcode project target names. The fix is complete when custom configurations no longer add the “(Simulator, Device)” suffix, while the target remains correctly generated for the reported Swift, Xcode, and Bazel versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system, devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100