>coordinates associated with his wifi SSID. I don't believe there's a public API for this on iOS. In order to use wifi hotspots to assist with GPS on iOS, you'

>coordinates associated with his wifi SSID. I don't believe there's a public API for this on iOS. In order to use wifi hotspots to assist with GPS on iOS, you'd have to have location services enabled for the app. That being said, it's very possible the app is just holding onto the last coordinates it was able to receive when location services was enabled for the app. This may be the default sane behavior to allow it to boot faster, as it'll be able to show/use the previously cached location to load maps, rather than waiting for a GPS fix to be acquired. The author's test case of booting waze at a different location and then seeing if uber picks up that location after traveling away from it, without booting up the app is probably bogus, as unless granted, uber does not have access to location in background, and thus will not be able to access new location data while the app is not running. Once location services is disabled again, and the app is booted, the app should not see the previous location a GPS fix was able to be acquired (as that would break the implicit guarantee that an app using location services w/o background permissions should only see where you are currently, and not where you have been). It's my suspicion this data is probably not directly used, and rather is used to enrich analytic events emitted internally within uber.