-
Notifications
You must be signed in to change notification settings - Fork 986
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android 11 new policy "MANAGE_EXTERNAL_STORAGE" #998
Comments
Do we have any update on that, please? Currently, react-native-fs is using deprecated android permission which will be rejected by Google in the future. |
there's an older issue also about this, but no one seems to be helping #926 |
from what I have researched as long as apps target sdk is set to 29 or less, we should be good, but nonetheless, this issue needs to be addressed sooner or later |
I guess using the Storage Access Framework or Media Store API will do the work... which is tricky to implement...? and I also need help in? |
I looked through a few pages of opens issues to tie back the related issues caused by the upgraded Scoped Storage changes in Android 11. If you see other, older ones, please feel free to reference them back to this single issue so it's easier for everyone to track. |
While we are targeting Sdk29, this lib is working well. I tried to implement the new Scopped method, but seems that react-native-fs doesnt support it (withtout the android:requestLegacyExternalStorage="true"). There is something that we can do, to accept tagertSdk30? |
Have any solution? |
Does anyone have solution? I think it is very important issue for android. |
I dont think that we have any solution yet. |
Any update? |
Anything new here? has anyone found a solution? |
Use instead of MANAGE_STORAGE Use below code to save file No need allow any storage permission in > Q for the same:
|
You need to add additional permission called |
Hi, any updates how to fix this? We need to target Android 11 in order to deploy an update to Play store, is there any work around for targetSdkVersion = 30? |
Hi, any workaround or updates on this? We are using targetSdkVersion 30 and are not able to copy or move files from an external location. |
Any update ? |
Any work around about this issue. |
After not able to proceed, I've given up and moved on to expo-file-manager package to be able to do I what I needed to do. |
@guofoo did you switch to the expo-file-manager library?? Is it better than expo-file-system? Or was a solution found with this library? |
I solved this issue for all React Native developers. I published an NPM package called react-native-manage-external-storage that you can use it to access all files in an android phone. Here is a link checkout https://www.npmjs.com/package/react-native-manage-external-storage |
I simplified @Hassan-jr 's package to make development easier and without strange problems. I also published an NPM package called react-native-external-storage-permissions that you can use it to access all files in an android phone. Here is a link checkout https://www.npmjs.com/package/react-native-external-storage-permission |
Google App Store send me a message as below. What should we do about it?
We've detected that your app contains the requestLegacyExternalStorage flag in the manifest file of 1 or more of your app bundles or APKs.
Developers with apps on devices running Android 11+ must use Scoped Storage to give users better access control over their device storage. To release your app on Android 11 or newer after May 5th, you must either:
For apps targeting Android 11, the requestLegacyExternalStorage flag will be ignored. You must use the All files access permission to retain broad access.
Apps requesting access to the All files access permission without a permitted use will be removed from Google Play, and you won't be able to publish updates.
The text was updated successfully, but these errors were encountered: