Android Studio 4.0 Beta 4 is now available in the Beta channel.
If you have Android Studio set up to receive updates on the Beta 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.
Build Analyzer disabled
The Build Analyzer is disabled in Android Studio 4.0 Beta 4. It will be re-enabled in Beta 5.General fixes
This update also includes fixes for the following public issues:Android Gradle Plugin
- Issue #147535554: Core library desugaring not applied to instrumentation tests
- Issue #146165298: Android library projects should only apply multidex to androidTestImplementation
- Issue #146869072: Task failed on mergeExtDex
- Issue #152428342: Build seems to be stuck
- Issue #150325708: Build Flavour resets itself to default each time I restart Android Studio
- Issue #151969439: R8 raise NullException while perform :app:dexBuilderDebugAndroidTest
- Issue #151207121: Many warnings when using desugared library
- Issue #149891395: Kapt-generated files not recognized in IDE as sources
- Issue #151964515: Endless loop when displaying JavaDoc for styles with cycles
- Issue #151409564: Lint fails to detect MotionLayout Constraints
- Issue #150198810: Bug: false positive error of version check
- Issue #144274828: "Build resource" action runs JPS builder in Android Studio
- Issue #150583984: ApkProvisionException: No outputs for the main artifact of variant: debug
- Issue #151649643: coreLibraryDesugaringEnabled = true leads to ClassNotFoundException on debug builds
- Issue #150274427: RET should be handled by the ASM jsr inliner
- Issue #140955511: View binding build fail: Unresolved reference
- Issue #151317169: Missing nullability annotations on bind and inflate fields / return types
For information on new features and changes in all preview builds of Android Studio 4.0, see the Android Studio Preview release notes. For details of bugs fixed in each preview release, see previous entries on this blog.
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.