Parse-sdk-ios-osx: Apple requires "NSLocationAlwaysUsageDescription" description to info.plist

[AndreasStokidis]

I use parse for Push Notifications purpose. When I uploaded the binary to itunes conenct with Parse SDK installed apple sends me an automated message like bellow. This issue have been a month from now. When i removed the SDK from pod i don' t delivered this message.

Also I have the same issue with more than one project.

Has anyone else the same issue? What text can i add to info.plist to make apple approve my project.

" Dear Developer,

We identified one or more issues with a recent delivery for your 
app XXXXX. Your delivery was successful, but you 
may wish to correct the following issues in your next delivery:

"Missing Purpose String in Info.plist File. 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. Starting spring 2019, all apps submitted to the App Store 
that access user data will be required to include a purpose 
string.If you're using external libraries or SDKs, they may 
reference APIs that require a purpose string. While your app might 
not use these APIs, a purpose string is still required. You can 
contact the developer of the library or SDK and request they 
release a version of their code that doesn't contain the APIs. 


 After you’ve corrected the issues, you can use Xcode or 
 Application Loader to upload a new binary to iTunes Connect.

 Best regards,

 The App Store Team"

[flovilmart]

Not an issue with the SDK, please ask on stackoverflow

[mman]

Just for the record if anybody gets here via google, this issue is caused by new AppStoreConnect sanity checks when your app accidentally links agains CoreLocation.framework. Not related to the Parse SDK at all but seems to be happening since summer time 2018 when uploading new builds to the App Store. So just remove CoreLocation.framework from linked libraries and the error is gone.

[AndreasStokidis]

Removing CoreLocation.framework is not enough, because there are CCLocation objects in Parse SDK, which can be built without the framework!!!!!

In addition to, I deleted PFLocationManager.h and PFLocationManager.m files and I commented CCLocation objects from PFGeoPoint.h/m, FPolygon.h/m and Parse.h and I uploaded the binary wihout warning from Apple System.

Thank you

[flovilmart]

Well you could have simply entered a text into the NSLocationAlwaysUsageDescription. The users would never have seen it...

[henrik]

See https://github.com/parse-community/Parse-SDK-iOS-OSX/issues/1398 for ideas on a bigger-picture solution to this.