Friday, November 21, 2025

Android Studio Otter 3 Feature Drop | 2025.2.3 Canary 2 now available

Android Studio Otter 3 Feature Drop | 2025.2.3 Canary 2 is now available in the Canary channel.

If you already have an Android Studio build on the Canary channel, you can get the update by clicking Help > Check for Updates (or Android Studio > Check for Updates on macOS). Otherwise, you can download it here.

For information on new features and changes in Android Studio Otter 3 Feature Drop, see the Android Studio Preview release notes. For details of bugs fixed in each previous release of Android Studio Otter 3 Feature Drop, see closed issues.

General fixes and features

Below is a list of general fixes in Android Studio Otter 3 Feature Drop | 2025.2.3 Canary 2 and Android Gradle Plugin 9.0.0-beta02. These are a result of your bug reports, which help us to make Android Studio better. If you encounter a problem, let us know by reporting a bug. You can also vote for an existing issue to indicate that it also affects you.

Fixed Issues
Android Gradle Plugin
Feature Request: Inject ideal AGP version as a property
Stabilize SingleArtifact.VERSION_CONTROL_INFO_FILE
androidTest connectedCheck logcat output is broken
Database Inspector
App Inspector - Database Inspector - Support 3rd Party Drivers
Debugger
Stackoverflow when debugging in AS Otter Canary5
Gemini
AS AI Remote - Remote Models - support for Github Copilot
Gradle
Mark SingleArtifact.MERGED_NATIVE_LIBS stable
Import/Sync
Please inject intellij platform version into gradle
In a composite-build project, "Clean Project" action in Android Studio launches multiple Gradle daemons
Android Studio does not provide a way to accurately detect AGP/IDE version during Gradle sync
Lint
AGP 8.11.0: lintAnalyzeRelease task crashes when applying .gradle.kts files with apply(from = "...")
Lint Integration
AndroidLintAnalysisTask cache misses across different JDK vendors or minor versions due to systemPropertyInputs.javaVersion differences
Manifests
[Otter 2 Feature Drop 2025.2.2 Canary 1] Thread occasionnally takes 100% CPU usage