MobileNativeFoundation / MobileNativeFoundation/rules_xcodeproj
Bug: BwB UI test targets are code signed twice
Open
Nobody has claimed this yet.
bug
BwB
- Dominant language
- Swift
- Stars
- 626
- Forks
- 124
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Both Bazel and Xcode code sign UI test targets. This is because we need to enable code signing to get Xcode to sign the test runner.
Expected behavior
Only the test runner is code signed by Xcode, not the test target.
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
Start by locating the Bazel and Xcode project-generation paths for UI test targets and inspect where code-signing settings are applied. Compare the generated test target with the test runner; done means only the test runner is signed by Xcode while the UI test target is not signed twice.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100