Parse Error on iPhone: NSXMLParserPrematureDocumentEndError

Question

Level 1

2 points

Parse Error on iPhone: NSXMLParserPrematureDocumentEndError

I have an app which fetches/parses XML and I keep getting a parse error at random. The parse error has an error code of 5, which corresponds to NSXMLParserPrematureDocumentEndError. This seems to be the error for when the device doesn't have a connection and tries to fetch a URL... except sometimes I get it even when the device Does have a connection. It happens more often on Edge, but can happen anytime.

Does anyone have an idea as to what the problem might be? Or a possible solution? I can't find any evidence of other people having this problem, which leads me to believe I'm doing something wrong :P. I based my XML code off of Seismic.

Mike O.

Posted on Aug 11, 2008 3:27 AM

Reply

Answer 1

Top-ranking reply

ourwebstop

Level 1

11 points

Oct 23, 2008 3:40 PM in response to ikon_zero

I had similar problems when I initialized the parser with a URL.
To debug that (and see what it was trying to parse), I fetched the XML as part of a NSURLRequest and then calling [NSURLConnection sendSynchronousRequest, then initializing the parser with the returned data like this: [[NSXMLParser alloc] initWithData:receivedData];

If the parsing still gives me an error, slip that data into an NSString before calling parse so I can take a look at it.

I haven't had those errors since changing it to fetch the xml first, then initialize a parser with the data rather than initializing the parser with initwithContentsOfURL.

Brian

Reply

Answer 2

petecj

Level 1

0 points

Oct 23, 2008 9:52 AM in response to Dan Haligas

I am getting this as well - seems to happen with and without WiFi on. I have used the same thing in other applications and don't see the issue. I am scrounging for suggestions.....

Reply

Answer 3

Sep 17, 2008 8:33 PM in response to ikon_zero

Did you ever figure out how to fix this? I too get it when I have an xml document stored locally and the wifi connection is off. Once I turn it on I get no issues???

Reply