Search Issue Tracker
Won't Fix
Votes
1
Found in
2020.3.38f1
2021.3.8f1
2022.1.14f1
2022.2.0b6
2023.1.0a6
2023.2.0a1
Issue ID
UUM-13137
Regression
No
Gradle Build failure when building a new project
Reproduction steps:
# Create a new Unity project
# Switch the build platform to Android
# Build the project
Expected result: The build is successful and generates an APK with no errors
Actual result: The build fails and does not generate an APK
Reproducible with: 2020.3.38f1, 2021.3.8f1, 2022.1.14f1, 2022.2.0b6, 2023.1.0a6
Reproduced on: Windows 10 Pro
Notes:
# Reproduced on Windows 10.0.19044 Build 19044
# Reproduced on a clean Windows environment/install (cannot have installed any Java/Android dev tools, no Android Studio, no independent JDKs, etc)
# Reproduced on Unity versions installed using Unity Hub 3.2.0
# “Android Build Support” plugin must have “OpenJDK” and “Android SDK & NDK Tools”
The error from [GradleBuildFailure_Editor.log|https://editorbugs.unity3d.com/api/v1.0/attachments/0c3edc7b-4255-4669-a5bf-7c63259c1ad3/GradleBuildFailure_Editor.log] says:
{code:java}
* What went wrong:
Could not create service of type FileHasher using .createCachingFileHasher().
> Timeout waiting to lock file hash cache (C:\Users\aaron.zurawski\.gradle\caches\6.1.1\fileHashes). It is currently in use by another Gradle instance.
Owner PID: 16616
Our PID: 14116
Owner Operation:
Our operation:
Lock file: C:\Users\aaron.zurawski\.gradle\caches\6.1.1\fileHashes\fileHashes.lock* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.* Get more help at https://help.gradle.orgBUILD FAILED in 1m 3s
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
]
stdout[
Starting a Gradle Daemon, 1 incompatible Daemon could not be reused, use --status for details
] {code}
Might be related to the user name...
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [D3D12][XR] SRP Foveation foveated rendering on Windows platform not working when Graphics API is set to D3D12
- The Game view renders extremely saturated or almost black when FSR 1.0, HDR and DX12 are enabled
- Build error on Android when using Patch And Run paired with Play Asset Delivery
- "Browse" button for Xcode in the "Build Profiles" window is too big
- USS styles fail to inherit correctly when contentContainer is overridden in a custom control
Resolution Note:
Unable to reproduce on several machines and several versions of Unity