We also use the Kotlin DSL Gradle to manage dependencies in our code.

Some Gradle settings like configuration cache, parallel, build cache, etc., will have different settings and can also break our code.Hopefully, some of the libraries that using kapt will be removed to increase build time as well.

Related to kapt, we also haven’t removed some of the dependencies which are directly related to kapt like glide, dagger, hilt, etc.We are also using an Annotation processor ( kapt) that has the potential to break if it is not fully supported on android Gradle plugin 7.0.0-alpha and Java JDK 11.Your project may be using a third-party plugin which is not compatible with the other plugins in the project or the version of Gradle requested by the project. We have installed several 3rd party Gradle plugins that have the potential to fail the building process on the CI Pipeline or local machines such as Triple-T, Jacoco, SonarQube, Hilt, Firebase Crashlytics.changing the JAVA_HOME environment variable. You can try some of the following options: - changing the IDE settings. Android Gradle plugin 7.0.0-alpha requires java JDK version 11, this requires a lot of changes in our codebase, plus in our team, 3 developers have different devices/machines with different operating systems, so it will cost a lot of money to just refactor the Java JDK.Īndroid Gradle plugin requires Java 11 to run.Here are the drawbacks we have found so far: Still, it provides some drawbacks, which eventually became the reason for us to downgrade the Android Gradle plugin version back to 4.1.3, which of course, already supports jetpack compose and is much more stable to implement in the production environment.

In the previous article, we used the android Gradle plugin version 7.0.0-alpha to develop UI using Jetpack Compose.

Android studio beta refactor fail