Open thiagohmcruz opened 5 months ago
The only two ways I was able to avoid this:
transition_support.apple_rule_transition
as an incoming edge transition in the legacy_xcodeproj.bzl
=> xcodeproj
ruletransition_support.apple_platform_split_transition
as an outgoing edge transition in the same rule above for its deps
attributeBoth "hacks" require the platform_type
and minimum_os_version
attributes to be set to something in the rule (rules_apple
requirement) and I'm debating if this is even the right approach here. I doesn't make a lot of sense for the project to be opinionated on platform_type
/minimum_os_version
.
Given that this generator is getting more and more in "life support" mode due to most folks moving to rules_xcodeproj
one might want to avoid setting apple.experimental.tree_artifact_outputs=1
when building from this generator as a workaround as I'm not convinced that its worth investing time in adjusting the rule to run well with the latest transitions-related changes that landed in rules_ios
recently (e.g. 1, 2, 3).
We might want to simply close this once we deprecate the legacy generator.
Invoke
xcodebuild
xcodebuild -project tests/ios/xcodeproj/Test-Imports-App-Project.xcodeproj -scheme TestImports-Unit-Tests -destination "id=SOME_VALID_SIM_ID" -PBXBuildsContinueAfterErrors=0 test
The issue doesn't happen if
apple.experimental.tree_artifact_outputs
is set to0
.