6

I'm running CI builds in a very resource-constrained Docker container.

AAPT2 doesn't seem to recognize that it's running in a container and spawns multiple daemon processes which then killed due to OOM and build fails:

AAPT2 aapt2-3.3.0-beta01-5013011-linux Daemon #0: Unexpectedly exit.
AAPT2 aapt2-3.3.0-beta01-5013011-linux Daemon #6: Unexpectedly exit.
AAPT2 aapt2-3.3.0-beta01-5013011-linux Daemon #3: Unexpectedly exit.
AAPT2 aapt2-3.3.0-beta01-5013011-linux Daemon #4: Unexpectedly exit.
AAPT2 aapt2-3.3.0-beta01-5013011-linux Daemon #2: Unexpectedly exit.
AAPT2 aapt2-3.3.0-beta01-5013011-linux Daemon #7: Unexpectedly exit.
AAPT2 aapt2-3.3.0-beta01-5013011-linux Daemon #1: Unexpectedly exit.
AAPT2 aapt2-3.3.0-beta01-5013011-linux Daemon #5: Unexpectedly exit.

Is there any way to disable AAPT2 daemon or at least limit the number of daemon processes? The Android Developer documentation doesn't seem to have any information about the AAPT2 daemon.

Sergey Ch.
  • 628
  • 1
  • 7
  • 17
  • Was Aapt2 deprecated in 2018? https://stackoverflow.com/questions/42082352/how-to-use-aapt2-where-is-the-documentation – MarkHu Feb 06 '19 at 21:07

2 Answers2

1

It's a known issue currently in the android plugin. Follow this issue on issue tracker to keep updated: https://issuetracker.google.com/117486770

Izabela Orlowska
  • 7,431
  • 2
  • 20
  • 33
0

You can temporarily add below line inside gradle.properties.

android.enableAapt2=false
shizhen
  • 12,251
  • 9
  • 52
  • 88