breautek commented on PR #889: URL: https://github.com/apache/cordova-plugin-camera/pull/889#issuecomment-2426554002
> plugin-media-capture has an open issue with a PR removing the permissions and plugin-camera is here doing the same, right? I haven't really kept a close eye on media-capture plugin so I don't know if it's "in-sync" with what the camera plugin is doing. I know there was previous proposals to make the media-capture plugin copy the assets from the content:// store to the app's internal temp directory to avoid permission problems or requiring the `READ_MEDIA_*` permissions but I think that fell through. This isn't so much a problem for images, but for videos copying the files can be an expensive and lengthy process too. With the Content FS changes in file plugin (which is currently in the release process and I'm hoping to make a release this week if I can get enough binding votes) it will give the app developers a choice of immediate playback directly from `content://` or if they need more persistent access they can choose to copy themselves, depending on the application use cases & needs. I'm not sure if the media-capture plugin has any PR that just simply exposes the content:// path, but that is likely where we want to go for it. -- 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: issues-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
