Please stop spamming the issue with +1 comments. If you are experiencing the same problem, and don’t have anything valuable to add, use reaction instead.

Spamming the issue only makes it difficult to find valuable comments which could actually help with fixing the issue.

As of now, there are 2 workarounds before a proper fix is provided:

1. requestLegacyExternalStorage flag as mentioned here: https://github.com/react-native-community/react-native-image-picker/issues/1233#issuecomment-561349254

2. lower your targetSDK to version 28 (android/build.gradle):

        buildToolsVersion = "28.0.3"
        minSdkVersion = 16
        compileSdkVersion = 28
        targetSdkVersion = 28

The issue can be related to new package visibility (https://developer.android.com/about/versions/11/privacy/package-visibility). After all updates (at least Android Studio 4.1) try to add in your manifest <queries> that shows what action is required in app. In my case problem disappears when adds.

IMAGE_CAPTURE -> CAMERA, GET_CONTENT -> GALLERY (to get files change mimeType if you want video) PICK -> GALLERY (should change mimetype if u want video) CHOOSER -> GALLERY (if someone have other image browsers)

You can also check in logcat what queries you have to add (should contains “BLOCKED” or “no permission”. Error is because ImagePickerModule when you don’t have permission in Intent with resolveActivity returns null (u can comment it to check better errors in startActivityForResult)

<queries>
    <intent>
        <action android:name="android.media.action.IMAGE_CAPTURE" />
    </intent>
    <intent>
        <action android:name="android.intent.action.GET_CONTENT" />
        <data android:mimeType="image/*" />
    </intent>
    <intent>
        <action android:name="android.intent.action.PICK" />
        <data android:mimeType="image/*" />
    </intent>
    <intent>
        <action android:name="android.intent.action.CHOOSER" />
     </intent>
</queries>

I hope that can help you

Hey, same for me with RN 0.63.2 and 2.3.3. Camera did not open and Logical say’s “Permission denied”.

With this option android:requestLegacyExternalStorage=“true” it works at the moment.

+1 A fix for this prior to Android 11 coming out of beta would be great.

Please stop spamming the issue with +1 comments. If you are experiencing the same problem, and don’t have anything valuable to add, use reaction instead.

Spamming the issue only makes it difficult to find valuable comments which could actually help with fixing the issue.

As of now, there are 2 workarounds before a proper fix is provided:

1. requestLegacyExternalStorage flag as mentioned here: #1233 (comment)
2. lower your targetSDK to version 28 (android/build.gradle):

        buildToolsVersion = "28.0.3"
        minSdkVersion = 16
        compileSdkVersion = 28
        targetSdkVersion = 28

Maybe it’s worth to the Readme file?

+11111111111111111111111111

+1 a fix for this

works now with - android:requestLegacyExternalStorage=“true” against SDK 29 targetSdkVersion = 29 compileSdkVersion 29 buildToolsVersion = “29.0.3”

I used this solution it worked on development, when deployed to internal test on google play and install from the store it didn’t work

Hey I was also facing the same issue along with gallery, so I found below mentioned solution. Although it seems like a temporary fix but can work meantime till the fix is done.

You just need to add the

android:requestLegacyExternalStorage=“true”

under the Application Tag of AndroidManifest.xml

Refer to this comment for the above mentioned solution: #1233 (comment).

@NMahendroo This solution will be deprecated as of Android 11 (this line in the manifest will be ignored), so a more permanent solution will still need to be found.

+1

+1

But lowering the target sdk version is not a solution given that Google Play will reject app:

Note: From 2 November 2020, app updates must target Android 10 (API level 29) or higher.

https://developer.android.com/distribute/best-practices/develop/target-sdk

This thread is too old with solution for various versions of this library. The latest version does not have this issue, feel free to create a new issue with details. I am happy to fix it. Thanks.

+1

+1 a fix for this

works now with - android:requestLegacyExternalStorage=“true” against SDK 29 targetSdkVersion = 29 compileSdkVersion 29 buildToolsVersion = “29.0.3”

Please stop spamming the issue with +1 comments. If you are experiencing the same problem, and don’t have anything valuable to add, use reaction instead.

Spamming the issue only makes it difficult to find valuable comments which could actually help with fixing the issue.

As of now, there are 2 workarounds before a proper fix is provided:

1. `requestLegacyExternalStorage` flag as mentioned here: [#1233 (comment)](https://github.com/react-native-community/react-native-image-picker/issues/1233#issuecomment-561349254)

2. lower your targetSDK to version 28 (`android/build.gradle`):

        buildToolsVersion = "28.0.3"
        minSdkVersion = 16
        compileSdkVersion = 28
        targetSdkVersion = 28

I receive a notification from google and new apps will not accept target version less than 29 and how don’t use it yet will need to upgrade.

A possible workaround (if you don’t need your pics to be public) is to use the privateDirectory flag:

storageOptions={{ privateDirectory: true  }}

+1 a fix for this works now with - android:requestLegacyExternalStorage=“true” against SDK 29 targetSdkVersion = 29 compileSdkVersion 29 buildToolsVersion = “29.0.3”

I used this solution it worked on development, when deployed to internal test on google play and install from the store it didn’t work

@AllanKlaus I installed the app to the Google Play Internal App Sharing too but was able to get the Camera and Photos to open with this setting. However, I was not able to upload the actual image. Not sure if this issue is directly related with Image Picker or the latest version of React Native (0.63.2).