We hit this while upgrading an Android project to both: Android Gradle Plugin 9.2.0 SonarQube Gradle plugin 7.3.0.8198 The previous CI baseline, before this upgrade stack, used SonarQube Gradle plugin 7.2.3.7755 and completed successfully. What worked before Before this upgrade stack, the Sonar task completed successfully with: SonarQube Gradle plugin 7.2.3.7755 sonar.gradle.skipCompile=true CI command: ./gradlew sonar -Dsonar.token=... -Pandroid.newDsl=false That baseline still logged Java analyzer warnings about unresolved Android/JDK types, but they were non-fatal and the build ended with BUILD SUCCESSFUL. What fails now After upgrading to AGP 9.2.0 and SonarQube Gradle plugin 7.3.0.8198, the same CI command fails: Execution failed for task ':sonar'. > org.sonar.java.AnalysisException: Your project contains .java files, please provide compiled classes with sonar.java.binaries property, or exclude them from the analysis with sonar.exclusions property. The project contains Java files in Android library modules, including: regular Java sources under src/main/java/... generated Java sources registered with variant.sources.java?.addStaticSourceDirectory(...) Possible root cause From the scanner source, 7.3.0.8198 added a new AGP 9 code path in AndroidConfig. That path appears to compute sonar.java.binaries using this hard-coded directory shape: build/intermediates/javac/ /classes For AGP 9.2.0, the actual JavaCompile output directory is: build/intermediates/javac/ /compile JavaWithJavac/classes For example: build/intermediates/javac/debug/compileDebugJavaWithJavac/classes Because the scanner later filters non-existing path properties before analysis, the guessed sonar.java.binaries path is removed. The scanner then sees Java source files but no valid sonar.java.binaries, which triggers the fatal Java analyzer error above. Suggested direction Instead of synthesizing the class output path from the component name, the AGP 9 path should use the matched JavaCompile task’s actual destinationDirectory, similar to the legacy AGP path that used variant.getJavaCompileProvider().getOrNull().getDestinationDirectory(). This avoids depending on AGP internal output directory layout and should be more robust for custom Gradle/AGP behavior.

Hi, Thanks for this report. I believe the tickets created in this thread cover the problem you’re seeing. Do you agree? Thx, Ann

It seems like you may have linked your comment to the original thread. Could you please check your original reply? This PR is associated with the fix for this issue: Fix AGP 9 Java binaries resolution by bc-lee · Pull Request #501 · SonarSource/sonar-scanner-gradle · GitHub Please take a look. Thanks.

Hi, Sorry about that! Try this one: [image] Sonar Scanner 7.3.0: AGP 9 MissingValueException Root Cause, CLI Workaround & Coverage Trade-offs sonarqube-serverSonarQube Server / Community Build Hello @Gustavo_Morales, Thank you for the feedback and your very detailed report on the latest version of the scanner for Gradle ! I have created a ticket for us to fix the issues with missing dependencies in the SonarResolverTask and another one to fix problems with the computation of compiled classes. As you have mentioned, we are aware of the issues with the computation of properties at configuration time and planning to move this logic to the execution phase. Best regards, Aurélien Ann

Hi, We are currently experiencing the same generated file issue and are waiting for the PR to be merged and rolled out with the new version. Do you already have an estimated timeline for the next Sonar plugin release? This would help us plan our update accordingly. Thanks, Veli

Hi @vakdeniz, Welcome to the community! Unfortunately, I don’t have a timeline for you. Ann

Hi @bc-lee, @vakdeniz, We have just released a new version of the scanner that should address the issue reported here.

Gradle scanner 7.3.0 sets invalid Java binaries for AGP 9.2

SonarQube Server / Community Build

ganncamp (G Ann Campbell) May 11, 2026, 5:23pm 4

Hi,

Sorry about that!

Try this one:

Ann

Topic		Replies	Views
Sonar-scanner-gradle 7.3.0: Incorrect sonar.java.binaries SonarQube Server / Community Build gradle , scanner , android , issues , sonar-scanner	4	352	May 27, 2026
Analysis error with Gradle Plugin 7.3.0.8198 SonarQube Server / Community Build	1	116	May 29, 2026
SonarScanner for Gradle 7.3.1 Sonar Updates gradle , scanner , android , plugin , sonar-scanner	3	436	June 9, 2026
Sonarcloud not working with Android Gradle Plugin 9.1.0 SonarQube Cloud gradle , scanner , android	8	1489	May 6, 2026
How to provide compiled Java classes with sonar.java.binaries property using the Sonar Gradle Plugin SonarQube Server / Community Build java , sonarqube , gradle , android	5	559	November 24, 2025

Gradle scanner 7.3.0 sets invalid Java binaries for AGP 9.2

Related topics