Published November 22, 2026
Android Studio Rabbit 2 Patch 2 Pushes AGP 9.5.2 to Stable with Two Build Fixes
Android Studio Rabbit 2 Patch 2 reached the stable channel on Friday, November 20, 2026, carrying Android Gradle Plugin 9.5.2. The release notes list exactly two fixed issues. Two is a small number for a patch that moves a Gradle plugin version, and that is the point: both entries describe builds that fail outright rather than degrade, and one of them is a warning about a future failure that has now been answered.
This is the third stable drop on the Rabbit 2 line in under three weeks. Rabbit 2 shipped on November 2, Patch 1 followed on November 5, and Patch 2 arrived on November 20. The cadence says as much about the AGP 9.5 series as the changelog does.
What actually changed
The first fix, issue 581925548, covers fat AARs that contain multiple nested jars. Starting with AGP 9.5, merging Java resources across those nested archives failed, so a library that packages dependencies inside itself could not be assembled. Fat AARs are not common in pure Flutter projects, but they are common in the Android libraries that Flutter plugins wrap, particularly anything distributed as a closed prebuilt binary.
The second fix, issue 582417470, is the more interesting one. The original bug title read that an Android app will soon fail under Isolated Projects when it uses implementation(project(...)). That phrasing matters. Gradle Isolated Projects is the configuration model AGP has been migrating toward for several release cycles, and it removes the ability for one project to reach into another project's build state during configuration.
Project dependencies declared with implementation(project(...)) are the most ordinary thing in a multi-module Android build. Every Flutter app that adds a local module, a shared UI package, or a plugin built from source has at least one. If that construct stopped resolving under Isolated Projects, the migration would have stalled on contact with real codebases.
The fix in AGP 9.5.2 means the migration continues. It does not mean the migration is finished, and it does not mean an app currently building with Isolated Projects disabled is safe from the next change in this area.
Where Flutter teams meet this
Flutter apps do not usually edit Gradle scripts by hand, but they inherit AGP through the Flutter Gradle plugin, and every plugin dependency compiles as its own Android subproject. Three places are worth checking after the upgrade:
- Local modules added through include in settings.gradle, which are the most likely source of implementation(project(...)) in a Flutter build.
- Plugin authors who ship prebuilt AARs with bundled dependencies, where the nested jar merge failure would surface.
- CI images pinned to an older AGP, which will now disagree with a local build that updated Android Studio.
The third item is the one that wastes a day. Android Studio updates AGP through its own version catalog defaults in some project templates, while a CI pipeline installs a Gradle distribution and resolves the plugin from a pinned version. A patch release that looks cosmetic locally can produce a build that passes on a laptop and fails on the runner, or the reverse.
The canary line kept moving too
Android Studio Stingray 1 Canary 2 landed the same day, bundling AGP 9.6.0-alpha05. Its fix list is longer and broader: recomposition tracing added to the Android CLI profiler system trace command, a Database Inspector corruption bug with Room and the bundled SQLite driver, a Gradle integration issue where managed-device instrumented tests ignored ANDROID_ADB_SERVER_PORT on Windows and reported a pass with zero tests, and a request to convert SVG text to vectors in the resource tools.
So the stable and canary channels are now two minor AGP versions apart, 9.5.2 against 9.6.0-alpha05. That gap is normal, and it is also the reason a Flutter project should pin its AGP version in the version catalog rather than accept whatever the IDE suggests after an update.
Since Flutter 3.50 and the 3.51 beta both build through the same Gradle plugin, nothing in the framework requires this patch. Take it if you hit either of the two issues, or if you are deliberately tracking the AGP 9.5 line. Otherwise the safer move for a team mid-release is to pin 9.5.1, finish the release, and update in the next window with a clean CI run behind it.