cordova-dev mailing list archives

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


William Wong commented on CB-2183:

Andrew, in my case, files downloaded from file:///.../www/ could be binaries (e.g. PNGs).
It would be great if we can use standard FileSystem APIs.

To obsolete FileTransfer and use standard HTML5 File APIs, PhoneGap will need to implement
few things around HTML5 Blob:
- HTTP (via XHR) -> file:///
  - Sends Blob downloaded by XHR to native
  - FYI, ArrayBuffer ( may give
you some hints how to convert Blob <-> DOM String, but looks like it won't be an efficient
- file:///.../Documents -> HTTP (via XHR)
  - (*) Implements FileReader.readAsArrayBuffer(Blob), or ask the user to use Data URI and
convert to Blob (
- file:///.../www/ -> file:///.../Documents
  - Implements (*)
  - Implements FileWriter.write(Blob), currently PhoneGap only support FileWriter.write(utf8)

If the bridge can handle Blob objects, and implement FileWriter.write(Blob) correctly, we
should be able to obsolete 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