IssueTracker

Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

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.

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.

Do we already have a tracking bug to re-evaluate how we collect stats? ATM not showing warnings is the right thing from user POV, but we should make explicit choices how to handle this.

Filed a new ticket b/288584713 :)

Thanks Bingran, but I just wanted to note that this is a very basic project (New Project template > Empty Activity). That means most projects will start hitting this code path (or were hitting it before without us knowing it -- comment #4).

Collecting correct data is crucial because it's the foundation of everything else. And we'll never know about these issues unless we throw an error/warning.

I don't know the actual consequence of hitting that code path (it may turn out to be trivial), but thought I should point that out so you can evaluate the priority of this issue.