Apps use location data for many purposes, ranging from social networking to turn-by-turn navigation services.They get location data through the classes of the Core Location framework.This framework provides several services that you can use to get and monitor the device’s current location:The significant-change location service provides a way to get the current location and be notified when significant changes occur, but it’s critical to use it correctly to avoid using too much power.To learn how to give users a great location-aware experience while conserving power, see Reduce Location Accuracy and Duration.To use the features of the Core Location framework, you must link your app to in your Xcode project.To access the classes and headers of the framework, include an statement at the top of any relevant source files.For general information about the classes of the Core Location framework, see Core Location Framework Reference.The value for the UIRequiredDeviceCapabilities is an array of strings indicating the features that your app requires.

Two strings are relevant to location services: If your iOS app requires location services to function properly, include the UIRequiredDeviceCapabilities key in the app’s Info.plist file.ios store websiteThe App Store uses the information in this key to prevent users from downloading apps to devices that don’t contain the listed features.The Core Location framework lets you locate the current position of the device and use that information in your app.ios store nsarray in nsuserdefaultsThe framework reports the device’s location to your code and, depending on how you configure the service, also provides periodic updates as it receives new or improved data.ios price in philippines

Two services can give you the user’s current location:The standard location service is a configurable, general-purpose solution for getting location data and tracking location changes for the specified level of accuracy.vape stores 75287The significant-change location service delivers updates only when there has been a significant change in the device’s location, such as 500 meters or more.Gathering location data is a power-intensive operation.puff nuggs v3 vaporizer reviewFor most apps, it’s usually sufficient to establish an initial position fix and then acquire updates only periodically after that.pax vaporizer review redditRegardless of the importance of location data in your app, you should choose the appropriate location service and use it wisely to avoid draining a device’s battery.ios injustice online

For example:If your iOS app must keep monitoring location even while it’s in the background, use the standard location service and specify the location value of the UIBackgroundModes key to continue running in the background and receiving location updates.vapor store in pasadena tx(In this situation, you should also make sure the location manager’s pausesLocationUpdatesAutomatically property is set to YES to help conserve power.)ios online djExamples of apps that might need this type of location updating are fitness or turn-by-turn navigation apps.If GPS-level accuracy isn’t critical for your app and you don’t need continuous tracking, you can use the significant-change location service.It’s crucial that you use the significant-change location service correctly, because it wakes the system and your app at least every 15 minutes, even if no location changes have occurred, and it runs continuously until you stop it.

Determining Whether Location Services Are AvailableThere are situations where location services may not be available.For example:The user disables location services in the Settings app or System Preferences.The user denies location services for a specific app.The device is in Airplane mode and unable to power up the necessary hardware.For these reasons, it’s recommended that you always call the locationServicesEnabled class method of CLLocationManager before attempting to start either the standard or significant-change location services.If it returns NO and you attempt to start location services anyway, the system prompts the user to confirm whether location services should be re-enabled.Because the user probably disabled location services on purpose, the prompt is likely to be unwelcome.Starting the Standard Location ServiceThe standard location service is the most common way to get a user’s current location because it’s available on all devices and in both iOS and OS X. Before using this service, you configure it by specifying the desired accuracy of the location data and the distance that must be traveled before reporting a new location.

When you start the service, it uses the specified parameters to determine the hardware to enable and then proceeds to report location events to your app.Because this service takes into account these parameters, it’s most appropriate for apps that need more fine-grained control over the delivery of location events.The precision of the standard location service is needed by navigation apps or any app that requires high-precision location data or a regular stream of updates.Because this service typically requires the location-tracking hardware to be enabled for longer periods of time, higher power usage can result.To use the standard location service, create an instance of the CLLocationManager class and configure its desiredAccuracy and distanceFilter properties.To begin receiving location notifications, assign a delegate to the object and call the startUpdatingLocation method.As location data becomes available, the location manager notifies its assigned delegate object.If a location update has already been delivered, you can also get the most recent location data directly from the CLLocationManager object without waiting for a new event to be delivered.

To stop the delivery of location updates, call the stopUpdatingLocation method of the location manager object.Listing 1-1 shows a sample method that configures a location manager for use.The sample method is part of a class that caches its location manager object in a member variable for later use.(The class also conforms to the CLLocationManagerDelegate protocol and so acts as the delegate for the location manager.)Because the app doesn’t need precise location data, it configures the location service to report the user’s general area and send notifications only when the user moves at least half a kilometer.Listing 1-1  Starting the standard location serviceThe code for receiving location updates from this service is shown in Receiving Location Data from a Service.Starting the Significant-Change Location ServiceTo use the significant-change location service, create an instance of the CLLocationManager class, assign a delegate to it, and call the startMonitoringSignificantLocationChanges method as shown in Listing 1-2.

Listing 1-2  Starting the significant-change location serviceAs with the standard location service, location data is delivered to the delegate object as described in Receiving Location Data from a Service.To stop the significant change location service, call the stopMonitoringSignificantLocationChanges method.If you leave the significant-change location service running and your iOS app is subsequently suspended or terminated, the service automatically wakes up your app when new location data arrives.At wake-up time, the app is put into the background and you are given a small amount of time (around 10 seconds) to manually restart location services and process the location data.(You must manually restart location services in the background before any pending location updates can be delivered, as described in Knowing When to Start Location Services.)Because your app is in the background, it must do minimal work and avoid any tasks (such as querying the network) that might prevent it from returning before the allocated time expires.

If it does not, your app will be terminated.If an iOS app needs more time to process the location data, it can request more background execution time using the beginBackgroundTaskWithName:expirationHandler: method of the UIApplication class.Receiving Location Data from a ServiceThe way you receive location events is the same whether you use the standard or the significant-change location service to get them.Beginning in OS X v10.9 and iOS 6, the location manager reports events to the locationManager:didUpdateLocations: method of its delegate when they become available.(In earlier versions of both operating systems, the location manager reports events to the locationManager:didUpdateToLocation:fromLocation: method.)If there is an error retrieving an event, the location manager calls the locationManager:didFailWithError: method of its delegate instead.Listing 1-3 shows the delegate method for receiving location events.Because the location manager object sometimes returns cached events, it’s recommended that you check the timestamp of any location events you receive.

(It can take several seconds to obtain a rough location fix, so the old data simply serves as a way to reflect the last known location.)In this example, the method throws away any events that are more than fifteen seconds old under the assumption that events up to that age are likely to be good enough.If you are implementing a navigation app, you might want to lower the threshold.Listing 1-3  Processing an incoming location eventIn addition to a location object’s timestamp, you can also use the accuracy reported by that object to determine whether you want to accept an event.As it receives more accurate data, the location service may return additional events, with the accuracy values reflecting the improvements accordingly.Throwing away less accurate events means your app wastes less time on events that can’t be used effectively anyway.Knowing When to Start Location ServicesApps that use location services should not start those services until they’re needed.With a few exceptions, avoid starting location services immediately at launch time or before such services might reasonably be used.

Otherwise you might raise questions in the user’s head about how your app uses location data.The user knows when your app starts location services, because the system prompts the user for permission as soon as your app starts the service.Waiting until the user performs a task that actually requires those services helps build trust that your app is using them appropriately.To build trust between the user and an app, an app that uses Core Location must include the NSLocationAlwaysUsageDescription or NSLocationWhenInUseUsageDescription key in its Info.plist file and set the value of that key to a string that describes how the app intends to use location data.If you call the requestWhenInUseAuthorization method without including one of these keys, the system ignores your request.If you are monitoring regions or using the significant-change location service in your app, there are situations where you must start location services at launch time.Apps using those services can be terminated and subsequently relaunched when new location events arrive.