[ 
https://issues.apache.org/jira/browse/CB-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285905#comment-13285905
 ] 

Simon MacDonald commented on CB-837:
------------------------------------

When Fil dropped the common JS into the Android repo all fullPath's had to 
start with the file:// protocol or it would just fail horribly. I'm surprised 
the same did not happen for you.

This is actually beneficial on the Android side as now mediaFile.fullPath can 
be passed to window.resolveLocalFileSystemURI() to get a FileEntry object. 
Pretty much every other API on the Android side returns a URL as a full path to 
any file.
                
> CaptureCB - mediaFile.fullPath does not resolve to file
> -------------------------------------------------------
>
>                 Key: CB-837
>                 URL: https://issues.apache.org/jira/browse/CB-837
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CordovaJS
>    Affects Versions: 1.7.0
>         Environment: Tested on iOS
>            Reporter: Dimitri Adamou
>            Assignee: Filip Maj
>            Priority: Minor
>
> Hey there,
> Simply put here is an example
> navigator.device.capture.captureAudio(successCB, error, {limit: 1});
> function successCB(mediaFile) {
>    
>    window.resolveLocalFileSystemURI(mediaFile[0].fullPath, gotFileEntry, 
> fsFail);
> }
> function fsFail(error) {
>    alert('we failed with code ' + error.code); //5
> }
> The issue is mediaFile[0].fullPath lacks file://localhost being prepended. Is 
> this intentional?
> Simple work around is just to add it in using
> var path = mediaFile[0].fullPath
> if(path.indexOf("file://localhost") == -1) path = "file://localhost" + path;

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to