[ 
https://issues.apache.org/jira/browse/CB-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Filip Maj resolved CB-912.
--------------------------

       Resolution: Fixed
    Fix Version/s: 1.9.0

This is not so much an issue with the framework as an issue with the way this 
API is being used.

I have added tests for this case to the cordova-js repo and added sanity 
parameter checking to the FileTransfer methods. If non-truthy values are passed 
into the source/target parameters for upload and download, FileTransfer will 
throw an exception now.

This commit is 
[8d2562|https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-js.git;a=commit;h=8d25620f18e47deb0da95606848fe46e7743df07].
                
> FileTransfer.download does not fire error callback when server is unavailable
> -----------------------------------------------------------------------------
>
>                 Key: CB-912
>                 URL: https://issues.apache.org/jira/browse/CB-912
>             Project: Apache Cordova
>          Issue Type: Bug
>    Affects Versions: 1.8.0
>         Environment: Android/iOS
> Others untested
>            Reporter: Dewang Shah
>            Assignee: Filip Maj
>             Fix For: 1.9.0
>
>         Attachments: cb-915-repro.tar.gz
>
>
> The download method on FileTransfer never fires the error callback if there 
> is a network connection but the download URL is not accessible. It simply 
> waits forever and does not return.
> Reproduction:
>         var fileTransfer = new FileTransfer();
>         fileTransfer.download('http://nosuchserver/nosuchfile.png', fullPath, 
> function(entry) {
>             console.log("download complete: " + entry.fullPath);
>         }, function(error) {
>             console.log("download error source " + error.source);
>             console.log("download error target " + error.target);
>             console.log("download error code" + error.code);
>         });

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