Status Update
No update yet.
Comments
ya...@google.com
ch...@google.com
ri...@google.com
i donnot understand why is the data the same?
ri...@gmail.com
ri...@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.
my...@gmail.com
Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.
mr...@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
ri...@google.com
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
my...@gmail.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.
ri...@google.com
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.
an...@google.com
yc...@gmail.com
We are going to move towards suggesting people use strict mode, in which case the keep rule is needed, so it would be good to add keep rules for all of the reflectively looked up strings in crashlytics.
Is there a gradle property to enable this "strict mode"?
ri...@google.com
No gradle property, this is controlled by keep xml files:
You should not do this if you are a library developer (since this is global)
my...@gmail.com
Hi it seems working in alpha16 safe mode. Strict mode seems to still remove that string resource though?
ri...@google.com
if you use strict mode you need the keep rule. In strict mode we ignore string constants in the program.
In the ideal world, no resources are looked up using getIdentifier calls (but we are not in a ideal world). Anything that is looked up reflectively using getIdentifier calls should have keep rules for them.
Description