Status Update
No update yet.
Comments
ls...@google.com
je...@google.com
zo...@gmail.com
i donnot understand why is the data the same?
zo...@gmail.com
cm...@google.com
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:
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.
cm...@google.com
Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.
mi...@google.com
mi...@google.com
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
zo...@gmail.com
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
mi...@google.com
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.
pa...@gmail.com
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.
mi...@google.com
pa...@gmail.com
What do you mean by unit test workflow?
Also the issue was/is tagged blocking 8.3 RC, could it be backported?
mi...@google.com
I mean for unit test rather than android test. It cannot be backported anymore to 8.3.
an...@google.com
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 Jellyfish | 2023.3.1 Canary 3
- Android Gradle Plugin 8.4.0-alpha03
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!
zo...@gmail.com
Thank you! :bow:
mi...@google.com
Hi, update here. I was able to cherry pick this fix, so it will be available in 8.3.
pa...@gmail.com
Awesome 😎!
an...@google.com
The fixes for this issue are now also available in:
- Android Studio Iguana | 2023.2.1 Beta 2
- Android Gradle Plugin 8.3.0-beta02
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
an...@google.com
The fixes for this issue are now also 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.
ji...@gmail.com
- Android Studio Hedgehog | 2023.1.1 Patch 2
- Android Gradle Plugin 8.2.2
The Jacoco plugin extension version '0.8.9' is not currently available in the Android Gradle Plugin. Setting the version to 0.8.8
ro...@gmail.com
Now we have the following issue:
- Android Studio Iguana | 2023.2.1 Beta 2
- Android Gradle Plugin 8.2.2
The Jacoco plugin extension version '0.8.9' is not currently available in the Android Gradle Plugin. Setting the version to 0.8.8
ge...@amazon.com
Android Studio Iguana | 2023.2.1 Beta 2
Android Gradle Plugin 8.3.0-beta02
and I'm still seeing the error:
The Jacoco plugin extension version '0.8.9' is not currently available in the Android Gradle Plugin. Setting the version to 0.8.8
mi...@google.com
Hi, thank you for the update. For the specific warning you are seeing, this has not been resolved until AGP 8.4. It should be available in any versions of 8.4.
Description
Setting JaCoCo version, done via:
```
jacoco {
toolVersion = '0.8.10'
}
```
No longer has any effect when using AGP 8.2.0.
STEPS TO REPRODUCE:
1. Clone/pull down
2. Run `jacocoTestReport` on main branch
3. Run `jacocoTestReport` on agp-8-2-0 branch
ATTACH SCREENSHOTS/RECORDINGS OF THE ISSUE
1. main branch JaCoCo output showing `0.8.10` as JaCoCo version
2. agp-8-2-0 branch JacoCo output showing `0.8.8` as JaCoCo version
ATTACH LOG FILES (Select Help > Show Log in Files, or Show Log in Finder on a Mac)
N/A
------------------
IMPORTANT: Please read
all required information.
------------------
Studio Build: Android Studio Hedgehog | 2023.1.1 Beta 1 / AI-231.9392.1.2311.10680768
Version of Gradle Plugin: 8.2.0-beta01
Version of Gradle: 8.2
Version of Java: 17 (Eclipse Temurin 17.0.8)
OS: MacOS Monterey 12.6.8