cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Grieve (JIRA)" <>
Subject [jira] [Commented] (CB-2183) [iOS] FileTransfer.didReceiveResponse may not return NSHTTPURLResponse
Date Mon, 14 Jan 2013 15:14:13 GMT


Andrew Grieve commented on CB-2183:

That's great! Supporting Blobs & ArrayBuffers is actually being worked on right now (likely
to be included in the 2.4).

It would be great if we could get you as a tester for it. Would you be willing?

What I'm wondering is:
-What platforms your developing for,
-Exactly which APIs you'd like to use and how (e.g. give code snippets of how you use FileReader/FileWriter/Blob/ArrayBuffer/XHR2)
-Would you be willing to test these features as they get added into the development version

We'll still fix this bug in FileTransfer.
> [iOS] FileTransfer.didReceiveResponse may not return NSHTTPURLResponse
> ----------------------------------------------------------------------
>                 Key: CB-2183
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 2.2.0
>         Environment: Tested on iOS 5.1 and 6.0
>            Reporter: William Wong
>            Assignee: Shazron Abdullah
>            Priority: Minor
>              Labels: File, FileTransfer
>             Fix For: 2.4.0
> When is downloading a file from file:///, NSURLConnection did
not return with NSHTTPURLResponse. This will fail for apps that copy files from www/, e.g.
apps that initialize its database from a pre-built cache packaged in IPA.
> In CB-1600 (fixed in 2.2.0), the fix assumes all response must be NSHTTPURLResponse.
So when is downloading from a file:/// URL (e.g. copying file from
www/ folder to Documents/), FileTransfer assumed the download operation failed and returned
> Tested if we comment out CB-1600, downloading from file:/// works again.
> We need to find out a better fix instead of commenting out CB-1600.
> According to,
URL of file:/// is supported.
> You can test by calling it with "encodeURI(document.location.href)"
as the "source" parameter.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message