IssueTracker

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

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

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.

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.

Missed the bug link for version CL 8.0.74: https://r8-review.git.corp.google.com/c/r8/+/87923

Thank you very much, it works for me now. But 4.x version also has similar problems, do you plan to fix it?

We don't expect to pull anymore updates to the 4.0 branch. Is it possible to use 8.0 or later?

OK, I'll try it with version 8.0.74.

Thanks for confirming the fix works and for reporting the issue! A fix will be pushed to 8.0, 8.1, 8.2 and 8.3 branches for R8.

I'm assuming you know the set up to use newer versions of R8 without AGP updates, but if not or others find this issue, I've included it below.

Amend your settings.gradle or settings.gradle.kts file with:

pluginManagement {
    buildscript {
        repositories {
            mavenCentral()
            maven {
                url = uri("https://storage.googleapis.com/r8-releases/raw")
            }
        }
        dependencies {
           classpath("com.android.tools:r8:8.0.74")
        }
    }
}

Since AGP 8, the R8 versions follow those of AGP, so if using AGP 8.0 use the latest version on the R8 8.0 branch (for this issue 8.0.74 or any later patch version).

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

• Android Studio Hedgehog | 2023.1.1 Patch 2
• Android Gradle Plugin 8.2.2

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

Comment added by automation: A postmortem has been automatically requested for this issue. Please author a postmortem on IRM. See go/android-postmortem-guidance for more context and details, including how to handle the case when this issue does not need a postmortem. If you have any questions not answered by go/android-postmortem-guidance, please email android-hygiene-tpm@, instead of reassigning the fixed bug. Thank you.

The fixes for this issue are now also available in:

• Android Studio Iguana | 2023.2.1 RC 1
• Android Gradle Plugin 8.3.0-rc01

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.