From fcc4076b947686c7379d8c70f017b666a6b374e0 Mon Sep 17 00:00:00 2001 From: Patrick Bertsch Date: Fri, 14 Aug 2026 22:11:12 -0600 Subject: [PATCH] fix: remove hardcoded macOS-only org.gradle.java.home from gradle.properties MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit android/gradle.properties hardcoded org.gradle.java.home=/Library/Java/JavaVirtualMachines/temurin-21.jdk/Contents/Home — a path that only exists on one macOS laptop, never on flutter-probe's Android E2E CI runner (ubuntu-latest), where it broke every Gradle build with "Java home supplied is invalid" immediately after fixing the nightowl_sdk pub-resolution failure (AlphaWaveSystems/flutter-probe#216). Removing it lets Gradle fall back to the JAVA_HOME environment variable (or PATH), which is how both CI's actions/setup-java step and any normal local dev environment already provide a JDK — no functional change for anyone who wasn't relying on that one specific hardcoded path. Verified locally: `flutter build apk --debug --dart-define=PROBE_AGENT=true` still succeeds with the property removed, resolving a JDK via the normal Flutter/Gradle toolchain lookup instead. --- mobile/android/gradle.properties | 1 - 1 file changed, 1 deletion(-) diff --git a/mobile/android/gradle.properties b/mobile/android/gradle.properties index 9342c95..fbee1d8 100644 --- a/mobile/android/gradle.properties +++ b/mobile/android/gradle.properties @@ -1,3 +1,2 @@ org.gradle.jvmargs=-Xmx8G -XX:MaxMetaspaceSize=4G -XX:ReservedCodeCacheSize=512m -XX:+HeapDumpOnOutOfMemoryError android.useAndroidX=true -org.gradle.java.home=/Library/Java/JavaVirtualMachines/temurin-21.jdk/Contents/Home