Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Date: Mon, 12 Mar 2012 21:44:40 +0000 (UTC)
From: "Shazron Abdullah (Updated) (JIRA)" <jira@apache.org>
To: callback-dev@incubator.apache.org
Message-ID: 
 <1487114119.4872.1331588680281.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1766013313.28368.1331056978879.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CB-300) CDVFileTransfer crashes with 303 and
 empty response
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CB-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shazron Abdullah updated CB-300:
--------------------------------

    Priority: Critical  (was: Major)
     Summary: CDVFileTransfer crashes with 303 and empty response  (was: PGFileTransfer crashes with 303 and empty response)
    
> CDVFileTransfer crashes with 303 and empty response
> ---------------------------------------------------
>
>                 Key: CB-300
>                 URL: https://issues.apache.org/jira/browse/CB-300
>             Project: Apache Callback
>          Issue Type: Bug
>          Components: iOS
>            Reporter: Shazron Abdullah
>            Assignee: Shazron Abdullah
>            Priority: Critical
>             Fix For: 1.6.0
>
>
> reported by: https://github.com/mckamey
> at: https://github.com/cordova/cordova-ios/issues/3
> It appears that when PhoneGap FileTransfer receives a 303 HTTP status code with an empty response body from the remote server, the component crashes with an NSInvalidArgumentException.
> Not sure if any of this console dump is helpful...
> 2012-01-09 12:37:31.638 XYZ[12677:707] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFDictionary setObject:forKey:]: attempt to insert nil value (key: response)'
> *** First throw call stack:
> (0x342618bf 0x344b11e5 0x342617b9 0x342617db 0x341ce6bb 0x1a195 0x35c6dc39 0x35bc56e9 0x35bc56b3 0x35bc55d5 0x322738a5 0x32268545 0x32268243 0x32268179 0x34235b03 0x342352cf 0x34234075 0x341b74dd 0x341b73a5 0x30a3bfcd 0x37638743 0x2cd3 0x2c8c)
> terminate called throwing an exception

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira