You’re probably being ARC’d. Make sure that you still have a reference to your CLLocationManager. You can easily do this by making it a property. ARC stands for Automatic Reference Counting. In an ARC-enabled project (and unless you are working on something really old or you turned it off on purpose, your project is an … Read more
RunKeeper actually does use the audio trick to stay awake. If you open up the app package and check their Info.plist you will see that it registers for the background audio mode. This is how they pull off periodic audio notifications of your distance, speed, and pace. It is also how they stay awake during … Read more
All the advice about the wisdom (or lack thereof) in guessing about motion states from location data still applies. But regarding your update about Core Motion and M7… Yes, you can use Core Motion on devices with an M7, M8, M9, etc motion coprocessor(*) to get an indication of whether the user might be driving. … Read more
It is now a property of CLLocationManager, authorizationStatus. So, create a CLLocationManager instance: let manager = CLLocationManager() Then you can access the property from there: switch manager.authorizationStatus { case .restricted, .denied: … default: … } There are a few location related changes in iOS 14. See WWDC 2020 What’s new in location. Needless to say, … Read more
I’m seeing this issue also. It only happens if you implement the renderFor overlay for MKMapView. And without this function, I can’t display the polyline that I’m adding to the mapView. This was working fine in Xcode 10.
You could create a StateObject of your LocationManager by implementing the ObservableObject protocol. With the @Published attribute you can create a publisher object which notify the observers (your view, in this case) when something changes inside that object. That’s why in my LocationManager I added the @Published attribute to those var: locationStatus: CLAuthorizationStatus? it contains … Read more
The easiest technique is to just shift the map down, say 40% from where the coordinate would be, taking advantage of the span of the region of the MKMapView. If you don’t need actual pixels, but just need it to move down so that the CLLocationCoordinate2D in question is near the top of the map … Read more
At the end of the day, Apple’s suggestion of removing location from UIBackgroundModes fixed our battery drain issue. In order to still get locations in the background we had to wrap the [locationManager startLocationUpdates] & [locationManager stopLocationUpdates] calls with: [[UIApplication sharedApplication] beginBackgroundTaskWithExpirationHandler]; [[UIApplication sharedApplication] endBackgroundTask:];
I believe the reason is the following: Apple’s geocoder does not answer every request in the same way. Instead, the first requests from a certain device are answered quickly, but if the device has sent say 100 requests or more, the answers arrive slower and slower or requests are not answered at all, which might … Read more
Here the code modified with the changes suggested by Oren Trutner and from myself: #define degreesToRadians(x) (M_PI * x / 180.0) #define radiansToDegrees(x) (x * 180.0 / M_PI) – (float)getHeadingForDirectionFromCoordinate:(CLLocationCoordinate2D)fromLoc toCoordinate:(CLLocationCoordinate2D)toLoc { float fLat = degreesToRadians(fromLoc.latitude); float fLng = degreesToRadians(fromLoc.longitude); float tLat = degreesToRadians(toLoc.latitude); float tLng = degreesToRadians(toLoc.longitude); float degree = radiansToDegrees(atan2(sin(tLng-fLng)*cos(tLat), cos(fLat)*sin(tLat)-sin(fLat)*cos(tLat)*cos(tLng-fLng))); if (degree … Read more