NSLocationAlwaysUsageDescription problem

Solar2D General Questions/Discussion
#1

ITMS-90738: Invalid value for purpose string  - The value ‘NSLocationAlwaysUsageDescription should be set to a valid usage description’ for Info.plist NSLocationAlwaysUsageDescription is not allowed. Your app’s code references one or more APIs that access sensitive user data. The app’s Info.plist file should contain a NSLocationAlwaysUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data.

I’ve got this message, after trying to upload a new building to apple store.

I didn’t change anything on my build.settings

iphone = { xcassets = "Images.xcassets", plist = { LSApplicationQueriesSchemes = { "comgooglemaps" }, UIBackgroundModes = {"remote-notification"}, NSAppTransportSecurity = { NSAllowsArbitraryLoads = true, }, --NSLocationAlwaysUsageDescription = "Necessita de dar permissão de acesso ao mapa para mostrar a localização do produtor.", --NSLocationWhenInUseUsageDescription = "Necessita de dar permissão de acesso ao mapa para mostrar a localização do produtor.", UIStatusBarHidden = false, UILaunchStoryboardName = "LaunchScreen", }, }

Why I need to enable “NSLocationAlwaysUsageDescription”?

it’s onesignal plugin problem?

plugins = { ["plugin.utf8"] = { publisherId = "com.coronalabs" }, ["plugin.OneSignal"] = { publisherId = "com.onesignal", } },
#2

Hi, I have the same problem with the OneSignal plugin.

Apparently (in other onesignal sdk) this command should be given:

OneSignal.setLocationShared (false)

But in Corona’s documentation it says:

–Currently not available

Regards,

solca

:frowning:

#3

OneSignal Response:

"Sorry, this is not available in the Corona SDK and we are not planning to add this unfortunately.*

Please let us know if you have any additional questions."

Regards,

Solca

#4

Hi @Solca, can you be more specific about your problem? Are you saying that you want to collect the users location through the OneSignal plugin, but they don’t support it?

#5

@troylyndon Thanks for your interest.

No sir. It’s the opposite. These are the details:

  1. We have sent an application to the app Store, but it has been rejected because geo-referenced information is accessed without explicitly requesting permissions.
  2. The application does not request these permissions because it does not need them.
  3. We suspect (99% sure) that it is the onesignal plugin that is requesting georeferenced data.
  4. The documentation of onesignal “apparently” allows to disable requesting georeferenced data, but in CoronaSDK it is not supported (in other sdk, YES this can be disabled), according to an official answer.

I think the only alternative is to not use Onesignal in this and other projects.

Regards,

@solca