I am trying to make sense of an inexplicable situation — starting February 15, a remarkably high percentage of the location readings we captured in our app are reporting exa
it is a Google Play Service issue, reported internally here and it will be fixed from version 13.4.0