Android Studio 4.1.2 is available now for everyone on the Stable Channel. So basically Android Studio is the official IDE for Android Development, which in layman terms means that it simply includes almost everything that you will require to build the Android apps. Now if you already have an Android Studio previously build on the Stable channel, you can easily get the update by following the simple steps on how to get it, and they are given below. So that you know how to go about it in order to get the update.
- Click on Help
- Check for any new updates (Android Studio)
- Check for the updates on your macOS.
Otherwise, you can directly download it by clicking here.
For more information on the new features and the latest changes that came in all of the releases of Android Studio, and from here you can see all the Android Studio release notes.
The makers of this application very much appreciate the bug reports, that helps us build the Android Studio better. So let’s say that you’ve encountered a problem, it is advisable that you let the makers know about the issue by reporting a bug in their system. And plus, you can also vote for some existing issues that even you’re facing along with your peers and notify them that you’re affected by that same issue too.
General fixes made in this update:
This update includes the fixes that were voted in the previous update by the public in general, some of them are listed below:
- The app is failed to run when it’s upgraded to AGP 4.1
- R8 suffering from Slowdown and Timeout due to the number of the proguard rules.
- Included Default method called using invoke-static instead of invoke-interface with AGP 4.1 (r8 2.1.62)
- Pressing the run button is not able to install the app on the device, but Android Studio is reporting the operation succeeded.
- Application not killed after install.
- The studio is building old files.
- Whenever you click “Run” every time, the changes made in the code are not applied. And one has to run it twice to apply those changes.
- Sync fails for the unit tests in libraries when the Android resources are disabled.
- JaCoCo plugin is hanging for a long time.
- AS 4.1+ fails to run JUnit tests, which leads to complaining about the JUnit version being too low.
- The embedded emulator on Windows never really closes the emulator process.
