Android Studio 3.5 Canary 10 is now available in the Canary and Dev channels.
If you have Android Studio set to receive updates on the Canary or Dev channel, you can get the update by choosing Help > Check for Updates (Android Studio > Check for Updates on macOS). Otherwise, you can download it here.
Known issues
The following issues are known to occur with this update:- If you're using Gradle 5.3.0 or later, the patch from 3.5 Canary 9 to 3.5 Canary 10 might fail due to Issue #129240938. If you are using 3.5 Canary 9 and want to upgrade to 3.5 Canary 10, please download the IDE. Alternatively, you can explicitly stop the Gradle Daemon processes by using the command
gradle --stop
and then retry the update. We apologize for any inconvenience. - Due to a bug in 3.5 Canary 8, no patches are available from that version to any other. If you are using Canary 8 and want to upgrade, please download the IDE. We apologize for any inconvenience.
General fixes
This update includes fixes for the following public issues:Data Binding
- Issue #129157264: Finding references in XML data binding expressions from Java not working
- Issue #128643036: clicking on error does not navigate to file
- Issue #120561619: Data binding is breaking code coverage on AS 3.3 RC 1
- Issue #129093274: Add kapt lint for new plugin {} syntax
- Issue #127623509: Android Studio exception when attaching to process for debugging
- Issue #123461157: Run configuration doesn't remember last played emulator selection with drop down menu
- Issue #122956093: Run keystroke (^R) doesn't work if the Navigation Bar is turned off
- Issue #120429381: Pixelbprobe test fail on Windows.
- Issue #129260858: Android Studio 3.5 Canary 8 - Build Failed - Project Sync Failed
- Issue #127955232: Unexpected failure during lint analysis - NullPointerException
- Issue #124321895: Android Studio Import Drawable should rename imported drawable as per naming conventions
- Issue #115421146: Wrong classpath order when running JVM tests
We greatly appreciate your bug reports, which help us to make Android Studio better. If you encounter a problem, let us know by reporting a bug. Note that you can also vote for an existing issue to indicate that you are also affected by it.