macOS CI machines have outdated Android build tools (30.0.3 instead of 36.1.0)

[shs96c]

The macOS CI machines appear to have Android build tools version 30.0.3 installed. That's surprising because the setup script macos/mac-android.sh specifies version 36.1.0. This causes builds using rules_android v0.7.1+ to fail, as they require build tools 35.0.0 or newer.

Reproduction

Any project using rules_android >= 0.7.1 with android_sdk_repository_extension will fail on macOS CI.

Example failure: https://buildkite.com/bazel/rules-jvm-external/builds/5625#019c426f-06f3-4b7c-af28-64068f2c7b4c

PR that triggered it: bazel-contrib/rules_jvm_external#1536

Error Message

ERROR: .../external/rules_android+/rules/android_sdk_repository/rule.bzl:139:13:
An error occurred during the fetch of repository 'rules_android++android_sdk_repository_extension+androidsdk':
   Traceback (most recent call last):
        File ".../external/rules_android+/rules/android_sdk_repository/rule.bzl", line 139, column 13, in _android_sdk_repository_impl
                fail("Bazel requires Android build tools version %s or newer, %s was provided" % (
Error in fail: Bazel requires Android build tools version 35.0.0 or newer, 30.0.3 was provided

Environment

• Machine: bk-macos-intel-qswt (macOS Intel)
• Platform: darwin-x86_64
• Bazel version: 9.0.0

[fweikert]

macos/mac-android.sh is a remnant of our old CI infrastructure and doesn't have any impact on our current MacOS CI -> #2467

Re buildtools: I published new Intel images with MacOS 15.7.3 and build tools 36.1.0 at the end of January, but unfortunately I had to roll the change back due to performance issues. Consequently, we're currently stuck with old Intel images :(

Debugging the issue is still on my todo list, but unfortunately I cannot promise a fix soon.

As a workaround, would it be possible to use MacOS ARM64 workers instead? They have build tools 36.1.0 installed.

[shs96c]

I'll happily move to macOS Apple silicon workers. I'd prefer it, even :)