180 Seconds Limit

[yreaction]

Hi:

First of all, thanks for this contribution.

I've been looking as you to reach a proper solution of unlimited update location every X time. Unfortunately I'm not able to do it even with your repository. I have set up everything, but still with this one and other solutions there is no way of break the 180 second limit.

[shanemileham]

I'm having the same issue while running on iOS9. The restartLocationUpdates: method is being called each minute, but backgroundTimeRemaining does not get reset. This leads to my app getting killed after 180 seconds as well.

@voyage11 - Do you know why this is happening or have a possible solution? I've been researching for hours and haven't found a solution that isn't ridiculously extravagant yet. Thanks for putting together this library!

[shanemileham]

Found it! Solution was posted in the comments here:
http://mobileoop.com/background-location-update-programming-for-ios-7#comment-433

To make it work on ios 9 change the singleton initializer in LocationTracker.m to

+ (CLLocationManager *)sharedLocationManager {
static CLLocationManager *_locationManager;

@synchronized(self) {
if (_locationManager == nil) {
_locationManager = [[CLLocationManager alloc] init];
if([_locationManager respondsToSelector:@selector(allowsBackgroundLocationUpdates)]){
[_locationManager setAllowsBackgroundLocationUpdates:YES];
}
_locationManager.desiredAccuracy = kCLLocationAccuracyBestForNavigation;
}
}
return _locationManager;
}

[yreaction]

Totally right. Thanks!

[sergii-frost]

Hi,
I've been successfully using current approach for iOS 7-8, updated app to iOS 9 with using [_locationManager setAllowsBackgroundLocationUpdates:YES]; but found an interesting case:

1. Start app for first time, make all configs with background tasks etc
2. Send app to background, check [UIApplication sharedApplication].backgroundTimeRemaining property --> it starts to count down from 180 to 0
3. Make app active
4. Send app to background, check [UIApplication sharedApplication].backgroundTimeRemaining property --> it is equal to CGFLOAT_MAX

Has anyone else faced this issue? It happens only on first app -> background.

[sergii-frost]

I've figured issue why I was getting issue described in previous comment, but it may be helpful to someone else:

I was calling [_locationManager setAllowsBackgroundLocationUpdates:YES]; in the handler of UIApplicationDidEnterBackgroundNotification notification, and it was too late actually. This method should be called whenever _locationManager is initialized.