Android SDK full changelog

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

Fixed issues:
[8.8] new Daemon JVM feature incompatible with android; needs additional criteria
Revert some of the build scope listener deprecations recently introduced
Project dependencies can be observed outside of Configuration Cache fingerprinting
Configuration Cache fails to restore `Proxy` created in Gradle-specific classloader
Gradle doesn't recognise inherited OpenTest4J FileInfo in test assertion exception
The example of creating a Script plugin in the documentation does not work
Wrong JDK version in error message suggestion correction steps
De-incubate `website` and `vcsUrl` properties of `GradlePluginDevelopmentExtension`
Improving the design of buttons
Update DomainObjectContext to expose a getProjectIdentityPath() method
Sample for Problems API does not work
Strongly-typed custom dependency schema should have their types preserved when being consumed from another repo
"Understanding tasks" docs page problems
A build scan cannot be produced due to "Dangling build operations detected".
When wrapper fails checksum validation, don't show the actual checksum, instead redirect users to a more reliable source
Update Working with Dependencies -> Learning the Basics section of User Manual
Gradle build fails with an error on sync with Configuration Cache
Simple custom interceptors for bytecode upgrade don't allow to upgrade any type
Problem description copied from the CC report is noisy and ill-formatted
`unreportedProblemInCurrentCall` error when using configure action
Deprecate running Gradle on JVM versions < 17
Wrong information about removing unintentional subprojects
Isolated Project violations should include a location
Simplify writing custom interceptors for upgraded properties
Working with Files - CopySpec - should be linked to on the Distribution Plugin doc page
Annotate all properties that should be migrated with `@ToBeReplacedByLazyProperty`
Report user-friendly errors when the DCL schema builder encounters collections (or ot

Fixed issues:
[8.8] new Daemon JVM feature incompatible with android; needs additional criteria
Revert some of the build scope listener deprecations recently introduced
Project dependencies can be observed outside of Configuration Cache fingerprinting
Configuration Cache fails to restore `Proxy` created in Gradle-specific classloader
Gradle doesn't recognise inherited OpenTest4J FileInfo in test assertion exception
The example of creating a Script plugin in the documentation does not work
Wrong JDK version in error message suggestion correction steps
De-incubate `website` and `vcsUrl` properties of `GradlePluginDevelopmentExtension`
Improving the design of buttons
Update DomainObjectContext to expose a getProjectIdentityPath() method
Sample for Problems API does not work
Strongly-typed custom dependency schema should have their types preserved when being consumed from another repo
"Understanding tasks" docs page problems
A build scan cannot be produced due to "Dangling build operations detected".
When wrapper fails checksum validation, don't show the actual checksum, instead redirect users to a more reliable source
Update Working with Dependencies -> Learning the Basics section of User Manual
Gradle build fails with an error on sync with Configuration Cache
Simple custom interceptors for bytecode upgrade don't allow to upgrade any type
Problem description copied from the CC report is noisy and ill-formatted
`unreportedProblemInCurrentCall` error when using configure action
Deprecate running Gradle on JVM versions < 17
Wrong information about removing unintentional subprojects
Isolated Project violations should include a location
Simplify writing custom interceptors for upgraded properties
Working with Files - CopySpec - should be linked to on the Distribution Plugin doc page
Annotate all properties that should be migrated with `@ToBeReplacedByLazyProperty`
Report user-friendly errors when the DCL schema builder encounters collections (or ot

adb:
Fix openscreen mDNS backend bug bringing down server on truncated query issue #294120933.
Make openscreen mDNS backend work on macOS.
Make openscreen mDNS backend default on all platforms.
Support to detect USB SuperSpeed+ (current and negotiated speeds) for diagnostic purposes.
Graceful shutdown: Release all USB interfaces on shutdown (all OSes).

adb
adb now defaults to libusb on macOS to address issue #270205252.
Previously, adb responded with a successful code when wireless pairing fails. Resolved this by returning a failure code (1) and user-facing error (error: protocol fault (couldn't read status message...)). echo $? now reports 1.
adb wait-for-disconnect is now operational for non-USB (wireless debugging).
Added new DbC interface for future support of ChromeOS over adb.
fastboot
Fixed flashall on Pixel 3 devices.