react-native-fs: Unable to download file in Android 11 (ENOENT: no such file or directory, open '/storage/emulated/0/fileName.pdf')

<application
        android:requestLegacyExternalStorage="true"

setting this solves the file download error on Android 10/11

If you want to be able to download a document to android storage, you must request user permission for PermissionsAndroid.PERMISSIONS.WRITE_EXTERNAL_STORAGE before downloading and saving to storage, as mentioned by @Yandamuri . But if you also want to view/open the document for the user, you must also request user permission PermissionsAndroid.PERMISSIONS.READ_EXTERNAL_STORAGE before attempting to open it.

For older versions of android, you must add the necessary permissions from above (see below) to AndroidManifest.xml under manifest tag before application tag. These are requested when installing the app rather than when using them and this applies to other android permissions as well (bluetooth, camera etc).

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
  package="<your package name here>">
    ...
    <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
    ...
    <application
    ....
    </application>
</manifest>

try for the permission in following way,

const granted = await PermissionsAndroid.request(PermissionsAndroid.PERMISSIONS.WRITE_EXTERNAL_STORAGE);

Add this permission to manifest file :

<uses-permission android:name="android.permission.ACCESS_MEDIA_LOCATION" />

Use below code to save file No need allow any storage permission in > Q for the same:

if (SDK_INT >= Build.VERSION_CODES.Q) { ContentResolver resolver = context.getContentResolver(); ContentValues contentValues = new ContentValues(); contentValues.put(MediaStore.MediaColumns.DISPLAY_NAME, fileName); contentValues.put(MediaStore.MediaColumns.MIME_TYPE, "video/mp4"); contentValues.put(MediaStore.MediaColumns.RELATIVE_PATH, dir); Uri videoUri = resolver.insert(MediaStore.Video.Media.EXTERNAL_CONTENT_URI, contentValues); OutputStream output = resolver.openOutputStream(videoUri); output.write(data, 0, count); output.close(); }

Hello, since by the 5th of May Google Play will ignore this flag and remove app that do not use API like Media Store or Storage Access Framework how should we handle this?

For android 11 + Try this let dirPath = ${RNFS.ExternalStorageDirectoryPath}/Documents/APP name Don’t try to create App directory in root… use any existing folder present already in root and create app folder inside that folder… In my case, I have created inside Documents

found any solution to save files in android 11?

Also, keep in mind that android 11 added scoped storage for apps by default and all react-native packages that I know of are not yet prepared to handle this. Until a next android version, you can opt out of this as mentioned here: https://developer.android.com/about/versions/11/privacy/storage.

So you probably also need to set requestLegacyExternalStorage="true" on the application node in the manifest for using the old storage model also on android 11, check android developer documentation for more info. In the link above it is stated that: The default value is: - false for apps with targetSdkVersion >= 29 (Q). - true for apps with targetSdkVersion < 29.

@Shreyakkk Your solution seems to be working for me on Android 12. Thanks.

EDIT: Throughout the day I found that if I delete a downloaded file from my device’s file system, RNFS.ExternalStorageDirectoryPath or RNFS. DownloadDirectoryPath would throw this error IF the app tries to download another file by the same name again. So for now I’ve added Date.now() to toFile to make sure every file the app downloads has a different name (thus a different path).

Perhaps my experience so far is not extensive enough to make any definitive conclusions, but this sure seems weird.

Hi @trungitvn I am getting the same error for Android 10. I guess your solution might work for me, but I don’t understand your code completely. Is DownloadManager another library that you are using? Really appreciate it if you could give some help. Thanks

@parameshwari5 Of course, it will work. But it won’t work with version 30 and Google Play require the maxSdkVersion to be 30 now.

you can use: if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.GINGERBREAD_MR1) { mPath= getActivity().getExternalFilesDir(Environment.DIRECTORY_DCIM) + “/” + now + “.jpeg”; } else { mPath= Environment.getExternalStorageDirectory().toString() + “/” + now + “.jpeg”; }

I noticed the same error message and it had nothing to do with permissions.

The problem was that I was trying to create a file with a name that was already taken on the Downloads directory.

I found the solution for myself. Hope to help someone!

• In AndroidManifest.xml set:

<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"
        android:maxSdkVersion="29" /> //For <= Android 10
    <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
    <uses-permission android:name="android.permission.INTERNET" />
    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />

    <application
        android:requestLegacyExternalStorage="true" //For Android 10
        ...

• To download and save a file for Android 11, i use code:

public static long downloadFile(Context context, File file) {
        String filePath = file.getAbsolutePath();
        Uri downloadUri = Uri.parse(URL);
        DownloadManager.Request request = new DownloadManager.Request(downloadUri);
        request.setAllowedNetworkTypes(DownloadManager.Request.NETWORK_WIFI
                | DownloadManager.Request.NETWORK_MOBILE);
        request.setDestinationInExternalPublicDir(Environment.DIRECTORY_DOWNLOADS, filePath);
        DownloadManager downloadManager = (DownloadManager) context.getSystemService(Context.DOWNLOAD_SERVICE);
        return downloadManager.enqueue(request);
    }

• To check exists file:

static public File getAbsoluteFile(String relativePath) {
        return new File(Environment.getExternalStoragePublicDirectory(Environment.DIRECTORY_DOWNLOADS),
                relativePath);
    }
static public boolean isDownloaded(File file) {
        File file = getAbsoluteFile(filePath);
        return file.exists();
    }

@gabrielporcher I am also using target SDK 29 with android:requestLegacyExternalStorage=“true” and can confirm that you can successfully upload the app to Play Store. Yet they have notified in Play Console that after august the app will be required to target SDK 30 and android:requestLegacyExternalStorage=“true” will not work anymore, forcing us to use the new scoped storage.

I am also confused as I don’t fully understand the Scoped Storage, nor think that any react native packages are ready for this change at this moment.

Hello @Yandamuri, this is the reference: docs.

The flag

<application
        android:requestLegacyExternalStorage="true" 

will be ignored soon and also app uploaded with this flag enable are receiving a warning form Google about this fact.

Thank you!

@marf is there any official note regarding this? if so, Can you please ping me the link?