-
Notifications
You must be signed in to change notification settings - Fork 761
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
feat(android): Make permission WRITE_EXTERNAL_STORAGE optional #543
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Also, just confirmed that
https://developer.android.com/reference/android/Manifest.permission#WRITE_EXTERNAL_STORAGE Therefore rather than making the permission optional, we'll probably just remove it altogether. Additionally, the plugin already is set to support only cordova engines android >= 10.0, which is intended to target API 30, so removing the WRITE declaration completely would not be considered a breaking change. |
I am currently targeting API level 31 and I am using my fork where I have removed the permission tag from the plugin.xml. I can confirm that there are no issues so far while using the plugin without the permission, as its use was very specific either way (with sd cards only?). Can we expect the permission to be removed in the next release of this plugin? |
Yes, but I cannot provide a timeline of when that will be. |
Feature Request
Motivation Behind Feature
Most applications and plugin functionalities do not require "android.permission.WRITE_EXTERNAL_STORAGE".
Feature Description
Adding a variable during installation whether or not to include the permission might be the simplest solution. I'm not exactly sure if the cordova xml structure supports something like checking if a preference is equal to a value and then adding a permission or any other tag.
Alternatives or Workarounds
A workaround for completely removing the permission is mentioned here: #243
I'm also using a fork in my projects where the permission is removed directly from the plugin.xml.
The text was updated successfully, but these errors were encountered: