Scaleup Guide
Fix Android 'Execution failed for task :app:...' (Gradle Build Failed)
In this guide
A simple guide to this issue: Android 'Execution failed for task :app:...' (Gradle Build Failed). Learn why it happens, what to check first, and how to fix it.
Gradle errors are intimidating because the real cause is buried in a wall of stack traces. The fix is almost always one of four things: a JDK mismatch, an SDK version, a corrupt cache, or out-of-memory. Work the list.
The Error
Execution failed for task ':app:processDebugResources' (or :app:mergeDexDebug, :app:compileDebugJavaWithJavac ...)
Step 1: Read the Real Cause
cd android && ./gradlew assembleDebug --stacktraceThe --stacktrace output names the actual failing dependency or resource — start there, not at the generic top line.
Step 2: Clear the Caches
flutter clean # Flutter
cd android && ./gradlew clean && cd ..
# React Native
cd android && ./gradlew clean && cd ..
rm -rf ~/.gradle/caches/Step 3: Match the JDK
Modern Android Gradle Plugin needs JDK 17. A JDK 11 or 21 mismatch is a very common cause. Confirm with java -version and set org.gradle.java.home if needed.
Step 4: Give Gradle More Memory
# android/gradle.properties
org.gradle.jvmargs=-Xmx4096m -XX:MaxMetaspaceSize=1024mOrder of Operations
1) --stacktrace to find the cause. 2) clean caches. 3) check JDK. 4) bump memory. Most builds go green by step 2.