Fixed
Status Update
Comments
je...@google.com <je...@google.com> #2
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?
i donnot understand why is the data the same?
hu...@google.com <hu...@google.com> #3
the fractional part of the location data is exactly the same.
hu...@google.com <hu...@google.com> #4
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.
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.
an...@google.com <an...@google.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.
Description
Steps to reproduce
./gradlew help
, it will fail with:./gradlew help
again without updating Gradle, it will fail with:Root cause
At this changehttps://android.googlesource.com/platform/tools/base/+/27e840abc64595652fd05ac564660b983ef8a478 (merged Jun 7, 2022), we use a static variable to record whether the Gradle version check has been performed. This is to avoid running the check multiple times, once for each subproject.
However, a static variable is not suited for this use case for 2 reasons:
Potential fix
We can replace the static variable with a property in a cross-classloader BuildService. This will fix both the scope and lifetime issues above (the scope will be JVM-scoped, cross-classloader, and the lifetime will be per build).
We've been talking about this cross-classloader BuildService for a while, maybe this is a good opportunity to implement it.