◉RORK LABJP
●MCP — Rork now lets you add and manage your own MCP servers inside Plugins (11/21)●2.5 ROUTE — From 12/1, apps calling gemini-2.5-flash are routed to 3.5 Flash-Lite and billed at its rates (9 days left)●CHANNEL — Users report Android notification channel reads and writes failing in Expo Go●NEW — New: three clues to check before replying to a stuck-on-splash review●EXPORT — Export your projects before you downgrade or cancel a plan●SONNET 4.5 — Apps that call Sonnet 4.5 through the API should switch before it retires on 11/30●MCP — Rork now lets you add and manage your own MCP servers inside Plugins (11/21)●2.5 ROUTE — From 12/1, apps calling gemini-2.5-flash are routed to 3.5 Flash-Lite and billed at its rates (9 days left)●CHANNEL — Users report Android notification channel reads and writes failing in Expo Go●NEW — New: three clues to check before replying to a stuck-on-splash review●EXPORT — Export your projects before you downgrade or cancel a plan●SONNET 4.5 — Apps that call Sonnet 4.5 through the API should switch before it retires on 11/30
Articles/App Dev
◇ App Dev/2026-11-16Intermediate

I Set cameraPermission to false for a Photo Picker, and the QR Scanner Lost Its Camera Too

In expo-image-picker, cameraPermission: false deletes NSCameraUsageDescription from Info.plist on iOS and blocks CAMERA for every package on Android. Here is what happens when you also use expo-camera, and a working script that checks permissions before you submit.

Expo237expo-image-pickerexpo-cameraInfo.plist9iOS permissionsAndroid permissionspre-release checksRork620

It was late afternoon, and I was tidying the config of an app with two screens: one that picks wallpaper material from the photo library, and one that scans QR codes. The picker never opens the camera, so I thought writing cameraPermission: false in the expo-image-picker config would trim one permission I didn't need.

That line has a trap in it. After reading Expo issue #53507, filed on November 14, and following the plugin source, I found that false does not mean "the picker won't use the camera." It means remove the camera permission from the whole app.

The short version: one value in one plugin can rewrite a permission that belongs to another package. If you ship without noticing, the iOS app crashes the moment the camera opens.

What actually happens

The reporter's repro is a blank project with expo-camera and expo-image-picker, and this in app.json:

"plugins": [
  ["expo-image-picker", { "photosPermission": "Pick a photo.", "cameraPermission": false }],
  ["expo-camera", { "cameraPermission": "Scan QR codes." }]
]

After npx expo prebuild --clean, the report says (expo 58.0.25, expo-image-picker 58.0.10, expo-camera 58.0.14; SDK 57 behaves the same):

  • iOS: NSCameraUsageDescription is gone from Info.plist, including the "Scan QR codes." string from expo-camera
  • Android: android.permission.CAMERA gets tools:node="remove", so it is stripped whichever package adds it
  • On device or simulator: opening a CameraView crashes because the usage description is missing

The docs describe false only in Android terms: it blocks the CAMERA permission on Android. Nothing there suggests the iOS string disappears too. That is how I read it at first, as well.

The source makes the reason plain

On iOS the work is done by applyPermissions in @expo/config-plugins. It is about 20 lines, and the part that matters is this branch:

if (permissions[permission] === false) {
  delete infoPlist[permission];
} else {
  infoPlist[permission] = permissions[permission] || infoPlist[permission] || description;
}

With false, the key is deleted from Info.plist, without checking whether another plugin already wrote it. With a string, an existing value is kept. So a string adds, and false subtracts.

On Android, the expo-image-picker plugin says so in a comment: if the user sets a permission to false, block it so no package can add it. That part is by design, and withBlockedPermissions shuts CAMERA out.

The Expo triage note also points out that only one plugin order was tested. Swapping the order might rescue you, but I'd rather not lean on that. A config whose meaning depends on line order is exactly the kind I break six months later.

The fix: drop false and give both plugins the same string

The reporter worked around it by passing the same cameraPermission string to both plugins. I think that is the cleanest answer.

"plugins": [
  ["expo-image-picker", {
    "photosPermission": "Choose a photo from your library to use as a wallpaper.",
    "cameraPermission": "The camera is used to scan QR codes."
  }],
  ["expo-camera", {
    "cameraPermission": "The camera is used to scan QR codes."
  }]
]

Whichever plugin writes last, the same sentence survives. If the picker never launches the camera, having a description on its side costs nothing.

If no part of your app uses the camera at all, that is the moment false earns its keep. Reliably blocking CAMERA on Android is reassuring when some third-party SDK tries to add it quietly. The line I now draw is this: read false as "this app may not use it," never as "this feature doesn't need it."

How to word the strings themselves is in rewriting purpose strings after a rejection, and the opposite problem, unused strings piling up, is in the Info.plist that had nine strings with an empty plugins array. This one is about a string you need going missing.

A script that checks permissions before you submit

Even after the fix, adding one more plugin can bring the problem back. So I wrote a small script that compares the prebuild output with the list of permissions the app really uses. It needs nothing beyond the Python standard library.

What it solves: it finds three things in one pass, before a build reaches a device. A missing key, a key still on the default English text, and an Android permission that has been blocked.

#!/usr/bin/env python3
"""Compare the permissions prebuild produced with the ones the app actually uses.
Usage: python3 check_permissions.py  (run from the project root)"""
import glob
import plistlib
import sys
import xml.etree.ElementTree as ET
 
# Write the permissions your app really uses, by hand (iOS key, Android permission)
REQUIRED = [
    ("NSCameraUsageDescription", "android.permission.CAMERA"),
    ("NSPhotoLibraryUsageDescription", None),
]
DEFAULT_PREFIX = "Allow $(PRODUCT_NAME)"  # the default sentence is weak in review
ANDROID_NS = "{http://schemas.android.com/apk/res/android}name"
TOOLS_NODE = "{http://schemas.android.com/tools}node"
 
problems = []
 
plists = [p for p in glob.glob("ios/*/Info.plist") if "Pods" not in p]
if not plists:
    sys.exit("No ios/*/Info.plist found. Run npx expo prebuild --clean first")
with open(plists[0], "rb") as f:
    info = plistlib.load(f)
 
manifest = "android/app/src/main/AndroidManifest.xml"
granted, removed = set(), set()
try:
    for el in ET.parse(manifest).getroot().iter("uses-permission"):
        name = el.get(ANDROID_NS)
        # tools:node="remove" means "strip it, whichever package adds it"
        (removed if el.get(TOOLS_NODE) == "remove" else granted).add(name)
except FileNotFoundError:
    print(f"Note: {manifest} is missing, skipping Android")
 
for ios_key, android_perm in REQUIRED:
    text = info.get(ios_key)
    if text is None:
        problems.append(f"iOS: {ios_key} is missing (the app crashes when it opens)")
    elif text.startswith(DEFAULT_PREFIX):
        problems.append(f"iOS: {ios_key} is still the default text: {text}")
    if android_perm and android_perm in removed:
        problems.append(f"Android: {android_perm} is stripped by tools:node=\"remove\"")
    elif android_perm and granted and android_perm not in granted:
        problems.append(f"Android: {android_perm} is not in the manifest")
 
for p in problems:
    print("NG", p)
print("OK everything is in place" if not problems else f"Fix {len(problems)} item(s) before you submit")
sys.exit(1 if problems else 0)

Run it from the project root after npx expo prebuild --clean. I tried it on a dummy Info.plist and manifest with the camera string removed and tools:node="remove" on CAMERA, and got this:

NG iOS: NSCameraUsageDescription is missing (the app crashes when it opens)
NG Android: android.permission.CAMERA is stripped by tools:node="remove"
Fix 2 item(s) before you submit

Restoring the string and removing remove turns it into "OK everything is in place," and the exit code goes from 1 to 0. One extra line in CI is enough to stop a build on it.

REQUIRED is written by hand on purpose. Which permissions an app uses is a decision, and a list you wrote yourself keeps a record of it in a way that scraping the code does not. As an indie developer who now has AI assemble more of my apps, this is the one list I keep in human hands.

The order I follow for an app built with Rork

A project exported from Rork works the same way.

  1. Open plugins in app.json (or app.config.ts) and search for false
  2. Check whether any other screen or package uses that permission
  3. If something does, replace false with a description string
  4. Run npx expo prebuild --clean, then the script above
  5. On iOS, open the camera screen by hand at least once before you submit

Skip step 5 and you won't notice a permission you forgot to put in REQUIRED. A machine check only guards the list you gave it.

Where I'd start

The issue is still open, and prebuild may warn about this one day. Even so, I expect false to keep subtracting, on both iOS and Android, for some time.

Search your own app.json for Permission": false first. If nothing turns up, that is the best news you can get.

Share

Thank You for Reading

Rork Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.

  • ✦Copy-paste ready implementation code
  • ✦New advanced guides published daily
  • ✦$5/mo or $10 for lifetime access
View Membership →

If you found this article helpful, a small tip ($1.50) would mean a lot to us. Your support helps keep this site ad-free and covers server and hosting costs.

Related Articles

◈ Getting Started2026-10-19
My plugins Array Was Empty, and Info.plist Still Had Nine Permission Strings
Even with an empty plugins array, every Expo package you install can add permission strings to Info.plist. I ran prebuild on SDK 58, counted them, and wrote the settings and a small audit script that remove them.
◇ App Dev2026-08-21
Apple's automated pass reads what your purpose strings are for, not whether they exist
Submit a Rork or Expo iOS build and you may get it back under Guideline 5.1.1 with a note about placeholder or otherwise insufficient purpose strings. Here is how to read a rejection that names no key, and how to rewrite the strings from app.json.
◇ App Dev2026-10-28
"Project is incompatible with this version of Expo Go": Three Places to Check Before Blaming Your Project
When Expo Go says your project needs a newer Expo Go, there are three things to compare before you delete node_modules: the project's SDK, the SDK the app supports, and, on Android, a real mix-up in Expo Go 56.0.1. Here is the order I check them in.