getLastLocation isn't necessarily the current location

My Android app uses the fused location provider client's getLastLocation method to get the user's location when needed. Usually this works great. I have noticed, however, that it sometimes gets a stale location (where the user was during a previous fetch). When having the exact, most up-to-date location is necessary, I use requestLocationUpdates and have found that this works well.