Stop installing the deprecated tools package - #538
Merged
ViliusSutkus89 merged 1 commit intoSep 17, 2026
Merged
ViliusSutkus89 merged 1 commit into
ViliusSutkus89 merged 1 commit into
Conversation
Google no longer serves the `tools` package: it is gone from repository2-3.xml, so `sdkmanager tools` fails with "Failed to find package 'tools'" and takes the whole action down with it. - Drop `tools` from the default value of the `packages` input, leaving `platform-tools`. The command line tools that replaced it are already installed by this action, and there is no bare `cmdline-tools` package path to install instead (only versioned ones, e.g. `cmdline-tools;20.0`). - Skip `tools` with a warning when it is requested explicitly, so the many workflows that pass `packages: 'tools platform-tools'` keep working instead of failing. - Update the README accordingly. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
enlightenedpie
approved these changes
Sep 16, 2026
|
calling this to your attention @ViliusSutkus89, lots of CI failures today because of it. |
|
@baywet The temp solution is to add a "with" block to the action in your pipeline: This removes the failing |
|
@enlightenedpie Thank you for the additional information. This is what I've done at the time I posted this message. But I figured it'd be far easier for the community if the action is fixed, rather than having to investigate/find the issue/update the workflow |
Collaborator
|
Hey folks. Let me look into this |
jjrasche
added a commit
to jjrasche/factoredui
that referenced
this pull request
Sep 18, 2026
…op suite setup-android v4.0.1 installs the `tools` package by default, which Google stopped serving, so sdkmanager exits 1 before a single Gradle task runs (every run since 2026-09-17). v4.0.2 drops `tools` from the defaults (android-actions/setup-android#538); pinned to v4.0.4 by SHA in both workflows. Behind that, ci.yml had been red since August: it ran desktopTest behind a --tests allowlist of 38 tests, and the suite floor of 100 fails any run that narrow. The publish workflow already runs the whole suite and published 0.19.0 green on it, so ci.yml now matches it — one unfiltered desktopTest, which includes the render-correctness gate — and builds kotlin-compose-capture as publish does.
gwennlbh
pushed a commit
to cigaleapp/cigale
that referenced
this pull request
Sep 21, 2026
##### [vv4.0.4](https://github.com/android-actions/setup-android/releases/tag/v4.0.4) Add cmdline-tools 22.0 macOS URL changed for 22.0+. Fixes [#536](android-actions/setup-android#536) ##### [vv4.0.3](https://github.com/android-actions/setup-android/releases/tag/v4.0.3) Updated dependencies. npm vulnerability list solved. ##### [vv4.0.2](https://github.com/android-actions/setup-android/releases/tag/v4.0.2) Fix for removed tools package. Thanks [@vbuberen](https://github.com/vbuberen) for the pull request [#538](android-actions/setup-android#538) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.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
4 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.
Google no longer serves the
toolspackage, so attempts to installtoolsfails with "Failed to find package 'tools'" and takes the whole action down with it as described in the #537 and I bumped into this as well:In this PR the default set of packages changes to only include
platform-tools, which should be enough for most tasks wheresetup-androidAction it used. The change is supposed to be safe also because most of thetoolsare already already on$PATHviacmdline-tools/<ver>/bin, which this action has always added —apkanalyzer,avdmanager,lint,screenshot2,sdkmanager, plusd8/r8/retrace/resourceshrinker/profgen. The emulatorsplit out into its own
emulatorpackage.Changes
toolsfrom the default value of thepackagesinput, leavingplatform-tools. The command line tools that replaced it are already installed by this action, and there is no barecmdline-toolspackage path to install instead (only versioned ones, e.g.cmdline-tools;20.0).toolswith a warning when it is requested explicitly, so the many workflows that passpackages: 'tools platform-tools'keep working instead of failing.Tested the change on workflows that build Android app for some Flutter projects - worked fine.
Fixes #537