Closed sgowroji closed 5 months ago
Looks like the failure is related to the changes in https://github.com/bazelbuild/examples/commit/5e37d3c0041dc8e4750f6dfbd7508782cdc3c610
/cc @katre Can you please take a look?
As indicated in android.yml
, the problem is that this example does not use the new Android platforms flags, it's using the legacy flags, which aren't supported in Bazel at HEAD.
Using Bazel 6.4.0, the build works:
$ USE_BAZEL_VERSION=6.4.0 bazel build --noincompatible_enable_android_toolchain_resolution --fat_apk_cpu=arm64-v8a,x86 --android_crosstool_top=@androidndk//:toolchain --enable_bzlmod //app/src/main:app
INFO: Analyzed target //app/src/main:app (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
Target //app/src/main:app up-to-date:
bazel-bin/app/src/main/app_deploy.jar
bazel-bin/app/src/main/app_unsigned.apk
bazel-bin/app/src/main/app.apk
INFO: Elapsed time: 0.350s, Critical Path: 0.01s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
I'll try updating the flags and see if that works, but last time I tried I ran into https://github.com/bazelbuild/rules_android/issues/77.
https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/3519#018c569e-3795-4226-ab3e-197736d4484f
Platform : Windows, Ubuntu, MacOS
Logs:
Steps:
CC Greenteam @comius