Setting JVM toolchain does not affect JavaCompile targetCompatibility value [260059413]

Fixed

Bug

Status Update

No update yet.

Description

eg...@gmail.com

created issue #1

Nov 22, 2022 04:24PM

When Gradle JVM toolchain is configured in Android project, I see it properly configures Kotlin compilation with jvmTarget value equals to toolchain JDK. Though JavaCompile targetCompatability stays as JavaVersion.VERSION_1_8. In the logs I see JavaCompile uses JDK from configured toolchain.

Toolchain should behave the same as in JVM-only project and configure JavaCompile.targetCompatibility value.

Issue is related to this one

Workaround is to specify these values explicitly in android extension:

android {
   compileOptions {
       sourceCompatibility JavaVersion.VERSION_..
       targetCompatibility JavaVersion.VERSION_..
   }
}

STEPS TO REPRODUCE:

Use AGP 7.4.0-beta02 in project
Also apply "org.jetbrains.kotlin.android" plugin version 1.7.20
Configure toolchain via following configuration:

kotlin {
    jvmToolchain {
        languageVersion.set(JavaLanguageVersion.of(17))
    }
}

Run build compilation via :assembleDebug and observe following warning in :compileKotlin task output:

'compileDebugJavaWithJavac' task (current target is 1.8) and 'compileDebugKotlin' task (current target is 17) jvm target compatibility should be set to the same Java version.

Comments

em...@google.com <em...@google.com> Nov 22, 2022 07:29PM

Assigned to an...@google.com.

je...@google.com <je...@google.com> Nov 29, 2022 06:37PM

Reassigned to ga...@google.com.

ga...@google.com <ga...@google.com> Jan 5, 2023 02:44PM

Reassigned to bi...@google.com.

ga...@google.com <ga...@google.com> #2Jan 5, 2023 03:45PM

for example, many different devices return the same longitude and latitude.such as : longitude is 121.474000 and latitude is 31.230001.
i donnot understand why is the data the same?

pa...@gmail.com <pa...@gmail.com> #3Jan 16, 2023 11:44AM

the fractional part of the location data is exactly the same.

Message last modified on Jan 16, 2023 11:44AM

ja...@google.com <ja...@google.com> #4Feb 3, 2023 08:56PM

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

What steps are needed to reproduce this issue? Frequency of occurrence?

Which Android build are you using? (e.g. AP4A.241205.013.A1)

Which device did you use to reproduce this issue?

Can you confirm if this issue is reproducible on a Pixel/Nexus device?

Please provide a sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.

Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:

https://developer.android.com/studio/debug/bug-report#bugreportdevice

Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.

pa...@gmail.com <pa...@gmail.com> #5Feb 3, 2023 10:08PM

Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.

At...@web.de <At...@web.de> #6Feb 4, 2023 02:05AM

I only aply permission android.permission.ACCESS_COARSE_LOCATION.I use android.location.Location in the program.
for example,we hava 100 users.
20 users returned the same location information, longitude is 121.474000 and latitude is 31.230001。
30 users returned the same location information, longitude is 122.474000 and latitude is 32.230001。
15 users returned the same location information, longitude is 120.474000 and latitude is 30.230001。

as for Android build,all versions have it.
I dont reprodouce this issue.

what may be the cause of this issue?please

bi...@google.com <bi...@google.com> Feb 6, 2023 04:33PM

Accepted by bi...@google.com.

bi...@google.com <bi...@google.com> #7Feb 11, 2023 01:30AM

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

Message last modified on Feb 11, 2023 01:35AM

pa...@gmail.com <pa...@gmail.com> #8Feb 11, 2023 09:13AM

Thanks for reporting this issue.

COARSE_LOCATION typically takes location information from the nearby cell tower. If many users are near the same cell tower, each of those users will be given the same position. Using a FINE position will give much more detailed information.

Also, in certain areas, for privacy reasons, a less-exact location will be given, and that less-exact location might be identical for many users. Again, a fine-location configuration will return more precise location data.

bi...@google.com <bi...@google.com> #9Feb 13, 2023 07:57PM

We believe with reference to the above comment, your query has been answered, hence closing the bug. Please feel free to re-open the issue in the future if desired.

hu...@google.com <hu...@google.com> #10Mar 7, 2023 02:16PM

Thank you very much! it is very useful to me . It solved my confusion.

bi...@google.com <bi...@google.com> #11Mar 7, 2023 05:09PM

Marked as fixed.

Thanks for working on it and sharing the updates, Hung!

hu...@google.com <hu...@google.com> #12Mar 7, 2023 05:59PM

Sure thing, I've also filed Issue 272050599 to address the remaining issue in comment #10.

cl...@vippsmobilepay.com <cl...@vippsmobilepay.com> #13Oct 3, 2024 09:11AM

According to this

https://developer.android.com/build/jdks bullet 3 in

comment #10

should have been the Gradle JDK.

pa...@gmail.com <pa...@gmail.com> #14Oct 3, 2024 11:01AM

Historically the default is 1.8, so I think they just kept that for backwards compatibility.

hu...@google.com <hu...@google.com> #15Oct 7, 2024 11:14AM

We've updated that page to match the current behavior: https://developer.android.com/build/jdks#source-compat. Thank you for letting us know!

cl...@vippsmobilepay.com <cl...@vippsmobilepay.com> #16Oct 7, 2024 11:45AM

#15 You need to update the diagram at the top of the page as well.

hu...@google.com <hu...@google.com> #17Oct 7, 2024 01:19PM

Ah yes, that diagram and the entire page will probably need another revamp once AGP has built-in support for Kotlin compilation (Issue 259523353) with a simpler DSL (Internal issue comment). // cc Scott

Message last modified on Oct 7, 2024 01:24PM

pa...@gmail.com <pa...@gmail.com> #18Oct 7, 2024 06:27PM

Is that close enough to delay fixing the current state?

hu...@google.com <hu...@google.com> #19Oct 8, 2024 11:10AM

I've filed Issue 372185847 to discuss this.