Error Appstore connect : Missing Purpose String in Info.plist File

Question

I've submitted my app for review to the App Store Connect. Although the app is still under review, I've received an email to inform me that I have to fix an error. Here is the content of the message:

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

My app is fully built with Expo and I don't know how to access and modify the Info.plist.

Any idea?

I'm having the same issue with the latest build, given that I don't even use Location Services in my app. And Apple has no official document about this change. — huong, Aug 24 '18 at 11:40
Same issue. I just did a tiny change and a new build and got this. I do have an `NSLocationWhenInUseUsageDescription` in the Info.plist that is blank but I have translation strings for it. — fphilipe, Aug 24 '18 at 15:13
+1 Did a release for the same app 2 days ago and everything is fine. 2 days later, just changed a couple of lines of code to do a new release (didn't add more Pods or something like that) and I got this message — Tiago Ornelas, Aug 24 '18 at 16:00
We've experienced the same issue. I suspect it's a bug in the approval process (hopefully). I'm going to ignore for the weekend and hope that it's fixed on Monday. — AMB, Aug 24 '18 at 16:48
I faced the same exact issue just now although our App doesn't really need Location Services Always. It just needs NSLocationWhenInUseUsageDescription which we already have a purpose string for. Probably this is just a glitch on Apple's end? — ilight, Aug 27 '18 at 08:06
And in Apple-fashion, the link they provide in the email to fix it, is broken. — gwalshington, Aug 27 '18 at 18:55
I also got the same issue. I installed `ionic diagnostic` plugin and got this `NSBluetoothAlwaysUsageDescription` in the Info.plist — Ragesh Pikalmunde, Oct 17 '19 at 06:55

AnthoPak · Answer 1 · 2019-07-16T15:12:20.960

EDIT April 2019 : You now have to add these two keys, as spring 2019 has begun. Note that NSLocationAlwaysUsageDescription is now deprecated (since iOS 11) and has been replaced with NSLocationAlwaysAndWhenInUseUsageDescription and NSLocationWhenInUseUsageDescription. If you want to support lower than iOS 11, you'll have to use the three values.

To sum up you have to:

Add NSLocationAlwaysAndWhenInUseUsageDescription AND NSLocationWhenInUseUsageDescription for iOS 11 and more
And add NSLocationAlwaysUsageDescription if you want to support iOS 10 and less
And finally, you can add NSLocationUsageDescription if you wan to support iOS 8 and less.

You can submit your app even if you got this message !

I’ve just faced the same issue yesterday, even if the app isn’t using the location functionality. It may be related to some framework included in the project that have this optional feature.

I can confirm that my app has been approved even without the NSLocationAlwaysUsageDescription and NSLocationWhenInUseUsageDescription key in info.plist

Indeed, as Apple stated in the mail :

Starting spring 2019, all apps submitted to the App Store that access user data will be required to include a purpose string.

So the only thing to do is to add this key (right now is better, so that you won’t forget) in you project so that it will be included in your next update.

Just add two new entries in your info.plist, with NSLocationAlwaysUsageDescription and NSLocationWhenInUseUsageDescription as keys and a short description of why you use them as the value (even if you don’t really use them...).

In your April 2019 edit, are you sure you don't have the deprecation reversed? From what I see NSLocationUsageDescription is the one that's deprecated. Looking here: https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CocoaKeys.html#//apple_ref/doc/uid/TP40009251-SW18 — apricity, May 17 '19 at 15:40
The email I received from apple mentions NSLocationAlwaysUsageDescription so i think he has it reversed. — Dror Bar, Jul 16 '19 at 09:41
@apricity @DrorBar Sorry guys, indeed I had made a mistake. It was not reversed but there was still a mistake, `NSLocationAlwaysUsageDescription` should be replaced by `NSLocationAlwaysAndWhenInUseUsageDescription` and `NSLocationWhenInUseUsageDescription `, and not by `NSLocationUsageDescription` (as I previously wrote, sorry…). I've updated my answer to add a sum up of the process. — AnthoPak, Jul 16 '19 at 15:25

score 62 · Accepted Answer · answered Aug 27 '18 at 19:24

62

If you're using Expo, you can add solve by adding infoPlist to app.json like so:

  "expo": {
     "ios": {
       "bundleIdentifier": "com.app.myapp",
       "infoPlist": {
         "NSLocationAlwaysUsageDescription": "Some message to appease Apple.",
       },
     },
   }

Expo Docs

answered Aug 27 '18 at 19:24

gwalshington

1,418
2
30
60

41

Actually it is **NOT** "some message to appease Apple" but to let the user know WHAT are you doing with the user's generated data (location) in this case. It is a matter of privacy concerns and I do think it is good to be fair to your apps users. – Lookaji Sep 18 '18 at 10:23
4

Gotcha! I was thinking to newbies that may be tempted to leave it so! I did not want to sound grumpy :) cheers! – Lookaji Sep 18 '18 at 21:58
@gwalshington I don't have any expo object in app.json – Heemanshu Bhalla Apr 18 '19 at 08:14
@HeemanshuBhalla hmm, i'm unsure why. In my app.json, it's at the top and the first object declared. It's where you declare the version number, bundle identifier, etc. If you have ejected the app, maybe it looks slightly different? – gwalshington Apr 18 '19 at 17:34
3

What text to type if we don't collect and Location data? We need to make up a lie :S – c0dehunter Apr 29 '19 at 11:42
@PrimožKralj Yes unfortunately - I don't collect location data, but it forced me to provide a message. – gwalshington May 10 '19 at 20:46
@Lookaji since Google is not asking for it, as a Flutter dev, I AM doing it just to please Apple. Hence I don't even know if the gets translated I'll have to figure this out – MwBakker Jun 26 '23 at 22:22

score 56 · Answer 3 · answered Aug 24 '18 at 21:40

56

I have some apps in the store and I tried to distribute a version for QA and the same thing happened in two different Apps. I think this is a new criteria to accept the builds uploads to Appstore connect.

The solution is simple, add the following lines in the .plist file.

<key>NSLocationAlwaysUsageDescription</key>  <string>custom message</string>  <key>NSLocationWhenInUseUsageDescription</key>  <string>custom message</string>

PS: In my case have not using any feature of location, but I added these lines in order to comply with Appstore connect guidelines. Btw after receive that email, I could test the app even when they said that build it had some issues.

I hope this work for you guys.

answered Aug 24 '18 at 21:40

vroldan

1,077
9
12

5

Wow, I just got this, realized everyone is just getting this too! – Cameron A. Ellis Aug 26 '18 at 05:31
first key has changed as of now to `NSLocationUsageDescription` – Hudi Ilfeld Mar 28 '19 at 08:01
1

Do we have to re-archive after updating the info.plist ? – Bishoy Hanna Apr 12 '19 at 16:37
1

Do I have to increase the bundle version or version number to upload a new binary? – Dror Bar Jul 16 '19 at 09:39
@BishoyHanna YES! Dror Bar YES! – Fotios Tsakiris Dec 29 '21 at 10:20

score 23 · Answer 4 · answered Aug 29 '18 at 00:04

23

It's a new requirement from apple, even if you do not use location. If you want to add the permissions in Xcode, look for "Privacy - Location Usage Description" and "Privacy - Location When In Use Usage Description" and type a custom string for each of them.

answered Aug 29 '18 at 00:04

Juan José Ramírez

639
6
10

1

In other app update, Apple requested this permission too: "Privacy - Location Always Usage Description" – Juan José Ramírez Aug 31 '18 at 22:34
2

So if I don't use these features, what I have to write there, a lie, something like "collect location for future use, maybe"? – Ruslan Shashkov Apr 24 '19 at 18:02
yes, apple will reach to you if they have questions – Juan José Ramírez Jul 10 '19 at 14:37
1

I am not able to find **Information Property List** in my xcode 10.1, you should have mentioned where to find it, I have looked for Build Settings both for Targets and Project – Muhammad Awais Sep 07 '19 at 06:41
2

Okay So Targets->Info->Custom ios Target Properties was the exact location – Muhammad Awais Sep 07 '19 at 06:59

Sachin Nautiyal · Answer 5 · 2019-03-28T09:44:27.613

21

For more simplifying you can add these lines in your info.plist. These error are coming because Starting spring 2019, all apps submitted to the App Store that access user data will be required to include a purpose string.

Open info.plist as source code.

Add these following lines in your plist

<key>NSLocationAlwaysAndWhenInUseUsageDescription</key>
<string>$(PRODUCT_NAME) needs Location access for "some reason"!</string>
<key>NSLocationWhenInUseUsageDescription</key>
<string>$(PRODUCT_NAME) needs Location access for "some reason"!</string>
<key>NSLocationAlwaysUsageDescription</key>
<string>$(PRODUCT_NAME) needs Location access for "some reason"!</string>

edited Mar 28 '19 at 09:44

answered Sep 04 '18 at 06:31

Sachin Nautiyal

568
4
15

3

I had to remove extra spaces in tags and then it worked. – innich Mar 28 '19 at 09:04
@innich thank you for pointing it out, I have changed my answer. – Sachin Nautiyal Mar 28 '19 at 09:44

score 9 · Answer 6 · answered Aug 27 '18 at 16:45

9

##Use this key in info.plist file

NSLocationAlwaysUsageDescription Your location is required for xyz benefits for you NSLocationWhenInUseUsageDescription Your location is required for xyz benefits for you

answered Aug 27 '18 at 16:45

Sumit Sharma

91
1

score 9 · Answer 7 · edited Mar 27 '21 at 22:04

"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.

Open Info.plist as source code.
Add these following lines in your plist

<key>NSLocationAlwaysAndWhenInUseUsageDescription</key>
<string>$(PRODUCT_NAME) needs Location access for "some reason"!</string>
<key>NSLocationWhenInUseUsageDescription</key>
<string>$(PRODUCT_NAME) needs Location access for "some reason"!</string>
<key>NSLocationAlwaysUsageDescription</key>
<string>$(PRODUCT_NAME) needs Location access for "some reason"!</string>

score 8 · Answer 8 · edited Mar 30 '19 at 08:08

8

We did receive the same email and we aren't using the CoreLocation at all. After a quick search, we found that Parse SDK could use CoreLocation. In Apple's email, they clearly say:

If you're using external libraries or SDKs, they may reference APIs that require a purpose string.

That mean the minute your code or any other Library or SDKs can use CoreLocation, even if you don't use it, you need to provide privacy description for "When In Use" and "Always Use".

It is also something new from Apple and for now it's only a warning but it will be required starting in Spring 2019 for new submissions.

edited Mar 30 '19 at 08:08

JJJ

32,902
20
89
102

answered Aug 24 '18 at 18:43

sebleclerc

321
3
5

It's just stupid.... If I'm not using it, it could make peoples dont downloading my app just because of that. -_- – Mayoul Sep 03 '18 at 12:18
4

Not really. The alert asking you to use your localization won't show unless somewhere in the code the `CLLocationManager.requestWhenInUseAuthorization()` is called. Apple analyzed each app code to see if such a function could be called. If it's never called, the alert won't show up. – sebleclerc Sep 04 '18 at 14:39

score 7 · Answer 9 · edited Oct 01 '19 at 14:46

There are the following cases:

NSLocationAlwaysAndWhenInUseUsageDescription (iOS>11)
NSLocationWhenInUseUsageDescription          (iOS>11)
NSLocationAlwaysUsageDescription             (iOS<=10)
NSLocationUsageDescription                   (seems very old, iOS8?)

Apple states at:

Add the NSLocationWhenInUseUsageDescription key and the NSLocationAlwaysAndWhenInUseUsageDescription key to your Info.plist file.

and:

If your app supports iOS 10 and earlier, add the NSLocationAlwaysUsage

NSLocationUsageDescription seems dead, the only ref in ADC site is: https://developer.apple.com/ibeacon/Getting-Started-with-iBeacon.pdf

So to be sure, use first 3.

Sachin Nautiyal · Answer 10 · 2018-08-27T05:57:04.567

6

This issue is occurring because you haven't included

 <NSLocationAlwaysUsageDescription>

for your app. I faced the same issue when I tried to submit my app on the AppStore. After the app was processed, I got the same mail. I just added the description and now its resolved.

Hope this helps.

edited Aug 27 '18 at 05:57

answered Aug 24 '18 at 18:47

Sachin Nautiyal

568
4
15

This helped me. If you are using Location in your app (or maybe just always) you need to add this line and a string below it. `NSLocationAlwaysUsageDescription Always And In Use Permission` – MaylorTaylor Oct 17 '19 at 22:27

score 4 · Answer 11 · answered Aug 27 '18 at 18:55

These answers all tell you how to comply with the App Store rules to avoid the warning but the true fix would be for Expo to allow you to disable their SDKs requirement for Location Services unless you actually use them - I'm not sure if this is possible.

dbrownjave · Answer 12 · 2019-06-27T17:53:55.987

4

Please review the email you received from **App Store Connect **

Identify The Missing Key

Instructions

Open info.plist file.
Add and search for the missing key from the options provided (e.g. Contacts = Privacy - Contacts Usage Description)
Add Usage Description:

$(PRODUCT_NAME) needs Contacts access to "Provide The Reason Here".

Example:

edited Jun 27 '19 at 17:53

answered Jun 27 '19 at 14:41

dbrownjave

437
1
8
19

1

sir i got same error but why add to info.plist actually i m not used contact feature in my app so why we need to add it? – Kapil Soni Feb 26 '20 at 08:02
@Kapilsoni Please ensure you are not accessing one or more APIs that has access to sensitive user data – dbrownjave Feb 26 '20 at 12:20
1

:sir I have used only camera and location in my app? – Kapil Soni Feb 26 '20 at 13:31

score 3 · Answer 13 · answered Feb 11 '19 at 01:16

3

same issue in Feb 19, got an email with a bunch of permissions I am not using, I assume they are from plugins. Apple says in March 19 it is a requirement so I am adding these in info.plst and uploading again.

It is very silly indeed.

answered Feb 11 '19 at 01:16

Panda Power

325
6
12

2

More of a comment really...? – Steve Feb 11 '19 at 02:14

score 3 · Answer 14 · answered Apr 19 '19 at 15:17

3

I had <key>NSLocationWhenInUseUsageDescription </key> instead of <key>NSLocationWhenInUseUsageDescription</key>

be sure to remove trailing whitespace

answered Apr 19 '19 at 15:17

Michael van de Waeter

1,473
15
29

score 3 · Answer 15 · answered May 09 '19 at 07:48

3

I also face the same issue but after 27 hours, I received the email about approved even I did nothing. So wait for approximately 24 hours instead of doing all this process again.

answered May 09 '19 at 07:48

Abdul Qayum

179
7

1

Yes, it’s a bug! – Danh Huynh Oct 08 '19 at 00:37

score 3 · Answer 16 · answered Oct 17 '19 at 20:04

With Xcode 11 copy the key NSLocationAlwaysUsageDescription and add this to Info -> Custom iOS Target Properties -> Click + in the bottom left of this tab and as a value insert some kind of description like This app requires location access to function properly..

score 1 · Answer 17 · answered Aug 28 '18 at 07:30

1

My app also got that， and I do nothing about it but it can run well ,next time I think should add such key in plist,just do some description

answered Aug 28 '18 at 07:30

liunianhuaguoyanxi

99
6

score 1 · Answer 18 · answered Nov 04 '19 at 11:06

1

A short answer to the above problem -

NSLocationAlwaysUsageDescription must be updated with the following description in Info.plist file

{Your App Name} requires access to the location to suggest dengue outbreak zones.

answered Nov 04 '19 at 11:06

Soman Dubey

3,798
4
22
32

score 1 · Answer 19 · answered Dec 30 '19 at 17:06

In our case, we were using NSLocationWhenInUseUsageDescription in our app, but not NSLocationAlwaysUsageDescription.

Reading from the comments here (thanks matt-oakes), it looks like NSLocationAlwaysUsageDescription is being used by one of the dependency frameworks we use.

Running our app it doesn't show the actual NSLocationAlwaysUsageDescription permission modal, so it looks to just handle this in the background.

So in summary, adding NSLocationAlwaysUsageDescription to the Info.plist fixed the warning email, and did not change any behaviour in the app

Error Appstore connect : Missing Purpose String in Info.plist File

19 Answers19

You can submit your app even if you got this message !

Linked

Related