CODEWITHSUNDEEP
androidubuntugradleaapt
user2061057
user2061057

Reputation: 1022

How to debug a failing Android Gradle build?

My build fails like this (I haven't written this piece of software) on Ubuntu 16.04:

FAILURE: Build failed with an exception.
11:00:04.533 [ERROR] [org.gradle.BuildExceptionReporter] 
11:00:04.533 [ERROR] [org.gradle.BuildExceptionReporter] * What went wrong:
11:00:04.533 [ERROR] [org.gradle.BuildExceptionReporter] Execution failed for task ':app:processArmv7DebugResources'.
11:00:04.534 [ERROR] [org.gradle.BuildExceptionReporter] > com.android.ide.common.process.ProcessException:     org.gradle.process.internal.ExecException: Process 'command '/home/xxx/Android/Sdk/build-tools/23.0.2/aapt'' finished with non-zero exit value 1
11:00:04.534 [ERROR] [org.gradle.BuildExceptionReporter]

So apparently running aapt fails. The problem is that this error obviously doesn't tell me anything. How can I find out what actually happened? I tried to run gradlew with --debug and --stacktrace with no luck.

Where is this task processArmv7DebugResources defined?

Upvotes: 0

Views: 196

Answers (1)

user2061057
user2061057

Reputation: 1022

I ended up creating a wrapper script called aapt that logs its arguments to a file and then calls the real aapt. This way I found out the actual command that caused the problem. It was something related to case sensitivity in asset file names that obviously had worked on Windows.

This was actually also printed by Gradle when called with --debug, but it was logged after the aapt crash and with Info tag so I wasn't sure if that's the root cause.

Upvotes: 1

Related Questions