New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing cache.properties
file causes Gradle to fail to start
#3176
Comments
The failure occurs here, where Gradle tries to load |
This is an attempt to fix #3176 . When .gradle/buildOutputCleanup/cache.properties is removed unexpectedly, Gradle will fail to start. This PR adds a safe-check before accessing the file.
This is an attempt to fix #3176 . When .gradle/buildOutputCleanup/cache.properties is removed unexpectedly, Gradle will fail to start. This PR adds a safe-check before accessing the file.
Removing the cache.properties.lock file did the trick for me |
Or removing buildOutputCleanup.lock |
las rutas?? |
With ubuntu I start react-native run-android with sudo. So its gets permissions to download .gradle. Maybe its works when chmod .gradle folder. |
or by removing the |
Sporadically, starting with Gradle 4.2, the file
.gradle/buildOutputCleanup/cache.properties
is removed or fails to be created when starting the Gradle daemon. This causes the build to fail very early (while creatingTaskExecutionServices
) and is unrecoverable without deleting the.gradle
directory or creating the missing file by hand. Stopping and restarting the daemon doesn't recreate the file.This doesn't appear to happen on every build and I believe the build sometimes works and then fails later (with another new daemon).
Expected Behavior
Gradle would not fail to start.
Current Behavior
Gradle fails with a cryptic message:
Context
I can provide more context privately.
Steps to Reproduce (for bugs)
This happens sporadically.
Your Environment
The build is running inside a Linux Docker container.
This occurs on Gradle 4.2. Previously, the project was using 4.0.2 and didn't see this problem.
The text was updated successfully, but these errors were encountered: