calling:
Permissions.requestPermission('microphone')
.then((permissionMicrophone) => {
console.log('permissionMicrophone:', permissionMicrophone);

results in:
2017-01-02 09:22:26.381 [info][tid:com.facebook.react.JavaScript] 'permissionMicrophone:', 'undetermined'

when using the simulator. It also does not show microphone in the settings where permissions are handled.

Anyone else seeing this? I wonder if this is an issue with the xcodes simulator since it works fine using an actual device.

Hello!

I keep getting this error when calling checkMultiplePermissions(['camera', 'photo']) on iOS. I added the library(the app is built correctly), added the descriptions to this permissions, nothing helps. Can you advise anything?

Hi i am new to IOS development. I installed react-native-permissions but the ios simulator app wont start now.

• when running from xcode, this shows
  

• when running react-native run-ios, this shows
  An error was encountered processing the command (domain=NSMachErrorDomain, code=-308): The operation couldn’t be completed. (Mach error -308 - (ipc/mig) server died)

I followed your steps correctly:

1. npm install --save react-native-permissions
2. rnpm link

what am i missing here?

Hi,
I want to use the module in my android project. I did use it in my iOS without problem when it was 0.0.2 release.

When i run react-native run-android I got this issue.

Can someone have this issue too ?

Thx

I'm getting undefined from line 71 !this.getPermissionTypes().includes(permission):

requestPermission(permission, type) {
    let options; 

    if (!this.getPermissionTypes().includes(permission)) {
        return Promise.reject(`ReactNativePermissions: ${permission} is not a valid permission type on ${Platform.OS}`)
    } else if (permission == 'backgroundRefresh'){
        return Promise.reject('ReactNativePermissions: You cannot request backgroundRefresh')
    } else if (permission == 'location') {
        options = type || 'whenInUse'
    } else if (permission == 'notification') {
        options = type || ['alert', 'badge', 'sound']
    }

    return RNPermissions.requestPermission(permission, options)
}

I'm thinking that perhaps the polyfill needs to be included in the library?

Thank you for the awesome job, I have a question and hope someone can help, the issue is actually related to react-native itself rather than react-native-permissions; I'm working on an app which has few different types of users, for some users I should beg for "Allow access to location while using the app" while other types of users would willingly "Allow access always", I have both NSLocationAlwaysUsageDescription and NSLocationWhenInUseUsageDescription set in Info.plist, your library does an awesome job checking and requesting a specific type of location tracking permission, but as soon as I call navigator.geolocation.getCurrentPosition() it will pop the "allow always" dialog only because its been set in Info.plist, even when the user has already permitted "while using", this is very annoying from UX point of view and I'm thinking about writing a native module for tracking the location for those users and use it instead of react-native's navigator, but before that I thought maybe someone has already found a workaround for this.

I have this error on Xcode that cause a build error :

Argument list too long: recursive header expansion failed at /Users/arthurlorent/workspace/ecovelo-mobile/ios/../node_modules/react-native-permissions/Example/ios.

I have removed the the Example folder and the error is gone.
I am using react-native v0.37.

Is there particular reason that minSdkVersion is 18?

RN has 16 on it which makes the library not compatible.

openSettings for Android opens application settings which just shows list of permissions for that app. We cannot change permissions like in iOS. It would be better if openSettings for Android opens device settings (ACTION_SETTINGS) instead of app settings (ACTION_APPLICATION_DETAILS_SETTINGS).

They should be the same, I suppose

const RNPTypes = {
    ios: [
        ....
        'photo',
        .... 
    ],
    android: [
        ...
        'photos',
    ]
}

Version

react-native : 0.41.1
lottie-react-native: 1.0.6
lottie-ios: 1.0.2
Xcode: 8.2.1

Code

checkPermission = () => {
    Permissions.requestPermission('bluetooth')
        .then(response => console.log('bluetooth', response))
};

Run app on device iOS 10.
It will popup alert, and I click Setting, to open Bluetooth. then check again.

Console

bluetooth undetermined

Is it Right?

and why not support check bluetooth on android? If not support, We will find other library to check it. @yonahforst Do you have plan to do it?

Hello,

I can't seem to get this working, using React Native and have followed these steps from the readme:

• npm install --save react-native-permissions
• rnpm link

Then running react-native run-ios results in:

Found Xcode project CandidateApp.xcodeproj
Launching iPhone 6 (9.3)...
Building using "xcodebuild -project CandidateApp.xcodeproj -scheme CandidateApp -destination id=EDA8ACD0-CC57-4E0D-9126-3913C8991B17 -derivedDataPath build"
User defaults from command line:
    IDEDerivedDataPathOverride = /Users/tom/Projects/candidate-native-app/ios/build

=== BUILD TARGET RNI18n OF PROJECT RNI18n WITH CONFIGURATION Debug ===

Check dependencies

=== BUILD TARGET RCTLinking OF PROJECT RCTLinking WITH CONFIGURATION Debug ===
Check dependencies

=== BUILD TARGET RCTWebSocket OF PROJECT RCTWebSocket WITH CONFIGURATION Debug ===
Check dependencies

=== BUILD TARGET ReactNativePermissions OF PROJECT ReactNativePermissions WITH CONFIGURATION Debug ===

Check dependencies
Unable to run command 'Libtool libReactNativePermissions.a' - this target might include its own product.

=== BUILD TARGET RCTVibration OF PROJECT RCTVibration WITH CONFIGURATION Debug ===

Check dependencies

=== BUILD TARGET ReactNativeConfig OF PROJECT ReactNativeConfig WITH CONFIGURATION Debug ===
Check dependencies

=== BUILD TARGET RCTActionSheet OF PROJECT RCTActionSheet WITH CONFIGURATION Debug ===

Check dependencies

=== BUILD TARGET React OF PROJECT React WITH CONFIGURATION Debug ===
Check dependencies

** BUILD FAILED **


The following build commands failed:
    Check dependencies
(1 failure)
Installing build/Build/Products/Debug-iphonesimulator/CandidateApp.app
Launching org.reactjs.native.example.CandidateApp
org.reactjs.native.example.CandidateApp: 14142

I opened my project in xCode and found that libReactNativePermissions.a is missing in the ReactNativePermissions project. Any ideas?

Cheers.

As of Xcode 8 and React Native 0.33 it is now necessary to add kit specific "permission" keys to your Xcode Info.plist file, in order to make requestPermission work. Otherwise your app crashes when requesting the specific permission. I discovered this after days of frustration.

Apple Developer Forum thread about the issue: https://forums.developer.apple.com/thread/48959

The solution is:
Open Xcode > Info.plist > Add a key (starting with "Privacy - ...") with your kit specific permission. The value for the key is optional.

Example:
If you need Contacts permission you have to add the key "Privacy - Contacts Usage Description".

It might be helpful to add to the documentation.

Getting the following build error for mipmap-mdli on iOS

Argument list too long: recursive header expansion failed at ... /node_modules/react-native-permissions/Example/android/app/src/main/res/mipmap-mdpi.

If I remove the Example file everything builds correctly.

Code being used:

function CheckPermissions(flow) {
  try {
    Permissions.checkMultiplePermissions(
      ['location', 'photo', 'camera', 'contacts', 'notification']
    ).then(perms => {
        console.debug('checked permissions', arguments);
      },
      () => {
        console.debug('checked permissions failed', arguments);
      }
    );
  }
  catch (e) {
    console.debug('checked permissions failed', e);
  }
}

Error:

 TypeError: Cannot read property 'getPermissionStatus' of undefined

It seems the reference of that is undefined.

Hi,
from my perspective there is a problem with the location permission and their options (always, whenInUse). I my app the location permission with option always is required but if the user sets it manually to whenInUse via device settings the permission request responses authorized. I've debugged a bit and found the reason in RNPLocation.m. When doing a request the first thing that is done is checking the status via getStatus. There, in both cases (always and whenInUse) authorized is returned.

...
        case kCLAuthorizationStatusAuthorizedAlways:
        case kCLAuthorizationStatusAuthorizedWhenInUse:
            return RNPStatusAuthorized;
...

Now there is no logic in request method that does check the option parameter (always) that I have passed. That's why I get authorized from the api even it was not set to always in settings.

Please have an eye on it.

Thanks in advance. Norman

Hi!
Great package, good work!

I was having a problem, but when I started writing this issue I figured it out.

As you can see in the screenshot, the result is different. To the left is your example app, and my app is to the right. I have copied your code exactly, but still get different result.

They are running on the same emulator, with Android SDK 25.

Answer: It is confusing to have SDK versions in both AndroidManifest.xml and android/app/build.gradle. I removed them from AndroidManifest.xml and updated values in build.gradle
AndroidManifest.xml:

    <uses-permission android:name="android.permission.INTERNET" />
    <uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW"/>
    <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
    <uses-permission android:name="android.permission.CAMERA"/>
    <uses-permission android:name="android.permission.RECORD_AUDIO"/>
    <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
    <uses-permission android:name="android.permission.READ_CONTACTS"/>
    <uses-permission android:name="android.permission.READ_CALENDAR"/>

    // I removed following lines
    /*
    <uses-sdk
        android:minSdkVersion="18"
        android:targetSdkVersion="23" />
    */

android/app/build.gradle

...
android {
    compileSdkVersion 25 // Changed to latest SDK
    buildToolsVersion "23.0.1"

    defaultConfig {
        applicationId "com.suvapp"
        minSdkVersion 16 // Decreased this to allow older devices use the app
        targetSdkVersion 25 // Target latest SDK
...

This isn't a bug, but I think that people who are new to configure Android apps will have a hard time understanding how to use permissions at runtime.

Do you @yonahforst think this is something that could be added to README?

When popup is opened, locking the screen will result in a "denied" response, when resuming the application the popup is still opened.

Causing issues to determine the user input in this scenario.

Thanks

Hi,
within ReactNativePermissionsModule in Line 96

mPermissionsModule.requestPermission(permission, new PromiseImpl(resolve, reject));

you missed to replace PromiseImpl parameter with singleresolve and reject callback. It wont build on Android in this way right now. Cheers.

I'm working on a standard for displaying version support on React-Native module README files. I would love your feedback: react-native-version-support-table

Dear developer,

We have discovered one or more issues with your recent delivery for "Ahead!". 
To process your delivery, the following issues must be corrected:

This app attempts to access privacy-sensitive data without a usage description. 
The app's Info.plist must contain an NSCalendarsUsageDescription key with a string 
value explaining to the user how the app uses this data.

This app attempts to access privacy-sensitive data without a usage description. 
The app's Info.plist must contain an NSBluetoothPeripheralUsageDescription key with a string 
value explaining to the user how the app uses this data.

Once these issues have been corrected, you can then redeliver the corrected binary.

Regards,

The App Store team

this is what i do

    _handleAppStateChange = (appState) => {
      if (appState == 'active') {
          /*
           Setup redux store with right permissions to be used accross the app
          */
          Permissions.checkMultiplePermissions(Permissions.getPermissionTypes())
              .then( status => {
                  this.props.dispatch_permissions_set_all_permissions(status);
              });
      }
    }

An at one point in my app i do this

: {text: 'Open Settings', onPress: Permissions.openSettings},

And this

Permissions.requestPermission("camera")

I don't se how this would affect the above mentioned permissions.

I'm attempting to use this module along with react-native-android-permissions, the issue is that requiring this module throws the following error.

I've forked and fixed it by adding a ReactNativePermissions.android.js as placeholder.

Would you accept a PR?

If I refuse the 'alert' that asks me if I want to allow location the app throws me a error:

But the permission is write in AndroidManifest.xml and if I accept the alert the app gets my location correctly.

EDIT: Sorry, I solved it. I was calling the getCurrentPosition when refused.

Hi,

With React Native 0.33, I get the following error when I try to build my app for Android:

:react-native-permissions:compileReleaseJavaWithJavac
/Users/mvila/Projects/enchante-app/node_modules/react-native-permissions/android/src/main/java/com/joshblour/reactnativepermissions/ReactNativePermissionsModule.java:82: error: method requestPermission in class PermissionsModule cannot be applied to given types;
    mPermissionsModule.requestPermission(permission, new Callback() {
                      ^
  required: String,Promise
  found: String,<anonymous Callback>,<null>
  reason: actual and formal argument lists differ in length
1 error
:react-native-permissions:compileReleaseJavaWithJavac FAILED

I guess there is a breaking change in 0.33.

First, thanks for your nice package that is working like a charm.

I just noticed that there is one important missing permission for Android.
Indeed, there is no way to ask permission for the Android READ_EXTERNAL_STORAGE and WRITE_EXTERNAL_STORAGEpermissions that are required to use some other packages as https://github.com/bamlab/react-native-image-resizer or https://github.com/johanneslumpe/react-native-fs that are manipulating files and stuff in the device storage.

I had to use http://facebook.github.io/react-native/releases/0.37/docs/permissionsandroid.html in order to request the storage permission.
It would be great to add it to your package !

The latest commits in master breaks in versions of React Native <= 0.39. Could this package versions be identified in specific Release versions so that we can safely assign the version numbers in our package.json and avoid breaks?

I'm trying to understand restricted. Can the camera or microphone permission return restricted? Can you give me some examples of when restricted is returned when getPermissionStatus() is called?

Hi,

I am using RN 0.35.0 and already tried rnpm link and I also tried doing the manual linking but still getting the following error:

error: package com.joshblour.reactnativepermissions does not exist

Thanks

error: method requestPermission in class PermissionsModule cannot be applied to given types;
mPermissionsModule.requestPermission(permission, new PromiseImpl(resolve, reject));

The latests change to support react-native 0.40 seem to published on npm.
The headers are

#import "RCTConvert.h"

Thank you.

I have a component that uses this module to check for and acquire the user's location.

    Permissions.getPermissionStatus('location')
      .then((response) => { ... });

When I run my unit test suite (Enzyme) on this component, I get the following error:

TypeError: Cannot read property 'getPermissionStatus' of undefined
      at ReactNativePermissions.getPermissionStatus (node_modules/react-native-permissions/ReactNativePermissions.js:62:11)

How does one test their components that use this module? Is there a way to mock this out?

Hi,

first of all, thanks for this component 👍

I have a little problem with Permissions.openSettings() (using version 0.2.5) - as mentioned in the title, as soon as I change the permissions of, e.g., my camera, the app crashes.. No error message, nothing..

• desciptions for Camera and Photos usage are added in Info.plist
• don't know if that has something to do with this or another comonent, but when running rnpm link, I get the error ERR! ERRPLIST Could not locate Info.plist. Check if your project has 'INFOPLIST_FILE' set properly

Any idea what could be the problem..?

This may or may not be a general problem, but it's problematic for our app and diverges from how React Native's built-in PushNotificationsIOS works, so I wanted to raise it.

https://github.com/yonahforst/react-native-permissions/blob/master/permissions/RNPNotification.m#L49

This stops registerForRemoteNotifications / registerForRemoteNotificationTypes being called if the user has been asked for permission already. When users log out of our app we unregister their push endpoint. When they log in again this line prevents them being registered because the user defaults flag will be true.

After following the android linking guide, can not link the library

React Native 0.33

error:
react-native-permissions:compileReleaseJavaWithJavac FAILED

Are they to be ignored?

The auto linker didn't automatically include the include the "compile project(':react-native-permissions')" in the app\build.gradle file. After addressing that, I get an error

"Could not expand ZIP '...react-native-permissions-release.aar', which I am guessing means there was a problem with the aar that gradle created, but I don't really have any other debug information (I'm a little new to react-native and building android apps in general).

Thanks for this great little library!

Just a little bug I've run into:
On Android, shouldShowRequestPermissionRationale indicates whether we should explain to the user why we need the permission, not whether the user has been presented with the permission dialog.

It returns false in two cases:

1. We have not asked the user for this perimssion yet.
2. We have asked the user for this permission at least two times, and the user selected "never ask again" last time we tried.

As a result, if a user selects "never ask again", getPermissionStatus and requestPermission will return "undetermined" instead of "denied".

Code:
ReactNativePermissionsModule.java#L64

Hey, thanks for this library — it fits my use case perfectly.

I didn't see libReactNativePermissions.a anywhere in the repo (per the installation instructions in the README) or in the npm package. Was it omitted by accident, or is there something I'm missing on my end?

Thanks!

I get this error when trying to run on IOS:

** BUILD FAILED **

The following build commands failed:
CompileC /Users/katarina/AndroidStudioProjects/reactnative-kitchensink/ios/build/
Build/Intermediates/ReactNativePermissions.build/Debug-iphonesimulator/ReactNativePermiss
ions.build/Objects-normal/x86_64/ReactNativePermissions.o ReactNativePermissions.m normal
x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)

Installing build/Build/Products/Debug-iphonesimulator/kitchensink.app
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=2):
Failed to install the requested application
An application bundle was not found at the provided path.
Provide a valid path to the desired application bundle.
Print: Entry, ":CFBundleIdentifier", Does Not Exist

Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/
Debug-iphonesimulator/kitchensink.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist

I tried to link library manually but I can't find "libReactNativePermissions.a" file.

I tried this import Permissions from 'react-native-permissions'; and Permissions is undefined.

Also tried import {NativeModules} from 'react-native'; and NativeModules.ReactNativePermissions is undefined.

And yes I do have it linked in my xcode.

在undetermined状态下，点击不是应该会弹出系统级别的提示窗口吗，还是我少些什么东西了

Hey, you might want to undo this pull. This allowed me to build in the version of RN that I was using (30), thus solving issue #45, but unfortunately it looks like it broke it for the latest version of RN (37, I just upgraded) I can verify that undoing this pull allows you to build using the latest RN version. The only real fix I can think of for this, is to add versions/releases to this project.

Hi,
Thanks for this utility! Just wondering if there was an Android app equivalent? I'm just checking as I do want to support Android at one stage. Same behaviour, no reprompt - we'll guide the user into providing the required access if required.

Thanks

Hi yonahforst, thanks for this module!

I'm unable do request location permission using RN 0.31. It seems like RN change it NativeModules structure and now this doens't work anymore

var RNPermissions = ReactNative.NativeModules.ReactNativePermissions;

So i get this error (title of this issue) in the line 81 of ReactNativePermissions.js

    requestPermission(permission, type) {
        let options;

        if (this.getPermissionTypes().indexOf(permission) === -1) {
            return Promise.reject(`ReactNativePermissions: ${permission} is not a valid permission type on ${Platform.OS}`)
        } else if (permission == 'backgroundRefresh'){
            return Promise.reject('ReactNativePermissions: You cannot request backgroundRefresh')
        } else if (permission == 'location') {
            options = type || 'whenInUse'
        } else if (permission == 'notification') {
            options = type || ['alert', 'badge', 'sound']
        }

        return RNPermissions.requestPermission(permission, options)
    }

I tried to fix it locally, but then an exception in BaseJavaModule.java was thrown. Something about a number of parameters.

is there other reports like this?

If you need more information, let me know

Hi @yonahforst, I'm developing for android and iOS and the permission identifier for photos is different on these platforms. I have to use "photos" on Android and "photo" on iOS. Can you roger that? Seems like a bug?!?

Using "react-native-permissions": "^0.2.4"

Thank you in advance.

permission.toUpperCase() (in ReactNativePermissionsModule.java:117) converts "microphone" to "MİCROPHONE" so we get "MİCROPHONE is not a constant in com.jshblour.reactnativepermissions.ReactNativePermissionsModule$RNType"

when we try to use MICROPHONE instead of "microphone" ==> "Possible Unhandled Promise Rejection" and module is not working...

Which IOS versions are supported?

react-native: 0.27

When i tried to use getPermissionStatus('photo') i got an 'is not a function' error.

So i started to use Permissions.default.photoPermissionStatus() which looks like depricated. Also there isn't an openSettings function in this object.

This is the Permissions object when i require 'react-native-permissions'

{ default: 
   { StatusUndetermined: 'undetermined',
     StatusDenied: 'denied',
     StatusAuthorized: 'authorized',
     StatusRestricted: 'restricted',
     locationPermissionStatus: [Function],
     cameraPermissionStatus: [Function],
     microphonePermissionStatus: [Function],
     photoPermissionStatus: [Function],
     contactsPermissionStatus: [Function],
     eventPermissionStatus: [Function],
     reminderPermissionStatus: [Function],
     bluetoothPermissionStatus: [Function],
     notificationPermissionStatus: [Function],
     backgroundRefreshPermissionStatus: [Function] } }