Published November 18, 2026

Android Studio Stingray 1 Canary 1 Opens a New Line with AGP 9.6.0-alpha04

Android Studio's Canary channel changed animals on November 16. Stingray 1 Canary 1 is now available and ships with Android Gradle Plugin 9.6.0-alpha04, which makes it the first build on a line that runs past the Rabbit 3 beta. For Flutter developers the interesting content is not the new name but the bug list, because several of those fixes sit directly on the path between a Flutter project and an Android artifact.

The release notes list thirteen issues across adb, the Android Gradle Plugin, Database Inspector, the emulator, Gradle sync, layout editing, lint, project structure, run configurations, running devices, and the SDK Manager. That spread is normal for the first canary of a cycle, since the initial drop tends to clear a backlog of reports that accumulated while the previous line was stabilizing.

The Fixes That Reach Flutter Builds

Two of the plugin fixes are worth reading twice. Generated BuildConfig.java files were emitting a dangling header comment that broke builds running with -Xlint:all -Werror on JDK 23 and newer, which is exactly the combination a growing number of teams adopt for strictness. Separately, the order of shrinker rule files pulled from a single dependency depended on the filesystem, which made R8's configuration.txt output nondeterministic. Determinism matters here because it is a prerequisite for reproducible builds and for caching that survives a machine change.

Three more plugin items land close to dependency handling. Fat AARs with multiple nested jars failed to merge Java resources starting in 9.5, apps will soon fail under Isolated Projects when they use implementation(project(...)) dependencies, and that second one is a warning about the direction of travel rather than a bug. Isolated Projects has been tightening for several releases, and Flutter plugin modules that reference sibling modules inside an Android build are the likely place to feel it.

On the tooling side, adb pair for wireless debugging no longer fails when the device is attached to an MLO Wi-Fi 7 network. Wireless debugging has become the default way many developers deploy to physical Android devices, and multi link operation networks have been an intermittent source of pain through 2026. If device pairing has been unreliable on a modern router, this is the fix to test.

  • Layout and Resource Editing no longer crashes when opening layout XML files, an issue that also appears in Rabbit 3 builds where plugins open those files
  • Lint 32.5.0, the version bundled with AGP 9.5.0, no longer throws a StackOverflowError on unary expressions inside KtToFirMapping
  • The SDK Manager no longer freezes the user interface when opening a project that sets sdk.dir, because the SDK scan no longer runs inside a write action on the event dispatch thread
  • Screen mirroring now honors the setting that turns the device display off, and the emulator orientation bug on tablet API 35 images is resolved

What the Codename Change Signals

Android Studio's release trains have followed a steady pattern through 2026. Rabbit 3 reached RC 1 in the Beta channel on November 11 with a single layout editor fix, which is what a train looks like when it is nearly done. Stingray 1 taking over the Canary channel means the next stable is close and a new feature window has opened behind it.

For teams that build Flutter apps against Android, the practical advice is unchanged. Stay on the stable channel for daily work, run the canary in a separate install when a specific fix matters, and watch the Gradle plugin version rather than the IDE version. AGP 9.6.0-alpha04 is an alpha, so it is a research target for dependency and shrinker issues, not something to put in a release branch.

The rest of the list is ordinary maintenance: the Database Inspector showing the wrong default database, unnecessary Gradle syncs on project reopen caused by a null cached before external project data loads, the Project Structure window freezing, Clear app storage not working from the App Configuration, and an orientation regression reported against tablet API 35 images.

None of those change how a Flutter project is structured. Each one costs an afternoon when it hits, which is the usual argument for keeping a canary install around: not to build releases with, but to confirm whether a specific annoyance has already been fixed upstream before spending time on a workaround.