Posts

Post not yet marked as solved
10 Replies
11k Views
In our latest two pushes to AppStore Connect, we've been getting the following message, where we hadn't previously: Dear Developer, We identified one or more issues with a recent delivery for your app, "XYZ" 1.2.3 (123). Your delivery was successful, but you may wish to correct the following issues in your next delivery:  ITMS-90683: Missing purpose string in Info.plist - Your app’s code references one or more APIs that access sensitive user data, or the app has one or more entitlements that permit such access. The Info.plist file for the “xyz.app” bundle should contain a NSLocationAlwaysAndWhenInUseUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. 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. Oddly though, we've not really made any changes to our codebase that should trigger this. Just wondering if others are seeing the same message? Has the algorithm to detect this changed recently and giving false positives? We've even uploaded a previous release (that didn't get this warning) to check if we get the warning again, and we are receiving the warning on an app upload that didn't get the warning previously. Would be good to know if any logic behind this trigger has changed, or is anyone else getting the same message when they are not expecting it? Searching our Codebase for CoreLocation reveals nothing, is there anything else that may trigger this popup and require this plist key?
Posted
by DaveLev.
Last updated
.