startMonitoringSignificantLocationChanges but after some time didUpdateLocations is not called anymore

2
votes

I have a very strange behaviour. I'm writing an application that uses both fetch and location background mode (don't know it it's important for the problem). I correctly set up the CLLocationManager with a delegate and I start monitoring significant location changes (startMonitoringSignificantLocationChanges) in the AppDelegate. Immediately I get called didUpdateLocations that gives me some locations. After that no more events are fired even I simulate a different location in Xcode (also using a GPX file) and even I stop and restart the monitoring. I'm not receiving any location both in background and foreground.

The strange thing is that if I start updating locations (using the GPS) it works correctly (doing the same tests... starting and stopping exactly like with startMonitoringSignificantLocationChanges). Obviously I've both didUpdateLocations and didFailWithError (I receive no errors).

This is my initialisation (called by the initialisation of an object in my AppDelegate didFinishLaunchWithOptions):

self.locationManager = [[CLLocationManager alloc] init];
self.locationManager.delegate = self;
self.locationManager.pausesLocationUpdatesAutomatically = NO;

I know that distanceFilter and accuracy are not important for significant location changes and I've already set pausesLocationUpdatesAutomatically to NO.

Am I missing something? And also does exist a way to read if a location fired is coming from wifi, cellular or gps?

Thanks in advance.

2
iphoneiosobjective-ccore-location
You know that startMonitoringSignificantLocationChanges doesn't use the GPS, uses the cellphone antennas to check if you have moved a significative distance. So maybe this won't work in the simulator. – JP Illanes

2 Answers

2
votes

You can simulate location for significant change on simulator only with "freeway drive" option from simulator location menu. It will be triggered with some minutes interval.

0
votes

Allocate the manager on the main thread and check if the manager or the app has always permissions could do the trick. Apple's documentation note is:

Note: Significant-change location updates require an authorization status of kCLAuthorizationStatusAuthorizedAlways.

You can check the status using: 

CLAuthorizationStatus status = [CLLocationManager authorizationStatus];

And maybe 

if (status != kCLAuthorizationStatusAuthorizedAlways)

You can request permissions again.