aapt2 / ResourceProcessorBusyBox build errors

[jin]

Reported internally when using Bazel.

> ResourceProcessorBusyBox failed: error executing command
> bazel-out/host/bin/external/bazel_tools/src/tools/android/java/com/google/devtools/build/android/ResourceProcessorBusyBox
> --tool MERGE_COMPILED -- --classJarOutput ... (remaining 13 argument(s)
> skipped)
>
> Use --sandbox_debug to see verbose messages from the sandbox
> Oct 21, 2019 2:20:07 PM
> com.google.devtools.build.android.AndroidCompiledResourceMergingAction main
> SEVERE: Unexpected
> java.lang.IllegalArgumentException
> at
> com.google.common.base.Preconditions.checkArgument(Preconditions.java:127)
> at
> com.google.devtools.build.android.AndroidCompiledDataDeserializer.readResourceTable(AndroidCompiledDataDeserializer.java:251)
> at
> com.google.devtools.build.android.AndroidCompiledDataDeserializer.read(AndroidCompiledDataDeserializer.java:688)
> at
> com.google.devtools.build.android.SerializedAndroidData.deserialize(SerializedAndroidData.java:105)

and another while building an example app in TensorFlow:

SEVERE: Error during merging
Exception in thread "main" com.google.devtools.build.android.AndroidResourceMerger$MergingException: Merging Error:

Caused by: com.google.devtools.build.android.DeserializationException: aapt2 version mismatch.

These were fixed by updating the build tools version to 29.0.x.

[donaldchai]

Bazel assumes a build of aapt2 which includes:

aosp-mirror/platform_frameworks_base@0045116

[hevrard]

I had a similar issue, updating the Android SDK build-tools to a more recent version (I guess recent enough to get an aapt2 build which has the change pointed out by @donaldchai) fixed it. To install e.g. the recent 29.0.2 version of build-tools:

$ANDROID_SDK_HOME/tools/bin/sdkmanager install 'build-tools;29.0.2'

[jin]

Current status: waiting for new CI images to roll out 29.0.2 build tools bazelbuild/continuous-integration#856 so we can run global downstream tests to see an approximation of breakages.

[sgowroji]

Hi there! We're doing a clean up of old issues and will be closing this one. Please reopen if you’d like to discuss anything further. We’ll respond as soon as we have the bandwidth/resources to do so.