Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

App Review says a purpose string is missing, but it is in InfoPlist.strings

ErrorMissing purpose string in Info.plist

Short answer

A localized InfoPlist.strings file does not replace the base entry. Apple says to put the usage description in Info.plist and, for apps with several languages, add the localized string in InfoPlist.strings as well. Add the key to Info.plist with a real sentence, and make the key names match exactly.

  • Applies to Xcode 26, iOS 18
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Look in the built app, not only the project. Print the key from the Info.plist that was actually packaged and compare it with your InfoPlist.strings.

    plutil -p MyApp.app/Info.plist | grep UsageDescription
    grep -r "UsageDescription" MyApp.app/*.lproj/InfoPlist.strings
  2. 2Match what you see, then jump to its fix

    1. 1plutil shows no NSxxxUsageDescription line, while the .lproj files contain themThe key exists only in localized files, not in Info.plistFix
    2. 2You never call the API yourself, but a plugin or SDK in the build doesThe data comes from a library you did not writeFix

What does the error look like?

  • Missing purpose string in Info.plist
  • Purpose strings exist in InfoPlist.strings but App Store Connect still rejects the app

Cause 1 of 2

The key exists only in localized files, not in Info.plist

1Check

Apple's guidance is that all usage descriptions are declared in the app's Info.plist, and localized strings are an addition for each locale, not a replacement.

plutil -p MyApp.app/Info.plist | grep UsageDescription

2Fix

Add each required key to Info.plist with a sentence that tells the person why the app needs the data. Keep the localized copies in InfoPlist.strings for every language you support.

<key>NSContactsUsageDescription</key>
<string>Your contacts are used to let you invite friends.</string>

3Verify

Build again and print the key from the packaged Info.plist.

plutil -p MyApp.app/Info.plist | grep UsageDescription

Confirmed by developer.apple.com

Did this fix it?

Cause 2 of 2

The data comes from a library you did not write

1Check

Apple says the app owner is responsible for access by third-party libraries. The data class named in the rejection email tells you which key is needed.

grep -rn "NSContacts\|NSCamera\|NSPhotoLibrary\|NSLocation" Pods/ 2>/dev/null | head

2Fix

Add the key the rejection names, and write a description that matches what the library really does with the data. Check the library's own setup notes for the keys it needs.

<key>NSCameraUsageDescription</key>
<string>The camera is used to scan a code you point it at.</string>

3Verify

The packaged Info.plist contains every key the rejection email listed.

plutil -p MyApp.app/Info.plist | grep UsageDescription

Confirmed by developer.apple.com

Did this fix it?

How do I stop it coming back?

  • Treat Info.plist as the base entry and InfoPlist.strings as translations of it, never the other way round.
  • After adding a library, read its iOS setup notes and add every key it names that day.
  • Check the packaged Info.plist in CI before each upload.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Related fixes

Mobile apps

App record creation fails because you lack permission

You cannot add a new app in App Store Connect as a Developer or limited user

Only the Account Holder, an Admin or an App Manager can create an app record, and Apple blocks it until the Account Holder has signed the latest agreement.

3 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.