You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
This task concerns only Android version:
My app has defined write_external_storage permission in AndroidManifest.xml, as I need it in other place:
I use camereawesome for taking pictures, I save them inside application directories, using path_provider.getTemporaryDirectory.
This permission is not required for saving files in this directory.
However when I open the camera, the permission popup appears asking for external storage.
I think the culprit is in CameraPermissions.kt - allPermissions list contains write_external_storage permission and it is never removed.
Maybe asking for this permission could be made optional?
The text was updated successfully, but these errors were encountered:
krzysztof-swi
changed the title
android.permission.WRITE_EXTERNAL_STORAGE
android.permission.WRITE_EXTERNAL_STORAGE is not always required
Apr 19, 2023
You are right. I tried to delete the part of the code that contains the write_external_storage permission, so it will no longer request this permission. The reason why the demo does not request permission is because this permission is not registered in the AndroidManifest. After registration, it will still request this permission.
Hi,
This task concerns only Android version:
My app has defined write_external_storage permission in AndroidManifest.xml, as I need it in other place:
I use camereawesome for taking pictures, I save them inside application directories, using path_provider.getTemporaryDirectory.
This permission is not required for saving files in this directory.
However when I open the camera, the permission popup appears asking for external storage.
I think the culprit is in CameraPermissions.kt - allPermissions list contains write_external_storage permission and it is never removed.
Maybe asking for this permission could be made optional?
The text was updated successfully, but these errors were encountered: