Repository navigation
ci: stop installing the obsolete tools SDK package - #112
Merged
RapierXbox merged 1 commit intoSep 24, 2026
Merged
Conversation
Every workflow run that actually starts fails in "Set up Android SDK",
before Gradle is ever invoked:
sdkmanager tools
Warning: Failed to find package 'tools'
Error: The process '.../sdkmanager' failed with exit code 1
android-actions/setup-android installs `tools platform-tools` by default.
Google removed `tools` from the SDK repository, so sdkmanager exits
non-zero and takes the step with it.
Pass an empty package list. Both workflows already install what they
need (platform-tools, the platform and build-tools) in the next step.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
2 participants
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.
Problem
Every workflow run that actually starts fails in Set up Android SDK, before Gradle is invoked:
android-actions/setup-androidinstallstools platform-toolsby default. Google removedtoolsfrom the SDK repository, sosdkmanagerexits non-zero and fails the step — regardless of what the PR changes.This is easy to miss right now: most recent runs never reach this point. PRs from first-time contributors sit at
action_requiredwaiting for approval and reportfailurewith no jobs at all, which looks like the same red X. Run 35842969848 is one that did start, and it dies here.Change
Pass an empty package list to the action. Nothing is lost: both workflows already install what they need in the very next step —
pr-apk.yml:platform-tools,platforms;android-36,build-tools;36.0.0release-apk.yml:platform-tools,platforms;android-35,build-tools;35.0.0Both are fixed, so the next release build does not hit the same wall.
Note
The release workflow has never been exercised with this change, since it only runs on a release. The edit is identical to the PR workflow's and the following step is the same shape, but it is worth knowing that the first real verification will be the next release.
🤖 Generated with Claude Code