views:

57

answers:

0

I recently migrated an iPhone project from the 2.2.1 SDK to 3.1.x and, to my surprise, an XML feed that was (and still is with the published app) being parsed by the 2.2.1 NSXMLParser is now causing NSXMLParser to return errors.

The XML document in question doesn't meet the W3C standard, but the 2.2.1 parser is able to handle this. I'm curious if anyone knows what changed and, more importantly, if there's a way to "relax" the 3.1.x parser. I don't have much control over the XML document, unfortunately, so I might have to get creative if I can't rely on the NSXMLParser to handle things as it did before.