bazelbuild / bazelbuild/bazel

android_library aapt invocation doesn't handle public.xml or public_*.xml

Open
#28,476 0 comments 0 reactions 0 assignees View on GitHub
team-Android type: bug untriaged
Dominant language
Java
Stars
25.8k
Forks
4.6k
Avg merge
2d 20h
Merged PRs (30d)
72

Description

### Description of the bug:

Hi team, I wanna reopen https://github.com/bazelbuild/bazel/issues/2124

### Which category does this issue belong to?

_No response_

### What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

_No response_

### Which operating system are you running Bazel on?

_No response_

### What is the output of `bazel info release`?

_No response_

### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.

_No response_

### What's the output of `git remote get-url origin; git rev-parse HEAD` ?

```text

```

### If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.

_No response_

### Have you found anything relevant by searching the web?

_No response_

### Any other information, logs, or outputs that you want to share?

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the referenced issue #2124 and the android_library aapt invocation, focusing on how public.xml and public_*.xml are handled. Reproduce the reported behavior with a minimal Android library if possible, then verify that both resource filename patterns are processed correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.