App Review says a purpose string is missing, but it is in InfoPlist.strings
Missing purpose string in Info.plistShort 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.
Fix it fast
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.strings2Match what you see, then jump to its fix
What does the error look like?
Missing purpose string in Info.plistPurpose 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 UsageDescription2Fix
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 UsageDescriptionConfirmed by developer.apple.com
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 | head2Fix
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 UsageDescriptionConfirmed by developer.apple.com
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 Store upload rejected with ITMS-90683: missing purpose string for the camera
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.
ITMS-90683 means your build contains code that can reach the camera, but the app's Info.plist has no usable NSCameraUsageDescription.
4 causes, each with a fixMobile apps
Cannot change the App Privacy answers in App Store Connect
Publish Your App Privacy Responses?
Only the Account Holder, Admin and App Manager roles can answer the App Privacy questions.
2 causes, each with a fixMobile 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 fixMobile apps
You cannot find the button to pull your app back from review
No 'remove this version from review' message appears on the version page
There is no button called Reject Binary.
3 causes, each with a fixMobile apps
Your Apple Account cannot sign in to App Store Connect
Sign-in to App Store Connect is refused for an account that should have access
App Store Connect does not open to every Apple Account.
3 causes, each with a fixMobile apps
Apple rejected the app under Guideline 4.3, Design: Spam
Guideline 4.3(b) - Design - Spam
Guideline 4.3 is Apple's duplicate rule.
5 causes, each with a fix