Location access - App is not asking for user permission to access location - iOS 11

user_3024579 0
Viewed 10431

Description

App is not asking for user permission to access location and getting state notDetermined

Working perfectly till iOS-10

var locationManager : CLLocationManager!

func getLocationDetails()
    {
        locationManager.delegate = self
        locationManager.desiredAccuracy = kCLLocationAccuracyBest
        locationManager.requestAlwaysAuthorization()
        locationManager.allowsBackgroundLocationUpdates = true
        locationManager.startUpdatingLocation()

    }

func locationManager(_ manager: CLLocationManager, didChangeAuthorization status: CLAuthorizationStatus)
    {
        if status == CLAuthorizationStatus.authorizedAlways || status == CLAuthorizationStatus.authorizedWhenInUse
        {
            locationManager.startUpdatingLocation()
        }
    }

    func locationManager(_ manager: CLLocationManager, didUpdateLocations locations: [CLLocation])
    {


    }

Plist screenshot enter image description here

Background Modes

enter image description here

ios11 xcode9 core-location location ios
4 Answers

I have gone through the Apple documentation and found the solution for this question.

Apple has changed few guidelines to get user location.

Here is the Video Link: Apple- What's New in Location Technologies

Full code for location access in Swift & Objective-C both

Solution:

Now we need to add three Authentication Key into Plist:

  1. NSLocationAlwaysAndWhenInUseUsageDescription
  2. NSLocationWhenInUseUsageDescription
  3. NSLocationAlwaysUsageDescription

Plist will look like : enter image description here And Authentication message screen will look like:

enter image description here

Full code for location access

user_30245790

Please ask for the other permission also "When ever in use permission" and add both permission on the plist.

user_68740720

Please change requestAlwaysAuthorization to whenInUseAuthentication. Then it will start working. I think this might be due to GM Seed/Beta version of xcode. In stable version we might not have this issue.

user_1161580
Related