[
https://issues.apache.org/jira/browse/CB-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623717#comment-13623717
]
Ian Clelland edited comment on CB-2840 at 4/5/13 3:36 PM:
----------------------------------------------------------
A first quick test with the simulator, using NLC (100% packet loss in both
directions) results in the error callback being called with the message "File
Transfer Error: The request timed out.". No crash; the app keeps running.
I'll see what I can get out of a real device.
was (Author: iclelland):
A first quick test with the simulator, using NLC (100% packet loss in both
directions) results in the error callback being called with the message "File
Transfer Error: The request timed out.". No crash; the app keeps running.
> crash when disabling network connection during file download
> ------------------------------------------------------------
>
> Key: CB-2840
> URL: https://issues.apache.org/jira/browse/CB-2840
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
> Affects Versions: 2.5.0
> Environment: all iOS Versions
> Reporter: Dominik Binz
> Assignee: Ian Clelland
> Labels: patch
>
> When disabling network connection during file download the app crashes to
> home screen with the following error:
> 2013-03-28 01:49:24.515 Cordova250[4255:907] -[CDVFileTransfer download:]
> [Line 350] File Transfer downloading file...
> 2013-03-28 01:49:38.440 Cordova250[4255:907] *** Terminating app due to
> uncaught exception 'NSInvalidArgumentException', reason: '***
> setObjectForKey: object cannot be nil (key: body)'
> *** First throw call stack:
> (0x345443e7 0x3c23f963 0x344a65ef 0xa30b5 0xa49b5 0x34e80915 0x34dc0769
> 0x34e80aeb 0x3422170b 0x34220d33 0x34249013 0x3448aacd 0x34249473 0x341ad461
> 0x345198f7 0x345191f3 0x34517f2f 0x3448b23d 0x3448b0c9 0x3806a33b 0x363a72b9
> 0x6d06f 0x6d030)
> libc++abi.dylib: terminate called throwing an exception
> (lldb)
--
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: http://www.atlassian.com/software/jira
