breautek commented on issue #1626:
URL: 
https://github.com/apache/cordova-android/issues/1626#issuecomment-1673132585

   > my app currently is push notification and file permission.
   > 
   > due to file permission, we move to this plugin 
https://github.com/customautosys/cordova-plugin-saf-mediastore for file storage 
at the moment, this will not required any file permission.
   > 
   > push notification have to add permission in the manifest file via 
config.xml 
https://developer.android.com/develop/ui/views/notifications/notification-permission#declare
   
   For some permissions, declaring them in the manifest is enough to have the 
permission grant. Other permissions may require an explicit permission grant 
from the user. It depends on the severity level of permissions. It's not 
cordova-android's responsibility for making these permission requests. It's up 
to the plugin to handle checking and requesting permissions if necessary.
   
   > my app currently is push notification and file permission.
   
   If by file permission you mean `READ_EXTERNAL_STORAGE` and/or 
`WRITE_EXTERNAL_STORAGE`, on API 33 devices requesting these permissions 
results in an auto rejection of the permission grant. So you wouldn't see a 
prompt. These permissions are completely obsolete on API 33 and later and 
replaced by 3 other permissions. For API 32 and earler, `READ_EXTERNAL_STORAGE` 
was still used. Again it's up to the plugin to manage requesting the 
appropriate permission based on API level.
   
   > due to file permission, we move to this plugin 
https://github.com/customautosys/cordova-plugin-saf-mediastore for file storage 
at the moment, this will not required any file permission.
   
   If you're using external storage (either emulated or sdcard) then this is a 
good move that I would have recommended. Not endorsing the specific plugin, but 
any plugin that uses the MediaStore API rather than File-based APIs. The scoped 
storage mechanism that is enforced since API 29 makes it very difficult to use 
external storage from a "File API" standpoint. I made a PR against the Apache 
File plugin that expands the docs regarding those issues: 
https://github.com/apache/cordova-plugin-file/pull/593
   
   It doesn't sound like what you have reported is a bug with cordova-android, 
but perhaps a bug with a particular plugin. If you were using the file plugin 
with the external storage, then there are also a lot of other issues not 
necessarily related to API 33 or the permissions, which is why moving to a 
MediaStore plugin is probably the best move for interacting with Android's 
external filesystem.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to