Fixed
Status Update
Comments
za...@gmail.com <za...@gmail.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?
za...@gmail.com <za...@gmail.com> #3
the fractional part of the location data is exactly the same.
ga...@google.com <ga...@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.
ga...@google.com <ga...@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.
sp...@google.com <sp...@google.com>
sp...@google.com <sp...@google.com> #6
I only aply permission android.permission.ACCESS_COARSE_LOCATION.I use android.location.Location in the program.
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
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
an...@google.com <an...@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.
Description
DESCRIBE THE ISSUE IN DETAIL:
While testing AGP 8.3 RCs, I noticed a strange issue where lint models types from sibling source sets as
<ErrorType>
. The simplest example of this is having a type inmain
that is used intest
sources.Example:
We have a kotlin.jvm project that defines this class in its
main
source setThen we also have a test in its
test
source set that usesSlackJvmTest
like soWhere things get weird is we have a lint check that enforces use of our common base test classes like
SlackJvmTest
, and that lint check suddenly started reporting an error on this case. After investigating, we found it's because lint reports the superclass as anErrorType
, where theasSourceString()
of that class looks like thisReproduced using both the bundled lint and also
android.experimental.lint.version=8.4.0-alpha10
. This also appears to affect all references (methods, classes, etc).