Published November 21, 2026

Stingray 1 Canary 2 Lands: How Fast Android Studio's Canary Channel Now Moves

Android Studio Stingray 1 Canary 2 reached the Canary channel on November 20, 2026. Canary 1 went out on November 16. Four days between canary drops is a compressed rhythm for an IDE that used to spend weeks between preview builds, and it says something about how the Android tools team is now shipping: small, frequent increments on a preview line that most working developers never install.

The build is labelled Stingray 1, version 2026.3.1, which places it in the 2026.3 release train. It sits in the Canary channel, one step ahead of Beta and two steps ahead of the stable line that most Flutter and Android teams run. The Stingray line opened alongside Android Gradle Plugin 9.6.0-alpha04, so the second canary is still moving on the same alpha AGP stream rather than introducing a new one.

Three release lines in flight at once

The confusing part of the current Android Studio schedule is that three lines are active simultaneously. Rabbit 3 is sitting in Release Candidate 1, which means the next stable is close. Quail 4 has been stable since the start of September and has already taken a patch. Stingray 1 is the fresh canary, three months of work away from being something a team should depend on.

That overlap is normal for JetBrains-based IDEs, and it is deliberately visible. Canary builds are where the tools team tests new Gradle integrations, new agent workflows, and new Compose tooling before those changes reach a release candidate. A canary that ships four days after its predecessor is usually a bug-fix or stabilisation drop rather than a feature drop, and the release notes for Canary 2 are short for exactly that reason.

Why a canary still matters to a Flutter project

A Flutter developer does not consume Android Studio the way an Android developer does. Flutter drives the build through Gradle and the Flutter Gradle plugin, and the IDE is mostly a host for the Dart plugin, the emulator, and the layout inspector. That insulation is real, but it is not total. Two things leak through.

The first is the Android Gradle Plugin version that a new Flutter project template pins, and the AGP version that a canary is tested against. The second is the JDK bundled with the IDE, since Gradle daemons started from the IDE inherit it. When a canary bumps either one, plugin projects with custom build types or older Gradle wrappers are the first to fail, and the failure usually appears as a configuration error rather than a compile error.

What changes first when a canary lands:

  • The AGP version the IDE is validated against, currently the 9.6 alpha line.
  • The bundled JDK, which Gradle daemons started from the IDE inherit.
  • The Gradle version used by the embedded build tooling, not by your wrapper.
  • The Compose and layout inspector tooling, which Flutter projects only touch indirectly.

None of those are reasons to install a canary on a machine that ships release builds. They are reasons to know what a canary changed when a teammate reports that their build behaves differently after an IDE update.

The practical rule for this week

Keep the stable channel for daily work. Android Studio supports side-by-side installs, so a canary can live next to a stable build for a specific experiment: checking whether a Gradle sync problem is your project or your IDE, or testing a preview feature before a migration. Installing a canary over a stable build is the mistake that costs an afternoon.

For the Android side of a Flutter app, pin the AGP version in android/settings.gradle.kts rather than accepting the template default, and pin the Gradle wrapper. Flutter's Android dependency matrix documents which AGP and Gradle combinations each Flutter release supports, and Canary 2 does not change that matrix. A canary is validated against versions that Flutter has not blessed yet, which is why a canary can build a project that stable Flutter later rejects.

The broader signal is worth noting. Android tooling is now shipping on a weekly-ish canary clock while Flutter ships four stables a year. The mismatch is fine as long as teams treat the IDE as infrastructure to be pinned, not as software to be updated the moment a notification appears. Canary 2 is four days of work on a line that will not be stable until next year, and the correct response for almost every Flutter team is to read the note, check the AGP version, and close the tab.