Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

why self.locationManager stopUpdatingLocation doesn't stop location update

Tags:

Problem: It seems I can't stop Core Location from sending updates to my app / tracking.

What am I doing: In my viewWillAppear I call self.locationManager and pass it to a method to show user's location on the map (an instance of MKMapView). The getter is overridden to check for availability of the serive, to see whether its authorized. If so, it allocs/inits and startMonitoringSignificantLocationChanges and returns.

In viewDidDisappear, I call [self.locationManager stopUpdatingLocation]. But still I can see the location icon in the status bar. Even when I terminate the app by double tapping the home button and closing it, the icon is still there... even after extended amount of time (10+ minutes). When I go to the Settings App, it tells me that my app is still using location services (purple icon).

Question: What am I missing here? Why location update doesn't stop?

Thanks in advance.

like image 608
Canopus Avatar asked Feb 27 '12 17:02

Canopus


People also ask

How do I stop my location from updating?

You can control what location information your phone can use. Open your phone's Settings app. Under "Personal," tap Location access. At the top of the screen, turn Access to my location on or off.

What is CLLocationManagerDelegate?

The object that you use to start and stop the delivery of location-related events to your app. Current page is CLLocationManagerDelegate. Apple.


Video Answer


2 Answers

The opposite of startMonitoringSignificantLocationChanges is not stopUpdatingLocation, it is stopMonitoringSignificantLocationChanges.

You probably want to replace startMonitoringSignificantLocationChanges with startUpdatingLocation for the sake of more regular updates, unless you have a specific reason for monitoring only for significant location changes.

Check out the CLLocation documentation for further detail.

like image 64
jnic Avatar answered Sep 30 '22 11:09

jnic


I too just experienced the same problem as Canopus. It appears that even if stopUpdatingLocation is called the navigation pointer still resides on the status bar if I have showUserLocation enabled. Perhaps this is a bug? It may be as I am running and testing with iOS 4.2.1 and this issue may have been fixed in a later SDK.

I would think that if stopUserLocation is called it would also stop showing the user location since the view I am using it in has already disappeared and is subsequently deallocated.

It appears that you must set showUserLocation to NO before stopping user location updates.

Anyway, in my viewDidLoad method I have the following code:

self.mapView.showsUserLocation = YES; 

More code...

- (void)viewWillDisappear:(BOOL)animated {         if (locationManager)     {         mapView.showsUserLocation = NO;         [locationManager stopUpdatingLocation];     }      [super viewWillDisappear:animated]; }  - (void)dealloc {     if (locationManager)     {         [locationManager release];         locationManager = nil;     }      (other code) } 
like image 43
Christopher Avatar answered Sep 30 '22 11:09

Christopher