App Store upload rejected with ITMS-90683: missing purpose string for the camera
ITMS-90683: Missing purpose string in Info.plist.Short answer
ITMS-90683 means your build contains code that can reach the camera, but the app's Info.plist has no usable NSCameraUsageDescription. Add the key with a real sentence, even when a plugin or SDK, not your own code, is what touches the camera. A blank or whitespace-only value is rejected too.
Fix it fast
1Find out which cause you have
Open the rejection email or the App Store Connect message and read which key it names. The key name is the whole diagnosis: here it is NSCameraUsageDescription. Then see whether that key exists in your app's property list.
grep -n -A1 'UsageDescription' ios/Runner/Info.plist2Match what you see, then jump to its fix
- 1
The grep above prints nothing for NSCameraUsageDescriptionThe key is not in Info.plist at allFix - 2
You never ask for the camera, yet the message still names NSCameraUsageDescriptionA plugin or SDK references the camera API, though your own screens never open itFix - 3
grep shows the key, with an empty <string></string> or a value of another type on the next lineThe key exists but its value is blank or not a stringFix - 4
Info.plist has no key, but the target's build settings carry INFOPLIST_KEY_ entriesThe text is set as an Xcode build setting, not in the file you editedFix
- 1
What does the error look like?
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 bundle should contain a NSCameraUsageDescription key with a user-facing purpose string
Cause 1 of 4
The key is not in Info.plist at all
1Check
Apple requires this key whenever an app uses APIs that access the camera. Flutter plugins that take photos, such as image_picker, document the same requirement for the iOS project.
grep -c 'NSCameraUsageDescription' ios/Runner/Info.plist2Fix
Add the key inside the top-level dict of ios/Runner/Info.plist and write one clear sentence that tells the person why the camera is used.
<key>NSCameraUsageDescription</key>
<string>We use the camera so you can take a photo for your profile.</string>3Verify
Build a fresh archive and upload it again. The same key must now be found in the Info.plist of the built app.
flutter build ipaConfirmed by pub.dev
Cause 2 of 4
A plugin or SDK references the camera API, though your own screens never open it
1Check
Apple states that external libraries and SDKs may reference APIs that need a purpose string, and that one is still required for App Review even if your app does not use those APIs. List the camera, scanner and image plugins in pubspec.yaml.
grep -n -i -E 'camera|image_picker|scanner|barcode|qr' pubspec.yaml2Fix
Keep the plugin and add the purpose string, or remove the plugin if you do not need it. Apple's note says you are responsible for all access to protected resources, including access by SDKs.
flutter pub remove <plugin-you-do-not-need>3Verify
Run pub get again and rebuild; if you kept the plugin, confirm the key from the first cause is present.
flutter pub get
flutter build ipaConfirmed by developer.apple.com
Cause 3 of 4
The key exists but its value is blank or not a string
1Check
Apple's rules for purpose strings: the text must not be blank or only whitespace, must be shorter than 4,000 bytes, and must be of the type the key needs, normally a string.
grep -n -A1 'NSCameraUsageDescription' ios/Runner/Info.plist2Fix
Replace the value with a specific sentence in a string element. If you support more than one language, also localize it in an InfoPlist string catalog as Apple describes.
<key>NSCameraUsageDescription</key>
<string>Take a photo to attach it to your report.</string>3Verify
Read the key back, then build and upload a new archive.
grep -n -A1 'NSCameraUsageDescription' ios/Runner/Info.plistConfirmed by developer.apple.com
Cause 4 of 4
The text is set as an Xcode build setting, not in the file you edited
1Check
Apple says Xcode turns a purpose string typed in the Signing and Capabilities editor into a build setting named INFOPLIST_KEY_ plus the key. Look at where your project stores it.
grep -rn 'INFOPLIST_KEY_NSCameraUsageDescription' ios/Runner.xcodeproj/project.pbxproj2Fix
Make sure the Runner target that you archive has the string, either in Info.plist or in the build setting for its Release configuration. Use one place only, so the values do not disagree.
# in Xcode: Runner target > Signing & Capabilities > add Camera,
# then fill in the purpose string3Verify
Archive from the same scheme you upload and read the key in the result.
flutter build ipa --releaseConfirmed by developer.apple.com
How do I stop it coming back?
- Whenever you add a plugin that touches the camera, photos, microphone, location or contacts, read its iOS setup section and add every key it lists the same day.
- Write purpose strings as one specific sentence about what the person gets, not a placeholder such as 'camera'.
- Keep Info.plist keys in one place per target, so a build setting and the file never disagree.
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?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- Dispatch ProA real-time logistics platform: Flutter apps, Spring Boot services and a Kafka event pipeline on AWS.
- Qist BazaarA buy-now-pay-later marketplace built from a blank repo, now past 100K downloads on Google Play.
Related fixes
Mobile 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 fixMobile apps
pod install cannot pick a version of a pod that satisfies every requirement
Specs satisfying the `FirebaseAuth (~> 11.0)` dependency were found, but they required a higher minimum deployment target.
CocoaPods tried every version of the named pod and none fit all requirements.
4 causes, each with a fixMobile apps
flutter run says: Could not run Runner.app, try Xcode Product > Run
Try launching Xcode and selecting "Product > Run" to fix the problem:
Flutter prints this when installing or launching the built app on the iPhone fails, and it hides the real reason.
4 causes, each with a fixMobile apps
flutter doctor says CocoaPods is installed but not working
You appear to have CocoaPods installed but it is not working.
Flutter runs pod --version and treats a failed or unreadable result as a broken install.
3 causes, each with a fixMobile apps
flutter run on iOS or macOS stops with Error running pod install
Warning: CocoaPods not installed. Skipping pod install.
Flutter only reports that pod install failed; the reason is in the lines just above it.
5 causes, each with a fixMobile apps
FirebaseMessaging.getAPNSToken() returns null on iOS
FirebaseMessaging.instance.getAPNSToken() returns null
getAPNSToken() gives null when iOS has not handed the app an APNs token yet or never will.
4 causes, each with a fix