Android SDK full changelog

Windows ARM support
Improved publishing APIs
Better guidance for dependency verification failures

Windows ARM64 support
Improved publishing APIs
Better guidance for dependency verification failures

Configuration Cache is the recommended execution mode
Gradle requires JVM 17 or higher to run
Build scripts use Kotlin 2.2 and Groovy 4.0
Improved Kotlin DSL script compilation avoidance

Configuration Cache is the recommended execution mode
Gradle now requires JVM 17 or higher to run
Build scripts use Kotlin 2.1 and Groovy 4.0
Improved Kotlin DSL build script compilation avoidance

New features and usability improvements:
Support for Java 24:
With this release, Gradle supports Java 24. This means you can now use Java 24 for the daemon in addition to toolchains.
GraalVM Native Image selection for toolchains:
Gradle's toolchain support allows provisioning and selection of specific JDK versions for building projects—compiling code, running tests, and even running Gradle itself.
Skipped tests now report assumption violations:
When a test is skipped due to an assumption violation, Gradle now includes the reason in both the HTML and JUnit XML reports. This applies to JUnit 4, JUnit Platform, and TestNG.
Build authoring improvements:
Gradle provides rich APIs for plugin authors and build engineers to develop custom build logic.
Configuration cache improvements:
The configuration cache improves build time by caching the result of the configuration phase and reusing it for subsequent builds. This feature can significantly improve build performance.
Fixed issues:
update jacoco default to 0.8.13
Prevent Java 24 native access warnings in launcher
Java compilation errors and warnings have generic display names in Problems summary html
Missing locations for some issues in problems report
Fix doc example for problems api
Update configuration cache report for new tabs
Problems API additional data needs more documentation
`MapProperty.keySet()` provider should track tasks dependencies
Remove obsolete usages of ProblemsProgressEventEmitterHolder
Remove unused InternalProblemSpec.additionalDataInteral() API
Fix project dependencies created by `snapshot-worker` project
Daemon JVM provisioning fails on existing JDK archive with same name
distZip top level directory has wrong name when version has substring ".zip"
Extract packaging related projects from subprojects
Jvm Toolchain: Add support for requesting native-image feature
CompilerOptions.getAllCompilerArgs may return unexpected types
Issue upgrading to Gradle 8.12: Problems API > “NullPointerE

It fixes the following issues:
#31245 FileLockCommunicator is not compatible with macOS 15.1 firewall and Crowdstrike/SentinelOne
#31942 Default working directory for ExecSpec changed between 8.11 and 8.12
#31946 Build failed on Linux after upgrading 8.11.1 -> 8.12
#32016 Incorrect output format for Java compiler problems

New features and usability improvements:
Error and warning reporting improvement:
Gradle provides a rich set of error and warning messages to help you understand and resolve problems in your build.
Summarization in the HTML report for problems:
The Problems API provides structured feedback on build issues, helping developers and tools like IDEs identify and resolve warnings, errors, or deprecations during configuration or runtime.
This release introduces a new problem summarization mechanism that reduces redundancy in the generated HTML Problems Report.
The feature limits the number of identical problems reported and provides a summarized count of additional occurrences in the summary report.
Ambiguous Artifact Transformation chains are detected and reported:
Previously, when two or more equal-length chains of artifact transforms produced compatible variants to satisfy a resolution request, Gradle would arbitrarily and silently select one. Gradle now emits a warning for this case.
This deprecation warning is the same failure message that now appears when multiple equal-length chains are available, producing incompatible variants that could each satisfy a resolution request. In this case, resolution fails with an ambiguity failure, and Gradle emits a message.
The formatting of this message has been improved to comprehensively display information about each complete chain of transformations that produces the candidates that would satisfy the request. This allows authors to better analyze and understand their builds, allowing them to remove ambiguity.
Platform enhancements:
Gradle provides many features for specific platforms and languages.
File-system watching and continuous mode support on Alpine Linux
File-system watching is now supported on Alpine Linux, a popular choice for container-based images and the default distribution for Docker.
The feature is enabled by default, as is the case with all other supported platforms.
Additionally, it is now possible to run bui

New features and usability improvements:
Error and warning reporting improvement:
Gradle provides a rich set of error and warning messages to help you understand and resolve problems in your build.
Summarization in the HTML report for problems:
The Problems API provides structured feedback on build issues, helping developers and tools like IDEs identify and resolve warnings, errors, or deprecations during configuration or runtime.
This release introduces a new problem summarization mechanism that reduces redundancy in the generated HTML Problems Report.
The feature limits the number of identical problems reported and provides a summarized count of additional occurrences in the summary report.
Ambiguous Artifact Transformation chains are detected and reported:
Previously, when two or more equal-length chains of artifact transforms produced compatible variants to satisfy a resolution request, Gradle would arbitrarily and silently select one. Gradle now emits a warning for this case.
This deprecation warning is the same failure message that now appears when multiple equal-length chains are available, producing incompatible variants that could each satisfy a resolution request. In this case, resolution fails with an ambiguity failure, and Gradle emits a message.
The formatting of this message has been improved to comprehensively display information about each complete chain of transformations that produces the candidates that would satisfy the request. This allows authors to better analyze and understand their builds, allowing them to remove ambiguity.
Platform enhancements:
Gradle provides many features for specific platforms and languages.
File-system watching and continuous mode support on Alpine Linux
File-system watching is now supported on Alpine Linux, a popular choice for container-based images and the default distribution for Docker.
The feature is enabled by default, as is the case with all other supported platforms.
Additionally, it is now possible to run bui

New features and usability improvements:
Configuration Cache improvements:
Gradle's Configuration Cache improves build performance by caching the result of the configuration phase. Gradle uses the Configuration Cache to skip the configuration phase entirely when nothing that affects the build configuration has changed.
Faster Configuration Cache with parallel load and store:
When enabled, the Configuration Cache can greatly increase build performance. However, for large and complex builds, storing and loading cache entries can still incur a noticeable overhead.
To address this, storing and loading of the Configuration Cache can now be performed in parallel, resulting in better performance in case of both cache misses and hits.
To enable the feature, add the following flag in gradle.properties:
org.gradle.configuration-cache.parallel=true
This is an incubating feature and may expose concurrency issues in some builds.
For more details on configuring parallel caching, see Configuration Cache.
Configuration Cache enabled by default when using the Build Init plugin:
The Configuration Cache has been stable since Gradle 8.1 and is already widely used. As we work towards making it the preferred mode of execution, we continue to encourage further adoption.
Starting with this release, projects generated by the Build Init plugin enable the Configuration Cache via the root gradle.properties file. This also includes projects converted from Maven.
Configuration Cache compatibility for C++ and Swift plugins:
Most core plugins and Gradle features are already compatible with Configuration Cache. This release also addresses the compatibility of native plugins.
The following C++ and Swift plugins are now Configuration Cache compatible:
Swift application
Swift library
XCTest
C++ application
C++ library
CppUnit
GoogleTest
Visual Studio
XCode
Error and warning reporting improvements:
Gradle provides a rich set of error and warning messages to help you understand and resolve problems in y

It fixes the following issues:
#30472 Investigate possibly broken 8.10.1
#30477 Kotlin Mutliplatform build with reused daemon fails with "Cannot query the value of task ':compileKotlinWindows' property 'kotlinNativeBundleBuildService' because it has no value available."
#30497 DefaultTaskCollection#configureEach(Action) on task set cannot be executed in the current context