Repository navigation
Fix Android SDK tool lookup in release jobs - #6
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The first Android release run failed before building with
sdkmanager: command not found(exit 127): run 42799619037. Both release jobs relied onsdkmanagerbeing on the runner's PATH.Invoke
"$ANDROID_HOME/cmdline-tools/latest/bin/sdkmanager"in the build and signing jobs, matching the GitHub runner's SDK layout. The requested Build Tools version and signing protections are unchanged.Validation: reproduced exit 127 with the SDK tool absent from PATH, then executed both corrected workflow commands against a controlled SDK layout (including spaces in the path) and checked the exact package argument. Workflow YAML parses; all 13 release regressions pass; React Doctor and AISlop both score 100/100, with ten dependency audits clean. Hosted CI passed for
1f628342e8e928ed843fa2e5017eb58ce321bfc1: branch run and PR run, each with 15 successful jobs and the main-only score badge skipped. Both native compiles passed; hosted quality scores are 100/100 with ten audits clean. The production build and signing flow still require a fresh run from main after this fix is merged and main CI passes; rerunning the old failed run would use its old workflow revision.