Status Update
No update yet.
Comments
ch...@google.com
je...@google.com
hu...@google.com
i donnot understand why is the data the same?
bi...@google.com
hu...@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.
hu...@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.
hu...@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
hu...@google.com
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
hu...@google.com
an...@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.
[Deleted User] <[Deleted User]>
[Deleted User] <[Deleted User]>
mi...@mikehardy.net
hu...@google.com
Great to hear, thanks for your confirmation!
Description
In a gradle multi module project with an app and a library a deadlock
happens if you call gradle assemble the second time. The library
project must be included in the app. When you enable desugaring in the
application and now call gradle assemble wait till it is finished
and call it again the gradle build hangs with "Configuring projects".
This worked fine with AGP 8.2.0
I have attached a test project and a threaddump
STEPS TO REPRODUCE:
1. use the testproject in the attachment
2. call gradle assemble wait till it is finished
3. call gradle assemble again. Gradle hangs with Configuring projects
------------------
IMPORTANT: Please read
all required information.
------------------
Studio Build: #AI-232.10227.8.2321.11479570, built on February 21, 2024
Version of Gradle Plugin: 8.3.0
Version of Gradle: 8.6
Version of Java: 17
OS: Windows 10