NSLocationWhenInUseUsageDescription warning, but I have already added it

Question

While I have already added:

NSLocationWhenInUseUsageDescription

I keep receiving this warning:

This app has attempte

Answer 1

Adding both

NSLocationAlwaysAndWhenInUseUsageDescription

and

NSLocationWhenInUseUsageDescription

keys in plist solved my problem.

    <key>NSLocationAlwaysUsageDescription</key>
    <string>Your location is required for xyz benefits for you</string>
    <key>NSLocationWhenInUseUsageDescription</key>
    <string>Your location is required for xyz benefits for you</string>

Answer 2

There are a ton of poorly structured frameworks (namely FirebaseMessaging) that use camera and location for no benefit to the user. You should alert end user this functionality is NOT needed for your application and user must NOT grant app access to that parasite inside. What a sad, sad times we live in.

    <key>NSLocationAlwaysUsageDescription</key>
    <string>Your location is not needed. This request has popped up due to a 3rd party framework used by the app in a context that does NOT need you to reveal you location</string>
    <key>NSLocationWhenInUseUsageDescription</key>
    <string>You will get zero benefit allowing this app accessing your location. You should never see this alert. If you do alert technical support at foo@bar.baz</string>

Answer 3

Well, actually, in my case I needed to put ALL THREE of them like this:

<key>NSLocationAlwaysAndWhenInUseUsageDescription</key>
<string>...</string>
<key>NSLocationAlwaysUsageDescription</key>
<string>...</string>
<key>NSLocationWhenInUseUsageDescription</key>
<string>...</string>

Otherwise, I wouldn't get the pop-up alert asking to allow the Location.

Note: I develop in Flutter, I don't know if it has any repercussions in this case...

Answer 4

remove the NSLocationWhenInUseUsageDescription from plist and run the application and add again and run the application again

Answer 5

I was requesting authorisation in

viewDidLoad

as follows:

self.locationManager.requestWhenInUseAuthorization()

when I removed this line the error disappeared.