Re-enable reject_build_waiting_for_review
after Fastlane upgrade
#23374
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follows up on #23118 (comment) now that @AliSoftware's fastlane/fastlane#21995 has landed and shipped by re-enabling
reject_build_waiting_for_review
I opened this against the release branch so we can see it in action sooner rather than later. However, to properly test this one would have to artificially submit two betas in short succession.
Luckily, @AliSoftware already tested the fix in the real world (see fastlane/fastlane#21995 description) so we can be quite confident in merging. Or, at least, as confident as anyone can be when interacting with the brittle ASC API...
Regression Notes
PR submission checklist:
RELEASE-NOTES.txt
if necessary. N.A.UI changes testing checklist: Not a UI PR.