Documentation

​
​

Development

User Acquisition

Monetization

Industry

Build Automation

DevOps

Build Automation REST API

Build Automation Editor Package

Open Unity Dashboard

Build Automation

​
​
Build Automation
  • Overview
  • Get started with Build Automation
  • Build Automation Glossary
  • Build configuration
  • Advanced build configuration
  • Run builds
  • Build results
    • Check build results
    • Troubleshooting Build Automation failures
      • Troubleshoot common issues
      • Builds fail immediately
      • Unrecognized project error
      • Clone hangs when you use Git submodules
      • Lightmap baking
      • Android build failures
      • Errors after migration to a new Xcode version
      • macOS notarization failure
      • Problems with iOS Build Automation during XCode export
      • iOS build can't download or install from Unity Build Automation
  • Optimize build speed
  • Manage artifact retention rules
  • Manage concurrent builds
  • Sign build artifacts
  • Build Automation integrations
  • Build Automation API
  • Build Automation Editor Package
  • Reference
  1. Unity Build Automation
  3. Build results
  5. Troubleshoot Build Automation failures

Android build fails in Unity Build Automation

Resolve Android build failures in Unity Build Automation and identify common causes.
Read time 2 minutes
Last updated 10 months ago

Symptoms

  • Android builds fail for an unclear reason.
  • Android builds fail and other targets build correctly.
  • Android builds fail in UBA but work locally.

Cause

Unity Build Automation runs the Unity Editor in 
batchmode
 to execute your builds, and uses the default Android tools (JDK/SDK) to complete them. When your Android build fails in the service but works locally or other targets seem to work correctly, the root cause is often incompatible Android tools.
Failures due to Android tool often have the message 
Gradle Build failed
in the logs. Gradle is the build system that Unity uses for Android builds.

Resolution

The first step to resolve this issue is to ensure you can build your project locally in batch mode with the following tool versions:
  • The Unity Editor.
  • The JDK (the default version that ships with the chosen version of the Editor).
  • The Android SDK (either the default version or as specified in your advanced target configuration).
You also need to validate the version of Gradle that you use.
Note
Check the versions of any project dependencies and ensure that they're pinned. Often builds begin to fail when dependency versions upgrade and require a newer Unity version or SDK version than you use for the build.
If your project does build locally, take note of the versions of the tools you used and ensure they match with the versions you use in the Unity Build Automation service. To check your local version of Gradle you can use the command 
gradle --version
in the terminal.
If your build works locally in 
batchmode
 but fails in the Unity Build Automation service with the same tools and versions, please open a support ticket so the support team can investigate further. To submit a ticket from the Unity Dashboard, open DevOps and select Help & Support > Ticket > File a ticket.

Additional resource

  • Default Android tools by Editor version
Copyright © 2026 Unity Technologies
LegalPrivacy PolicyCookiesDocumentation Terms of UseDo Not Sell or Share My Personal InformationYour Privacy Choices (Cookie Settings)

"Unity", Unity logos, and other Unity trademarks are trademarks or registered trademarks of Unity Technologies or its affiliates in the U.S and elsewhere (more info here). Other names or brands are trademarks of their respective owners.

Some pages are machine-translated for convenience, and may contain inaccuracies. In the event of conflicting information, the English version is authoritative.

  • On this page

    • Symptoms

    • Cause

    • Resolution

    • Additional resource

Report a problem with this page