You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 9, 2018. It is now read-only.
Go to Settings and turn off Location Services for your app
Go back to your app
Go to Settings and turn Location Services back on for your app
Go back to your app
Actual Results
mapViewWillStartLocatingUser: is never called at any point
mapView:didUpdateUserLocation: is never called after Location Services are revoked, even after they're turned back on
Expected Results
mapViewWillStartLocatingUser: should be called once when Location Services are allowed the first time, and once again when Location Services are reinstated
This is consistent with the behavior of mapViewDidStopLocatingUser:, which is called both when Location Services are blocked on first request and when Location Services are revoked later
mapView:didUpdateUserLocation: should resume being called for location changes after Location Services are reinstated
The text was updated successfully, but these errors were encountered:
In mapbox/mapbox-gl-native#1491, I wound up adding code that double-checks +[CLLocationManager authorizationStatus] when the host app returns to the foreground. It’s for a different purpose, not the user dot, but the same approach would work here. I couldn’t find any other reliable way to get this notification.
Steps to Reproduce
showsUserLocation
toYES
.Actual Results
mapViewWillStartLocatingUser:
is never called at any pointmapView:didUpdateUserLocation:
is never called after Location Services are revoked, even after they're turned back onExpected Results
mapViewWillStartLocatingUser:
should be called once when Location Services are allowed the first time, and once again when Location Services are reinstatedmapViewDidStopLocatingUser:
, which is called both when Location Services are blocked on first request and when Location Services are revoked latermapView:didUpdateUserLocation:
should resume being called for location changes after Location Services are reinstatedThe text was updated successfully, but these errors were encountered: