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 Wed, 30 Apr 2014 02:34:17 GMT


ASF subversion and git services commented on CB-6525:

Commit 4435819f6356e14602a4173d32e08576be473eca in cordova-plugin-file's branch refs/heads/master
from [~agrieve]
[;h=4435819 ]

CB-6525 android, ios: Allow file: URLs in all APIs. Fixes not being

Root problem of downlaod was that the target URL was not being properly
resolved to an Entry on the native side. This wasn't caught by
mobilespec due to the requestFileSystem() using cdvfile: URLs still,
while resolveLocalFileSystemURL(entry.toURL()), would yield a file: URL.

This commit normalizes fs.root DirectoryEntries so that they are file://
as well, and initializes them on start-up with a new "getAllFileSystems"
exec() call.

It also aims to ensure that JSON entries always have nativeURL set.

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