Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Building using local android_tools causes a DexMapper error #11810

Closed
nkoroste opened this issue Jul 20, 2020 · 4 comments
Closed

Building using local android_tools causes a DexMapper error #11810

nkoroste opened this issue Jul 20, 2020 · 4 comments
Labels
P2 We'll consider working on this in future. (Assignee optional) stale Issues or PRs that are stale (no activity for 30 days) team-Android Issues for Android team type: bug

Comments

@nkoroste
Copy link
Contributor

Description of the problem / feature request:

When attempting to build and android app using a locally build version of android_tools it causes the following error:

Error: Could not find or load main class com.google.devtools.build.android.ziputils.DexMapper

I'm pretty sure it's related to sandboxing and the --override_repository=android_tools= flag. I was following your instructions from a different PR on how to build using locally built tool.

When I manually ran the dexmapper subcommand it passed just fine

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

bazel build //src:bazel-dev //tools/android/runtime_deps:android_tools
mkdir -p /tmp/bazel_android_tools
tar -xzvf bazel-bin/tools/android/runtime_deps/android_tools.tar.gz -C /tmp/bazel_android_tools
./bazelw build --override_repository=android_tools=/tmp/bazel_android_tools //app

What operating system are you running Bazel on?

Replace this line with your answer.

What's the output of bazel info release?

3.4.1

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

More context in #11618

@ahumesky ahumesky added P2 We'll consider working on this in future. (Assignee optional) and removed untriaged labels Dec 3, 2020
@nkoroste
Copy link
Contributor Author

Still hitting this issue with v4.1.0 by the way

@nkoroste
Copy link
Contributor Author

Oh I think I figured it out. I can't use /tmp because of:

build:linux --sandbox_tmpfs_path=/tmp 

Needed due to #3236

@github-actions
Copy link

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

@github-actions github-actions bot added the stale Issues or PRs that are stale (no activity for 30 days) label May 24, 2023
@github-actions
Copy link

github-actions bot commented Jun 7, 2023

This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team (@bazelbuild/triage). Thanks!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 We'll consider working on this in future. (Assignee optional) stale Issues or PRs that are stale (no activity for 30 days) team-Android Issues for Android team type: bug
Projects
None yet
Development

No branches or pull requests

3 participants