cllocationmanager

I have a question about CLLocationManagerDelegate . The documentation says if the user changes the settings for your location services (in the iPhone's Settings.app) then your app is supposed to receive an didChangeAuthorizationStatus: message to the delegate. My question is, when would this happen? If the user changed the setting, it means they are in the settings app, and your app is either backgrounded or not running at all, so in the former case, when would your app's CLLocationManager delegate get the didChangeAuthorizationStatus: call? I just ran across this method an hour ago, so good

I have been unable to work out how to handle a scenario where the phone is already inside a region when startMonitoringForRegion is called? Other questions have suggested calling requestStateForRegion inside didStartMonitoringForRegion this then calls the method didDetermineState: forRegion: . So the code looks something like this: - (void)viewDidLoad { //location manager set up etc... for (Object *object in allObjects){ CLRegion *region = [self geofenceRegion:object]; [locationManager startMonitoringForRegion:region]; } } - (void)locationManager:(CLLocationManager *)manager

I wonder if I could test Significant-Change location service (startMonitoringSignificantLocationChanges method ) in Xcode Simulator or it just only works in actual device. Notice, I already tried it in Simulator and it didn't work, but I'm not sure if this only because it don't work on simulator or because I did something wrong. Thanks I've answered this question before on SO, and using the simulator is not an accurate way to test for -startMonitoringSignificantLocationChanges. This method relies primarily on cell-tower triangulation and hand offs. You can occasionally get an initial fix from

I submitted an app which tracks the user's location (and sends it to the server) at some fixed intervals chosen by the user (5 min, 10 min, 30 min, 1 h). The app should work in background, too (sending the requests) and I have declared it as UIBackgroundMode = location . I am able to send the requests while in background at those fixed intervals. Apple rejected it, suggesting the following: We found that your app uses a background mode but does not include functionality that requires that mode to run persistently. This behavior is not in compliance with the App Store Review Guidelines. We

Since the depreciation of initCircularRegionWithCenter:radius:identifier: , how would you define the region to be monitored using CLLocationManager ? Since CLCircularRegion is a subclass of CLRegion , you can just cast the instance. CLCircularRegion *region = [[CLCircularRegion alloc] initWithCenter:theCenter radius:theRadius identifier:theIdentifier]; // Then cast the instance for use with your CLLocationManager instance [manager startMonitoringForRegion:(CLRegion *)region]; 来源： https://stackoverflow.com/questions/19205210/how-do-you-use-clregion-in-ios-7-since

What happens if I call startUpdatingLocation while startMonitoringSignificantLocationChanges is running? Does significantLocationChange monitoring get stopped? If I then stopUpdatingLocation will significantLocationChange monitoring continue or restart? I can find no documentation covering the interplay between these two ways of monitoring location. They are not meant to be used concurrently. It's either or as they both deliver heading and location changes to the same delegate method. locationManager:didUpdateToLocation:fromLocation They differ in the frequency and accuracy (and by extension

I just can get my CLLocationManager to authorise. (swift under ios8) I even add an explicit requestAlwaysAuthorization call (which I don't need with objC under ios7) func finishLaunch() { //ask for authorization let status = CLLocationManager.authorizationStatus() if(status == CLAuthorizationStatus.NotDetermined) { self.locationManager.requestAlwaysAuthorization(); } else { self.startMonitoring() } ... } the callback never gets anything but NotDermined and there is no UIAlertView shown to the user. func locationManager(manager: CLLocationManager!, didChangeAuthorizationStatus status:

I am having issue regarding significant-change location service. Apple documentation says "Whether you use the standard location service or the significant-change location service to get location events, the way you receive those events is the same." but in case of "significant-change location service" I am not able to get any callbacks which I get in case of "standard location service" Please let me know if anybody has any inputs? startUpdatingLocation updates the location when it is called first time and then when the distance filter value exceeds. But the