Checks to see if the position is valid before OnLocationUpdate call.
A StopProvider call from the Engine was being received while a message
was being processed to go to the Engine from the Client. This caused
the LocationArbitrator to reset. When we came back from sending,
the callback tries to get the new location from the LocationArbitrator,
but since it was reset, it now has an invalid location. This adds a
check for this case.
BUG=645230
Review-Url: https://codereview.chromium.org/2331513002
Cr-Commit-Position: refs/heads/master@{#419258}
2 files changed
