Note that there are some explanatory texts on larger screens.

plurals
  1. PONSXMLParser stops right after it starts
    primarykey
    data
    text
    <p>Im practicing RESTKit, and so I'm building a Dribbble client to get the hang of REST, i get the XML response successfully, but when i use NSXMLParser to parse it, it logs start, then stop immediately after, how can i fix it, or just make it easier with the XML to sort out which item is which, and put it into my table then?</p> <p>heres the code: </p> <pre><code>-(void)parser:(NSXMLParser *)parser didStartElement:(NSString *)elementName namespaceURI:(NSString *)namespaceURI qualifiedName:(NSString *)qName attributes:(NSDictionary *)attributeDict { NSLog(@"I just found a start tag for %@",elementName); } - (void)parser:(NSXMLParser *)parser foundCharacters:(NSString *)string{ NSLog(@"the parser just found this text in a tag:%@",string); } -(void)parserDidStartDocument:(NSXMLParser *)parser { NSLog(@"starting"); } -(void)parserDidEndDocument:(NSXMLParser *)parser { NSLog(@"end"); } -(IBAction)test { [[RKClient sharedClient] get:@"/shots/popular" delegate:self]; } -(void)request:(RKRequest *)request didLoadResponse:(RKResponse *)response { if ([request isGET]) { NSLog(@"Retrieved XML: %@", [response bodyAsString]); NSXMLParser *xmlParser = [[NSXMLParser alloc] initWithData:[response body]]; [xmlParser setDelegate:self]; [xmlParser parse]; } else if ([request isPOST]) { if ([response isJSON]) { NSLog(@"Got a JSON response back from our POST!"); } } else if ([request isDELETE]) { if ([response isNotFound]) { NSLog(@"The resource path '%@' was not found.", [request resourcePath]); } } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload