iPhone JSON object releasing itself?

Question

I'm using the JSON Framework addon for iPhone's Objective-C to catch a JSON object that's an array of Dictionary-style objects via HTTP. Here's my connectionDidFinishLoading function:

- (void)connectionDidFinishLoading:(NSURLConnection *)connection {
   [connection release];
 NSString *responseString = [[NSString alloc] initWithData:responseData encoding:NSUTF8StringEncoding];
 [loadingIndicator stopAnimating];

 NSArray *responseArray = [responseString JSONValue]; // Grab the JSON array of dictionaries
 NSLog(@"Response Array: %@", responseArray);
 if ([responseArray respondsToSelector:@selector(count)]) {
  NSLog(@"Returned %@ items", [responseArray count]);
 }
 [responseArray release];
 [responseString release];
}

The issue is that the code is throwing a EXC_BAD_ACCESS error on the second NSLog line. The EXC_BAD_ACCESS error I think indicates that the variable got released from memory, but the first NSLog command works just fine (and shows that the data is all there); it seems that only when calling the count message is causing the error, but the respondsToSelector call at least thinks that the responseArray should be able to respond to that message. When running with the debugger, it crashes on that second line, but the stack shows that the responseArray object is still defined, and has 12 objects in it (so the debugger at least is able to get an accurate count of the contents of that variable).

Is this a problem with the JSON framework's creation of that NSArray, or is there something wrong with my code?

Answer 1

count returns an NSUInteger, not an object. Per the Apple Documentation you should use %lu and cast to unsigned long in this case instead to display it:

NSLog(@"Returned %lu items", (unsigned long)[responseArray count]);

With %@, NSLog() tries to interpret the value as a pointer to an object and to send a description message to it.
It is highly unlikely that there is accidentally a valid object at that memory location, so the code is bound to fail badly or show unpredictable results.

Answer 2

Simple typo: Your format string in the second NSLog contains an %@ instead of %d.

Answer 3

In addition to what gf and Nikilai said, [responseArray release]; over releases

If those guys got their method naming right, NSArray *responseArray = [responseString JSONValue]; returns an autoreleased instance.