Fixed
Status Update
Comments
hu...@google.com <hu...@google.com>
je...@google.com <je...@google.com>
al...@google.com <al...@google.com>
al...@google.com <al...@google.com>
al...@google.com <al...@google.com>
se...@team.bumble.com <se...@team.bumble.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?
ki...@gmail.com <ki...@gmail.com> #3
the fractional part of the location data is exactly the same.
ki...@gmail.com <ki...@gmail.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.
Description
Related to https://issuetracker.google.com/issues/263876380 , I am trying to configure Checkstyle and Detekt static analysis tools to work with the new issue 263876380 , I am using the
gradle-api
AGP artifact. PerVariant#sources.java.all
API to get the files to pass to Checkstyle. I am noticing that this API includes all sources that are generated by tasks registered as code generation tasks, which makes sense for the API in general, but does not work for static analysis tools like Checkstyle or Detekt.Ideally we need an API that will give us only the source files that are actually in the repo and human-editable. Scanning generated files is not useful because developers usually can't edit them to fix violations, and these tools expect you to not pass the files to the tool in the first place and don't provide great options for filtering them out after the fact.
Last tested with AGP 8.1.0-alpha01