jschillingApollo commented on issue #263:
URL: 
https://github.com/apache/cordova-plugin-media-capture/issues/263#issuecomment-1480145941

   @vesper8 No solution yet unfortunately. We ended up removing video capture 
functionality from the Android version of our application temporarily while we 
look for a better option because this plugin is not going to work for us in its 
broken state.
   
   As far as accessing the video file on Android its pretty straightforward. 
Its the same for iOS or Android for us and we are able to upload videos just 
fine. Its just where the media-capture plugin stores them that's the problem. 
They can still be accessed the same way iOS videos are accessed using the file 
plugin and getting a FileEntry object from the file path.
   
   The 
[docs](https://github.com/apache/cordova-plugin-media-capture#capturecapturevideo)
 give a decent overview of how the `.captureVideo()` function works and what 
parameters it accepts. This function returns a Promise of type MediaFile[] 
(don't forget to import MediaFile from the media-capture plugin) so you'll need 
a way to extract that information from the Promise (i.e. `.then` or 
`async/await`). Then you just loop through the array and collect the paths to 
each captured video file using the `.fullPath` attribute. On iOS you will 
likely need to replace the start of the fullPath string from '/private' to 
'file://' but on Android you shouldn't need to change that. The process for 
accessing/reading the file for upload should be the same for either platform 
and we use the awesome-cordova-plugins-file plugin for that.


-- 
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