Multiple Gradle daemons might be spawned because the Gradle JDK and JAVA_HOME locations are different. Project 'android' is using the following JDK location when running Gradle: '/nix/store/51qj1qsns3arj8lj3izngkb7vxk1zcnw-android-studio-stable-2023.1.1.26-unwrapped/jbr' The system environment variable JAVA_HOME is: '/nix/store/drg93za9f2d6sa843kzr9xlxhx75mm2g-android-studio-stable-2023.2.1.25-unwrapped/jbr' If you dont need to use different paths (or if JAVA_HOME is undefined), you can avoid spawning multiple daemons by setting JAVA_HOME and the JDK location to the same path.
aleeusgr
commented
2 months ago
Multiple Gradle daemons might be spawned because the Gradle JDK and JAVA_HOME locations are different. Project 'android' is using the following JDK location when running Gradle: '/nix/store/51qj1qsns3arj8lj3izngkb7vxk1zcnw-android-studio-stable-2023.1.1.26-unwrapped/jbr' The system environment variable JAVA_HOME is: '/nix/store/drg93za9f2d6sa843kzr9xlxhx75mm2g-android-studio-stable-2023.2.1.25-unwrapped/jbr' If you dont need to use different paths (or if JAVA_HOME is undefined), you can avoid spawning multiple daemons by setting JAVA_HOME and the JDK location to the same path.