ITMS-90683 means your app's binary references a protected iOS API (camera, photos, location, microphone and so on) without the matching purpose string in Info.plist explaining why. It often appears for permissions your app never asks for, because a library you installed links that API. In Expo, fix it by setting the permission text through each library's config plugin or ios.infoPlist in app.json, write strings that explain the real reason, remove packages you don't use, and rebuild.
You upload a build, App Store Connect starts processing it, and an email arrives:
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 "MyApp.app" bundle should contain a NSCameraUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data.
Depending on the case, this can block the build from being submitted, or show up as a warning you'll be rejected for later. Either way, it's quick to fix once you know where purpose strings come from in an Expo project.
Disclosure: this guide is from LetsDeployIt, where we fix submission errors like this for AI-built apps.
What a purpose string is
On iOS, every sensitive permission needs a sentence explaining why your app wants it. iOS shows that sentence in the permission prompt ("MyApp Would Like to Access Your Camera… Used to scan receipts"). The sentence lives in Info.plist under a specific key.
The most common keys:
-
NSCameraUsageDescription: camera -
NSPhotoLibraryUsageDescription: reading photos -
NSPhotoLibraryAddUsageDescription: saving photos -
NSMicrophoneUsageDescription: microphone -
NSLocationWhenInUseUsageDescription: location while using the app -
NSLocationAlwaysAndWhenInUseUsageDescription: background location -
NSContactsUsageDescription: contacts -
NSFaceIDUsageDescription: Face ID -
NSBluetoothAlwaysUsageDescription: Bluetooth -
NSUserTrackingUsageDescription: App Tracking Transparency - Calendar and reminders keys, which changed in recent iOS versions (check Apple's docs for the current names)
Why it appears for permissions you don't use
Apple scans your compiled app for references to protected APIs. If any code in the binary references the camera API, you need the camera purpose string, even if your own code never opens the camera.
That code usually comes from a dependency:
- A package that supports both camera and photo library (for example, an image picker) references both APIs.
- An "all-in-one" SDK includes location or Bluetooth features you never call.
- AI app builders and templates often install packages "just in case".
So the error is really asking: does your app need this library?
Fix 1: Set purpose strings with config plugins (recommended)
In an Expo app, you don't edit Info.plist by hand; the native project is generated from your config. Most Expo libraries that need permissions accept the text as config plugin options:
{
"expo": {
"plugins": [
["expo-camera", {
"cameraPermission": "Used to scan receipts so you can add expenses without typing.",
"microphonePermission": "Used to record audio when you film a video note."
}],
["expo-image-picker", {
"photosPermission": "Used to attach photos of your receipts to expenses."
}],
["expo-location", {
"locationWhenInUsePermission": "Used to show stores near you."
}]
]
}
}
Option names differ per library, so check each package's documentation for its plugin options. The advantage of this approach is that the library's plugin also sets anything else it needs.
Fix 2: Set keys directly with ios.infoPlist
For libraries without a config plugin, or to override a value, set the key directly:
{
"expo": {
"ios": {
"infoPlist": {
"NSCameraUsageDescription": "Used to scan receipts so you can add expenses without typing.",
"NSPhotoLibraryUsageDescription": "Used to attach photos of your receipts to expenses."
}
}
}
}
Rebuild with EAS after either change. A purpose string is native configuration, so it can't be delivered as an over-the-air update.
Fix 3: Remove what you don't need
If the API comes from a package you don't use, the cleanest fix is removing the package:
npm uninstall some-unused-package
npx expo install --check
Fewer packages also means a smaller app, fewer permission prompts and fewer questions on Apple's privacy form.
Find out which package is responsible
Generate the native project locally and look at the result:
npx expo prebuild --clean --platform ios
Then open ios/<YourApp>/Info.plist to see which keys are set, and search your dependencies for the API mentioned in the email:
grep -rl "AVCaptureDevice" node_modules --include=*.m --include=*.mm --include=*.swift | head
Replace AVCaptureDevice with the relevant framework or class (for example CLLocationManager for location, CNContactStore for contacts). The package folders in the results tell you which dependency references it. If your ios/ folder isn't committed, delete it again afterwards.
You can also inspect the final config Expo will use, including what plugins changed:
npx expo config --type introspect
Write strings that pass review
Fixing ITMS-90683 with a placeholder like "This app needs the camera" swaps one problem for another: Apple can reject vague purpose strings under Guideline 5.1.1. A good purpose string:
- Says what the feature does for the user: "Used to scan receipts so you can add expenses without typing."
- Matches what the app actually does. Reviewers check.
- Is specific to your app, not copied from a template.
- Is localized if your app is.
Weak examples to avoid: "Needed for the app to work", "Camera access", "We use your location".
And ask for permissions at the moment the feature is used, not on launch. That's better for users and for review.
Don't forget Android
Android has a similar problem in a different shape: libraries can add permissions to your manifest that you don't use, and Google Play asks you to justify sensitive ones. In Expo, you can list the permissions you need in android.permissions and remove ones added by libraries with android.blockedPermissions:
{
"expo": {
"android": {
"blockedPermissions": ["android.permission.RECORD_AUDIO"]
}
}
}
Only block permissions you're sure your app doesn't need; blocking one a feature relies on will break that feature at runtime.
A quick checklist
- Read which key the ITMS-90683 email names.
- Decide: does the app use this feature?
- If yes, set a specific purpose string via the library's config plugin or
ios.infoPlist. - If no, remove the package that references the API.
- Rebuild and upload. Check the next processing email is clean.
- Make sure your App Privacy answers match the permissions you now declare.
Conclusion
ITMS-90683 isn't about your code doing something wrong; it's about your binary referencing protected APIs without explaining why. In Expo, the fix is configuration: set clear purpose strings through config plugins or ios.infoPlist, remove packages you don't need and rebuild. Write the strings for real users, and the same fix protects you from a 5.1.1 rejection later.
If you'd rather hand submission errors off, LetsDeployIt takes AI-built apps through App Store and Google Play review until they're approved.
Which purpose string surprised you the most? Share which library added it in the comments; it'll save someone else a build.
Top comments (0)