cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CB-6525) download success callback not called in 0.4.3
Date Fri, 20 Jun 2014 06:41:26 GMT


ASF subversion and git services commented on CB-6525:

Commit 4f455ac3efe64caede6cbaff9d7c638caf6e5392 in cordova-plugin-file's branch refs/heads/master
from [~martin.c.glez.glez]
[;h=4f455ac ]

CB-6980 Fixing filesystem:null property in Entry

when resolveLocalFileSystemURI or resolveLocalFileSystemURL is called on
the File Plugin under Windows Phone 8, on success it should return a
Entry with several properties, as it is the filesystem information,
which returns as null.
on resolveLocalFileSystemURI.js it calls fileSystem.getFS the object
retrieved it should contain the filesystem information.
Since the fix, CB-6525, only adds support for Android and iOS, for other
platform it retrieves a null object, so adding a condition to retrieve
the information if the object from the callback is null.

> download success callback not called in 0.4.3
> ---------------------------------------------
>                 Key: CB-6525
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Plugin File Transfer
>    Affects Versions: 3.4.0
>         Environment: Cordova 3.4.1
> iOS
> 0.4.3 of the file transfer plugin
>            Reporter: AH
>            Assignee: Andrew Grieve
> I've noticed that the success callback doesn't get executed after a download is successfully
completed. Specifically, if success contains a console.log, nothing is logged to the Xcode
debugger even though the download has completed successfully. I can tell that the download
was completed because the following message is logged in Xcode: "File Transfer Finished with
response code 200"
>, localPath, success, error);
> I think this is an issue with version 0.4.3 of the file transfer plugin. Version 0.4.2
of the plugin running on Cordova 3.4.1 didn't have this bug. 
> I found another possible report of this bug:

This message was sent by Atlassian JIRA

View raw message