CLLocationManager stopUpdatingLocation not working?

[gbhatnag]

I am working on an application that uses the phone's current location. I've created a class that has a CLLocationManager instance and implements the CLLocationManagerDelegate protocol to get location updates.

Once I receive a "valid" location update (based on how recent or accurate the location update is), I want the locationManager to stop sending updates. I do this by calling:

[locationManager stopUpdatingLocation]

After the stopUpdatingLocation call, there is no way that startUpdatingLocation can be called again.

On the simulator, this works fine (perhaps because there is only one hard-coded location: Cupertino). On a device, this does not work and I continue to get updates even after the stopUpdatingLocation call.

Anybody have similar problems? Is this a bug, or, am I missing something about the way CLLocationManager's startUpdatingLocation and stopUpdatingLocation work? Thanks very much.

[debug77]

I've got exactly the same problem. Did you ever get to the bottom of it, or did anyone else?

[greenflame]

*BUMP*

[S.LakshmiKanth Reddy]

i am facing the problem , like CLLocationManager is returning me the same old location that it got when the application has started.

can anyone help me out in solving this issue.

[greenflame]

Originally Posted by S.LakshmiKanth Reddy

i am facing the problem , like CLLocationManager is returning me the same old location that it got when the application has started.

can anyone help me out in solving this issue.

Depends on where you are calling startUpdatingLocation.

Also make sure you have implemented...

- (void)locationManagerCLLocationManager *)manager didUpdateToLocationCLLocation *)newLocation fromLocationCLLocation *)oldLocation

This method recognises when the current location has changed. Use this method to detect whether the current location is getting updated.

[Danny]

Originally Posted by greenflame

Depends on where you are calling startUpdatingLocation.

Also make sure you have implemented...

- (void)locationManagerCLLocationManager *)manager didUpdateToLocationCLLocation *)newLocation fromLocationCLLocation *)oldLocation

This method recognises when the current location has changed. Use this method to detect whether the current location is getting updated.

In didUpdateToLocation you have check old location and new location difference
but when update start you have to wait for some time then you have to check

[S.LakshmiKanth Reddy]

Originally Posted by greenflame

Depends on where you are calling startUpdatingLocation.

Also make sure you have implemented...

- (void)locationManagerCLLocationManager *)manager didUpdateToLocationCLLocation *)newLocation fromLocationCLLocation *)oldLocation

This method recognises when the current location has changed. Use this method to detect whether the current location is getting updated.

yes, i have implemented the CLLocationManagerDelegate and implemented this method even then i am not getting the updated location, i am getting the location only when i have launched the application later if i try to update then i am getting the old location only.

This is my problem, if u can help anyway it is greatly appreciable.

[Joseph Nardone]

Hi:
Did anyone find the answer to whether or not stopUpdatingLocation works as its name implies. I call it but then I still get updated locations!!

Has everyone just been programming around it?

I keep recalling startUpdatingLocation until my horizontal accuracy reaches the desired level and then i call stopUpdatingLocation and proceed. With the phone stationary I get 2 extra updates.

[site_reg]

I was having the same problem, and it seems to be fixed by declaring a static BOOL in your .m file and checking it when you enter the didUpdateToLocation method.

@implementation MyFile
@synthesize MySynth;
static BOOL haveAlreadyReceivedCoordinates = NO;

Then in your didUpdateToLocation method:

- (void)locationManager:(CLLocationManager *)manager didUpdateToLocation:(CLLocation *)newLocation fromLocation:(CLLocation *)oldLocation {
if(haveAlreadyReceivedCoordinates) {
	return;
	}
haveAlreadyReceivedCoordinates = YES;
...
}

This won't technically make it stop receiving updates, but it will ignore any updates after the first one. If your app depends on getting just one location update to do its work, this should help. :-)

[RayKrueger]

I ran into the same issue just this morning.
I resorted to setting and unsetting the delegate as needed.

self.locationManager.delegate = self;
[self.locationManager startUpdatingLocation];

And then when I stop it...
self.locationManager.delegate = nil;
[self.locationManager stopUpdatingLocation];

In my scenario it isn't that stopUpdatingLocation doesn't work, it's that all instances of CLLocationManager get updated by every instance of CLLocationManager. In my case, the one I created was getting called by the one created in the MapView. Nasty.

[jsd]

stopUpdatingLocation does indeed make it stop, but you will get two calls to didUpdateToLocation even if you say stop the first time it is called. Not sure if this is a bug or a feature.

[bleasdell]

Originally Posted by site_reg

I was having the same problem, and it seems to be fixed by declaring a static BOOL in your .m file and checking it when you enter the didUpdateToLocation method.

@implementation MyFile
@synthesize MySynth;
static BOOL haveAlreadyReceivedCoordinates = NO;

Then in your didUpdateToLocation method:

- (void)locationManager:(CLLocationManager *)manager didUpdateToLocation:(CLLocation *)newLocation fromLocation:(CLLocation *)oldLocation {
if(haveAlreadyReceivedCoordinates) {
	return;
	}
haveAlreadyReceivedCoordinates = YES;
...
}

This won't technically make it stop receiving updates, but it will ignore any updates after the first one. If your app depends on getting just one location update to do its work, this should help. :-)

Thanks Site_reg. Your suggestion worked for me.

[sebastien]

Hi, I am trying to get stopUpdatingLocation working for an iphone application but it is not working. I declared a static BOOL in my .m file but it is still updating, I dont know why. I dont know what I am doing wrong.

[Danny]

Hi friends,

I've query regarding the app store release. our client previously use other app store account for release his app on app store. Now we develop next version of same app for same client. we want upload updated version of app using our apple account. My question is if older version of app deactive from older apple account & upload updated new version same app using our account.Will the older user thoughs already have old version of app gets notification?

Thanks,
Dan

[Duncan C]

Originally Posted by Danny

Hi friends,

I've query regarding the app store release. our client previously use other app store account for release his app on app store. Now we develop next version of same app for same client. we want upload updated version of app using our apple account. My question is if older version of app deactive from older apple account & upload updated new version same app using our account.Will the older user thoughs already have old version of app gets notification?

Thanks,
Dan

Open a new thread for this. It certainly does not belong in a thread about location manager. It doesn't even belong in a development forum, since it's an app store procedural question. It belongs in the Business/legal/app store forum:

http://www.iphonedevsdk.com/forum/bu...gal-app-store/