Android Studio Stingray 1 Canary 1 came out on 16 November 2026 with Android Gradle Plugin 9.6.0-alpha04. The release post has no feature list, only 14 fixes, and four of them are bugs that hit stable builds on AGP 9.5 today: fat AARs with several nested jars fail to merge Java resources, the generated BuildConfig.java breaks -Xlint:all -Werror on JDK 23 and newer, R8’s configuration.txt changes order between machines, and Lint 32.5.0 can crash with a StackOverflowError. If any of those is blocking you, you do not need a canary IDE: the stopgaps are below, and the real fix arrives with AGP 9.6.
This post is a table we built from the Stingray 1 Canary 1 release post, with each issue linked, cross-checked against the other Android Studio releases of the last four weeks.
Why we did this: Peepal, Shopkeeper and the BMDB TV app build with AGP on CI, and our React Native Android builds pull in vendor AARs. Two of these bugs are the kind that fail a release build at night with no code change.
Which Studio ships which AGP right now
| Release | Date | Channel | AGP named in the post |
|---|---|---|---|
| Rabbit 2 and Patch 1 | 28 Oct and 5 Nov 2026 | Stable | none in the post; the preview page lists AGP 9.5.0 as stable |
| Rabbit 3 Canary 3 | 5 Nov 2026 | Canary | 9.6.0-alpha03 |
| Rabbit 3 RC 1 | 11 Nov 2026 | Beta | the version is missing from the post |
| Stingray 1 Canary 1 | 16 Nov 2026 | Canary | 9.6.0-alpha04 |
Stingray is the line after Rabbit 3. The Android Studio preview features page was last updated on 28 October and has no Stingray section yet, so there is nothing to say about Stingray features. For what Rabbit 3 itself changes, see our post on Rabbit 3 RC 1, and for the Gradle side of AGP 9.6, our AGP 9.6 preview.
The build fixes, and who they hit
| Fix | Issue | Introduced | Who is affected | Until AGP 9.6 is stable |
|---|---|---|---|---|
| Fat AARs with multiple nested jars fail to merge Java resources | 581925548 | AGP 9.5 | Apps consuming vendor SDKs shipped as one big AAR (payment, KYC and analytics SDKs often are); RN apps that link such SDKs | Stay on AGP 9.4 for that app, or test 9.6.0-alpha04 on a branch |
Generated BuildConfig.java has a dangling /** comment |
567587949 | not stated | Any module compiling Java with -Xlint:all -Werror on JDK 23+ |
Turn off only the dangling-doc-comments lint (card below) |
Shrinker rule files from one dependency are read in filesystem order, so R8 configuration.txt is not deterministic |
581609407 | not stated | Teams that diff release outputs or check reproducible builds between CI and local | Expect noise in that file across machines; do not fail a build on it yet |
Warning that apps will fail under Isolated Projects with implementation(project(...)) |
582417470 | not stated | Multi-module projects that turned on Isolated Projects | Read the warning as a heads-up, not a broken build |
Lint 32.5.0 crashes with StackOverflowError in KtToFirMapping on an extension call on (-1) |
581949596 | AGP 9.5.0 (Lint 32.5.0) | Kotlin modules with an extension call on a parenthesised negative literal, such as (-1).ext |
Find those calls (grep below); lint is crashing, so a baseline does not help |
The other fixes are IDE and tooling bugs: adb pair over a Wi-Fi 7 MLO network (409806985), the wrong default database in Database Inspector (584147741), a tablet orientation bug in Running Devices on API 35 (476026968), an unnecessary Gradle sync on reopen (582423009), a crash opening layout XML (583343830, also fixed in Rabbit 3 RC 1), a Project Structure freeze (166760789), “Clear app storage” not working (567222753), mirroring not turning the device screen off (574545175) and an SDK Manager freeze on projects with sdk.dir (581018315). The wireless pairing fix is the one people notice first: new routers advertise MLO by default.
The -Werror stopgap
JDK 23 added a dangling-doc-comments lint to javac, and -Xlint:all turns it on. A /** comment that documents nothing, which is what the issue reports in the generated BuildConfig.java, then becomes an error under -Werror. Dropping -Werror throws away every other warning check; disabling only that one lint keeps them.

Turn off one lint, keep the rest, and remove the exclusion when AGP 9.6 is stable.
def lint = "-Xlint:all,-dangling-doc-comments"
tasks.withType(JavaCompile) {
options.compilerArgs += [lint, "-Werror"]
}
This also drops the check for your own dangling doc comments, so put a note next to it and remove it with the AGP bump.
Five greps to see if you are affected
Before deciding whether to wait or move to the 9.6 alpha, check which of these fixes touch your project. We tried the script on the Android folder of a published React Native library; it runs and prints nothing when no fix applies.

Run from the root of the Android project; each line maps to one row in the table above.
grep -rln --include="*.gradle*" -e "-Werror" .
grep -n "isolated" gradle.properties
grep -rn "implementation(project(" --include="*.gradle.kts" .
grep -rnE "\(-[0-9]+\)\." --include="*.kt" .
find . -name "*.aar" -size +1M
A large local AAR is only a hint: the merge bug needs several nested jars inside one AAR. Unzip it and look at its libs/ folder to be sure.
What we would do this week
- Stay on Rabbit 2 and AGP 9.5.0 for release builds; Stingray is a canary and its AGP is an alpha.
- If the fat AAR bug blocks a build, pin AGP 9.4 for that app rather than shipping on an alpha plugin.
- Apply the
-dangling-doc-commentsexclusion if you build with-Werroron JDK 23+, with a note to remove it. - Watch for AGP 9.6.0 beta: these fixes reach a stable plugin only through it.
Sources
- Android Studio Stingray 1 Canary 1 now available, 16 November 2026
- Android Studio Rabbit 3 RC 1 now available, 11 November 2026
- Android Studio release blog index, Rabbit 2 and Rabbit 3 posts
- Android Studio preview features, last updated 28 October 2026



