Disable duplicate asset checks for Robolectric tests

Since Robolectric tests only implement a small portion of an application which often includes test overrides, there is little need for costly duplicate asset detection within these tests, especially given the performance ramifications.

Additionally, AAPT2 already can perform its own duplicate resource validation during compilation and linking, so these additional checks are redundant for Robolectric tests where symbolsOut is not needed. If needed, these kinds of verifications would be more efficiently implemented within AAPT2 itself.

A new argument generate_out_symbols skips the costly process of checking for merge conflicts within Aapt2ResourcePackagingAction.java for Robolectric tests while preserving this functionality otherwise.

PiperOrigin-RevId: 924841916
Change-Id: Ib125fbe6e5803f6ea38649738cb040de07b0e9c6
3 files changed
tree: 5dd2a210817fd5e59946213bbf06ea33c00b1bc9
  1. .bazelci/
  2. .bcr/
  3. .github/
  4. android/
  5. bzlmod_extensions/
  6. contrib/
  7. examples/
  8. kokoro/
  9. mobile_install/
  10. providers/
  11. py_support/
  12. rules/
  13. src/
  14. stardoc/
  15. test/
  16. third_party/
  17. toolchains/
  18. tools/
  19. .bazelignore
  20. .bazelrc
  21. .bazelversion
  22. .gitignore
  23. android_sdk_supplemental_repository.bzl
  24. AUTHORS
  25. BUILD
  26. CONTRIBUTING.md
  27. CONTRIBUTORS
  28. defs.bzl
  29. defs_dev.bzl
  30. go.mod
  31. go.sum
  32. groups
  33. LICENSE
  34. MODULE.bazel
  35. prereqs.bzl
  36. project.config
  37. README.md
  38. ROADMAP.md
  39. robolectric-bazel.patch
  40. rules_android_maven_install.json
  41. WORKSPACE
  42. WORKSPACE.bzlmod
README.md

Android support in Bazel

Disclaimer

NOTE: This branch is a development preview of the Starlark implementation of Android rules for Bazel. This code is incomplete and may not function as-is.

A recent version of Bazel (7.4+, 8.0+, HEAD, Bazel 9 pre-release) is required.

This ruleset depends on Protobuf, which has a minimum C++ language level of 17 (as of Protobuf v30, ~2025 Q3). Depending on your system‘s compiler version, you may have to set -std=c++17 in your C++ toolchain arguments. This repository’s .bazelrc file provides a minimal set of Bazel configuration flags to build an Android app.

Overview

This repository contains the Starlark implementation of Android rules in Bazel.

The rules are being incrementally converted from their native implementations in the Bazel source tree.

Stardoc for the Android rules can be found at https://bazelbuild.github.io/rules_android.

Getting Started

To use the Starlark Bazel Android rules, add the following to your WORKSPACE file:

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
    name = "rules_android",
    sha256 = "fe3d8c4955857b44019d83d05a0b15c2a0330a6a0aab990575bb397e9570ff1b",
    strip_prefix = "rules_android-0.6.0-alpha1",
    url = "https://github.com/bazelbuild/rules_android/releases/download/v0.6.0-alpha1/rules_android-v0.6.0-alpha1.tar.gz",
)

# Android rules dependencies
load("@rules_android//:prereqs.bzl", "rules_android_prereqs")
rules_android_prereqs()

##### rules_java setup for rules_android #####
load("@rules_java//java:rules_java_deps.bzl", "rules_java_dependencies")
rules_java_dependencies()
# note that the following line is what is minimally required from protobuf for the java rules
# consider using the protobuf_deps() public API from @com_google_protobuf//:protobuf_deps.bzl
load("@com_google_protobuf//bazel/private:proto_bazel_features.bzl", "proto_bazel_features")  # buildifier: disable=bzl-visibility
proto_bazel_features(name = "proto_bazel_features")
# register toolchains
load("@rules_java//java:repositories.bzl", "rules_java_toolchains")
rules_java_toolchains()

##### rules_jvm_external setup for rules_android #####
load("@rules_jvm_external//:repositories.bzl", "rules_jvm_external_deps")
rules_jvm_external_deps()
load("@rules_jvm_external//:setup.bzl", "rules_jvm_external_setup")
rules_jvm_external_setup()

##### rules_android setup #####
load("@rules_android//:defs.bzl", "rules_android_workspace")
rules_android_workspace()

# Android SDK setup
load("@rules_android//rules:rules.bzl", "android_sdk_repository")
android_sdk_repository(
    name = "androidsdk",
)

register_toolchains(
    "@rules_android//toolchains/android:android_default_toolchain",
    "@rules_android//toolchains/android_sdk:android_sdk_tools",
)

Or, if you want to use bzlmod, add the following to your MODULE.bazel file:

MODULE.bazel:

bazel_dep(name = "rules_java", version = "7.11.1")
bazel_dep(name = "bazel_skylib", version = "1.3.0")

bazel_dep(name = "rules_android", version = "0.6.5")

remote_android_extensions = use_extension(
    "@rules_android//bzlmod_extensions:android_extensions.bzl",
    "remote_android_tools_extensions")
use_repo(remote_android_extensions, "android_tools")

android_sdk_repository_extension = use_extension("@rules_android//rules/android_sdk_repository:rule.bzl", "android_sdk_repository_extension")
use_repo(android_sdk_repository_extension, "androidsdk")

register_toolchains("@androidsdk//:sdk-toolchain", "@androidsdk//:all")

Then, in your BUILD files, import and use the rules:

load("@rules_android//rules:rules.bzl", "android_binary", "android_library")
android_binary(
    ...
)

android_library(
   ...
)