detecting timeout with NSURLConnection

chuck · 09-13-2010, 06:45 AM

I want to detect a timeout, but every time my app reaches the line to check for it, it crashes whether there was an error or not. Am I fundamentally not understanding how NSError works? Should I be implementing NSURLConnection with a delegate instead?

I've looked into this for several hours and can't make any headway and I'm pretty sure I'm just going about it in completely the wrong way. Any help in moving in the right direction would be greatly appreciated. Thanks in advance!

Code:

NSError *error;

NSURLRequest *ccRequest =
[NSURLRequest requestWithURL:[NSURL
                              URLWithString:[self createUrl]]
                 cachePolicy:NSURLRequestUseProtocolCachePolicy
             timeoutInterval:60.0];

NSURLResponse* response;

NSData* myData = [NSURLConnection sendSynchronousRequest:ccRequest 
                                       returningResponse:&response
                                                   error:&error];

// 1001 is the error code for a connection timeout
// It CRASHES below when it tries to determine the error code.
if ( error && [error code] == 1001 ) {
    NSLog( @"Server timeout!" );
}

chuck · 09-13-2010, 08:47 AM

I just changed the first line to:

Code:

NSError *error = nil;

and the bottom part to:

Code:

if ( error != nil && [error code] == 1001 ) {

When I look at the Debugger, it also doesn't have any information. Any other ideas?

chuck · 09-13-2010, 09:10 AM

Also tried:

Code:

f ( myData == nil && [error code] == 1001 ) {

Same crash.

**smithdale87** · 09-13-2010, 09:16 AM

Quote:

When I look at the Debugger, it also doesn't have any information. Any other ideas?

Have you tried running a backtrace in the d ebugger?

chuck · 09-13-2010, 09:46 AM

Quote:

Originally Posted by smithdale87

Have you tried running a backtrace in the d ebugger?

How do you run a backtrace? When I load the debugger after the crash, there is nothing in it.

**smithdale87** · 09-13-2010, 09:57 AM

When the app crashes, and you open the debugger, type the word "backtrace" or just "bt" and it should spit out some more info about the crash

chuck · 09-14-2010, 04:15 AM

Quote:

Originally Posted by smithdale87

When the app crashes, and you open the debugger, type the word "backtrace" or just "bt" and it should spit out some more info about the crash

Weird. That does absolutely nothing. Anything, I've since learned that synchronous NSURLConnection is buggy and I should use asynchronous instead. Anyway, thanks for the tip! I'm sure it will come in handy on future projects.