Maaz Zindani

Loading the index…

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

react-native-permissions on iOS logs No permission handler detected

ErrorNo permission handler detected

Short answer

On iOS, react-native-permissions only compiles the handlers you list in the Podfile. If the permission you ask for is not listed, the library logs that no handler was detected. Add it to setup_permissions, run pod install, add the Info.plist text and rebuild the app.

  • Applies to react-native-permissions (current), React Native CLI template, Xcode 26, CocoaPods 1.x
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Open the Podfile and look for the setup_permissions call. The permission named in the log message must appear in its list.

    grep -n -A8 "setup_permissions" ios/Podfile
  2. 2Match what you see, then jump to its fix

    1. 1The log names a permission, for example No "Camera" permission handler detectedThe permission is not listed in setup_permissions in the PodfileFix
    2. 2The Podfile already lists the permission, yet the message staysThe Podfile changed but pod install was not run again, or the app was not rebuiltFix
    3. 3pod install prints [Permissions] Unknown permissions: ...The permission name in the Podfile is misspelled or not a supported nameFix

What does the error look like?

  • No permission handler detected
  • No "Camera" permission handler detected

Cause 1 of 3

The permission is not listed in setup_permissions in the Podfile

1Check

The package README says only the permissions listed in setup_permissions are added. The native code includes a handler only when its files were built in, so an unlisted permission has no handler.

grep -n -B2 -A10 "setup_permissions" ios/Podfile

2Fix

Add the permission name to the list, keeping the exact spelling used in the README, and load the setup script before the call.

# ios/Podfile
node_require('react-native-permissions/scripts/setup.rb')

setup_permissions([
  'Camera',
  'PhotoLibrary',
])

3Verify

Run pod install; the permission's handler is now part of the project.

cd ios && pod install

Confirmed by github.com

Did this fix it?

Cause 2 of 3

The Podfile changed but pod install was not run again, or the app was not rebuilt

1Check

The README says pod install must be run again each time you change this config. A JavaScript reload does not rebuild native code, so a running Metro session will not pick the change up.

ls -l ios/Podfile ios/Podfile.lock

2Fix

Run pod install, then build and install the iOS app again from Xcode or the CLI.

cd ios && pod install
# then build and run again from Xcode

3Verify

Request the permission again; the log message is gone and the system prompt shows.

# Xcode: Product > Run, then request the permission again

Confirmed by github.com

Did this fix it?

Cause 3 of 3

The permission name in the Podfile is misspelled or not a supported name

1Check

The setup script matches each name in setup_permissions against the handler folders of the package. A name that matches none is reported as unknown and nothing is added for it.

cd ios && pod install 2>&1 | grep Permissions

2Fix

Use a name from the README list, for example LocationWhenInUse, PhotoLibrary, Notifications or Microphone, with the same capital letters.

setup_permissions([
  'LocationWhenInUse',
  'Microphone',
])

3Verify

pod install no longer prints the unknown-permissions line.

cd ios && pod install 2>&1 | grep Permissions

Confirmed by github.com

Did this fix it?

How do I stop it coming back?

  • Treat the Podfile list and the JavaScript PERMISSIONS constants as a pair: when you request a new permission in code, add it to both in the same commit.
  • Add the matching usage description to Info.plist for every permission you list; the README gives the key for each one.
  • Run pod install after every change to the permissions list, and rebuild instead of reloading.

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:

Related fixes

Next step

Want this handled for good?

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