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

Jacob G edited comment on CB-6428 at 3/17/15 12:28 AM:
-------------------------------------------------------

That's exactly the error I'm getting also when downloading to directory 
(cordova.file.dataDirectory + 'wwwTmp/'). I have to dig into this further to 
find the bug.


was (Author: jacobgu):
That's exactly the error I'm getting also when downloading to directory 
(cordova.file.dataDirectory + 'wwwTmp/'), which is of course resolved to an 
valid DirectoryEntry using getDirectory. I have to dig into this further to 
find the bug.

> Unable to read android_asset directory through File API
> -------------------------------------------------------
>
>                 Key: CB-6428
>                 URL: https://issues.apache.org/jira/browse/CB-6428
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Plugin File
>    Affects Versions: 3.3.0
>         Environment: Android 4.4.2 / Samsung Galaxy S4
>            Reporter: Matt Grande
>            Assignee: Andrew Grieve
>              Labels: android, file
>
> Attempting to read the 'android_asset' folder through the File API results in 
> Error Code 5 (FileError.ENCODING_ERR). I've tried accessing via 
> resolveLocalFileSystemURL, and by creating a directory reader and calling 
> readEntries().
>     
> window.resolveLocalFileSystemURL('file:///android_asset/www/my_asset_folder', 
> success, fail);
>     var sourceDir = new DirectoryEntry( { fullPath: 
> 'file:///android_asset/www/my_asset_folder' } );
>     var reader = sourceDir.createReader();
>     reader.readEntries(success, fail);
> (I have also tried with the URLs being '/android_asset/www/my_asset_folder'; 
> same result)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to