Status Update
Comments
yo...@gmail.com <yo...@gmail.com> #2
i donnot understand why is the data the same?
pr...@gmail.com <pr...@gmail.com> #3
th...@gmail.com <th...@gmail.com> #4
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.
th...@gmail.com <th...@gmail.com> #5
Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.
pr...@gmail.com <pr...@gmail.com> #6
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
sg...@google.com <sg...@google.com> #7
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
ch...@google.com <ch...@google.com>
sg...@google.com <sg...@google.com> #8
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.
ap...@google.com <ap...@google.com> #9
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.
ap...@google.com <ap...@google.com> #10
ap...@google.com <ap...@google.com> #11
Branch: 8.5
commit c8ac09c8a408171ae438989d32817ac58f24b8f7
Author: Søren Gjesse <sgjesse@google.com>
Date: Thu Aug 15 15:43:44 2024
Fix java.util.ConcurrentModificationException
Fixes:
Change-Id: Ib59bed89294d831e26ae9e6e4e3b2aa63406958a
M src/main/java/com/android/tools/r8/shaking/Enqueuer.java
A src/test/java/com/android/tools/r8/annotations/NestedAnnotationsUnusedTest.java
A src/test/java/com/android/tools/r8/annotations/NestedAnnotationsUsedTest.java
ap...@google.com <ap...@google.com> #12
Branch: 8.6
commit b094951dc20f25541e696511bce1c35dee7fd639
Author: Søren Gjesse <sgjesse@google.com>
Date: Thu Aug 15 15:43:06 2024
Version 8.6.24
Bug:
Change-Id: I65e46ae214e4b788628eec6cec36d152a03997fe
M src/main/java/com/android/tools/r8/Version.java
ap...@google.com <ap...@google.com> #13
Branch: 8.6
commit d6058fde773d135ade972df5e70cb9226537fe11
Author: Søren Gjesse <sgjesse@google.com>
Date: Thu Aug 15 15:42:51 2024
Fix java.util.ConcurrentModificationException
Fixes:
Change-Id: Ib59bed89294d831e26ae9e6e4e3b2aa63406958a
M src/main/java/com/android/tools/r8/shaking/Enqueuer.java
A src/test/java/com/android/tools/r8/annotations/NestedAnnotationsUnusedTest.java
A src/test/java/com/android/tools/r8/annotations/NestedAnnotationsUsedTest.java
sg...@google.com <sg...@google.com> #14
The issue has been fixed. You can use R8 8.5.41 with AGP 8.5.2 using the following patch:
diff --git a/settings.gradle b/settings.gradle
index fbba233..9b89dcb 100644
--- a/settings.gradle
+++ b/settings.gradle
@@ -1,4 +1,15 @@
pluginManagement {
+ buildscript {
+ repositories {
+ mavenCentral()
+ maven {
+ url = uri("https://storage.googleapis.com/r8-releases/raw")
+ }
+ }
+ dependencies {
+ classpath("com.android.tools:r8:8.5.41")
+ }
+ }
repositories {
google {
content {
When switching to AGP 8.6.0 please use R8 8.6.24 as this fix most likely will not go into AGP until 8.6.1.
an...@google.com <an...@google.com> #15
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 Koala Feature Drop | 2024.1.2 Patch 1
- Android Gradle Plugin 8.6.1
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!
Description
with AGP 8.5.0 (also 8.5.1 and 8.5.2) i'm getting
project affectedhttps://github.com/SelvinPL/SyncFrameworkAndroid/tree/1.5.12
problem seems to only appear on Windows
Full stacktrace: