incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shazron Abdullah (JIRA)" <>
Subject [jira] [Commented] (CB-864) Writing large file blocks Cordova
Date Tue, 05 Jun 2012 18:00:23 GMT


Shazron Abdullah commented on CB-864:

Tracing the execute call here:

When it errors, it should print out some logs, see:

Does it print out any of the NSLogs in your console log?

Your issues:
1. This is a general NSLog, usually the commands are small. We could add a filter for string
length and truncate it.
2. We could only print this in Debug configuration (use DLog from CDVDebug.h)
3. This is in a general handler, and no callback is called. Will have to investigate if its
possible here to callback to the error handler, it shouldn't be a problem though.
> Writing large file blocks Cordova
> ---------------------------------
>                 Key: CB-864
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 1.7.0
>         Environment: Reproduced on two environments - iOS version: 5.1 (272.21) simulator
(on OS X 10.7.3) AND iOS version: 5.1.1. 
> Cordova 1.7.0 
>            Reporter: Mikael Andersson
>            Assignee: Shazron Abdullah
>             Fix For: 1.9.0
> The write method never returns/throws when trying to write a ~3 MB file. After write
is called, a message is logged: "FAILED pluginJSON = { "className": "File", "methodName":
"write" ... and then the contents of the file!
> After the writing the file to the log, the following is written: "void SendDelegateMessage(NSInvocation*):
delegate (webView:decidePolicyForNavigationAction:request:frame:decisionListener:) failed
to return after waiting 10 seconds. main run loop mode: kCFRunLoopDefaultMode"
> There are multiple issues: 
>  1. The file should not be written to the log. 
>  2. I have not found any way to inhibit logging (which could have been a workaround).
>  3. The call must return or throw.

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


View raw message