core-location

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'm trying to solve two problems with MKUserTrackingModeFollowWithHeading in iOS 6: MKUserTrackingModeFollowWithHeading works briefly, but it's jittery and returns to MKUserTrackingModeFollow almost immediately, especially at high zoom levels. The app occasionally crashes when repeatedly changing the MKUserTrackingMode : I get EXC_BAD_ACCESS on the main thread, without further information. This is hard to reproduce, but it has happened repeatedly. Any thoughts on what might be causing this? It feels like a bug, but Apple's own "Maps" app doesn't exhibit this behavior. In order to isolate the

I make a location app. But Core Location does not work. I tested other iPhone application on my iPhone. Like google earth, a navigation software. The other applications do not work also. Why doesn't update location? Why 'locationManager:didUpdateToLocation:fromLocation:' message called 2 times only? Maybe... My iPhone broken down? or iOS 6 CoreLocation frameworks have some bug? Location service - On on iPhone settings Info.plist armv7 accelerometer location-services gps microphone magnetometer Code Example: - (CLLocationManager *)setupLocationManager { if ([CLLocationManager

Is it possible to make the phone to "know" that a specific wifi network is at specific geographic location? if (answer == YES) { than how? } else { can the phone figure this out by himself? } Another similar question: is there any way to start monitor a region with accuracy of ~100m but telling the CLLocationManager to use only by wifi networks and cellular antenas? Because I don't want to power up the GPS no matter what... Thanks! iPhone positioning sucks and there is nothing you can do. If you jailbreak your device you can use the Apple80211 private framework to look up the available Wi-Fi

I'm building an app which displays result data based on your current location. At the moment, I'm using the viewDidLoad method of a UIViewController to start the CLLocationManager and getting the current location. Once I have the location that matches the accuracy I desire, I do a request to my web service to get the results and dump it into a UITableView . My problem is that when you close the app (although it's still running in the background). If you were to drive to another town, re-open the app, the data doesn't get updated and continues to show the results from your old location.

This is my code, showing both the alert and the blue dot for the current position on the map: MapName.h #import <UIKit/UIKit.h> #import <MapKit/MapKit.h> #import <CoreLocation/CoreLocation.h> @interface MapName : UIViewController <MKMapViewDelegate, CLLocationManagerDelegate> @property (strong, nonatomic) IBOutlet MKMapView *MapName; @property (strong, nonatomic) CLLocationManager *locationManager; @end MapName.m - (void)viewDidLoad { [super viewDidLoad]; self.locationManager = [[CLLocationManager alloc]init]; self.locationManager.delegate = self; if ([self.locationManager respondsToSelector:

When testing with a simple app to test beacon region monitoring I seem to get very inconsistent results depending on the device (not the device model, the specific device). The problem is that I don't receive the CLRegionStateInside state on the region after requestStateForRegion and didEnterRegion does not get called at all on these device. startRangingBeaconsinRegion : works fine but to conserve power and processing it is recommended to only start ranging when the didEnterRegion : method gets called. I tested this on 6 devices and it works on half on them (iPhone 5's) and does't work on one