NSLocation required strings

Solar2D iOS
#1

It appears that the Corona docs on this topic are out-of-date in three out of four places (latest daily build docs). Build.settings (and from there, info.plist) must contain strings for “NSLocationWhenInUseUsageDescription” _ and also _ “NSLocationAlwaysUsageDescription”. 

There are at least two other NSLocation strings that may be required:
NSLocationAlwaysAndWhenInUseUsageDescription,

NSLocationUsageDescription.

There’s some redundancy here, and the Apple documentation didn’t make much sense to me. Has anyone tried submitting apps with limited subsets of these? Which ones are actually required?

#2

The two we have documented are the two currently needed by iOS 12 and earlier. iOS 13 is adding some new conditions, like asking for permission each time the app is in use will likely add a new key that will need to be included.

Rob

#3

Just for reference, in the main documentation on location events (api/event/location/), the Android permission settings are present but there’s no mention of the iOS NSLocation settings at all. In _ three _ other pages in the documentation, requestLocation.html, nearestAddress.html, getUserLocation.html, just one of the two settings, NSLocationWhenInUseUsageDescription, is mentioned as a required string. And in only _ one _ page in the documentation, newMapView.html, the two NSLocation settings which are currently required are listed:

plist =

        {

            NSLocationAlwaysUsageDescription = “This app would like to use location services.”,

            NSLocationWhenInUseUsageDescription = “This app would like to use location services.”,

        },

#4

If you do a File->New Project, we should be inserting default strings for you.

#5

Default strings like that in build.settings for location services (and other required strings for iOS/iPadOS) would certainly be nice, but I’m not seeing that behavior from File/New Project. That produces a minimal list of properties. Is there some more complete up-to-date template that’s maintained somewhere? Thanks.

#6

The two we have documented are the two currently needed by iOS 12 and earlier. iOS 13 is adding some new conditions, like asking for permission each time the app is in use will likely add a new key that will need to be included.

Rob

#7

Just for reference, in the main documentation on location events (api/event/location/), the Android permission settings are present but there’s no mention of the iOS NSLocation settings at all. In _ three _ other pages in the documentation, requestLocation.html, nearestAddress.html, getUserLocation.html, just one of the two settings, NSLocationWhenInUseUsageDescription, is mentioned as a required string. And in only _ one _ page in the documentation, newMapView.html, the two NSLocation settings which are currently required are listed:

plist =

        {

            NSLocationAlwaysUsageDescription = “This app would like to use location services.”,

            NSLocationWhenInUseUsageDescription = “This app would like to use location services.”,

        },

#8

If you do a File->New Project, we should be inserting default strings for you.

#9

Default strings like that in build.settings for location services (and other required strings for iOS/iPadOS) would certainly be nice, but I’m not seeing that behavior from File/New Project. That produces a minimal list of properties. Is there some more complete up-to-date template that’s maintained somewhere? Thanks.