Has NSXMLParser become more strict in iPhone SDK 3.x?
Posted
by D Carney
on Stack Overflow
See other posts from Stack Overflow
or by D Carney
Published on 2010-06-16T01:56:05Z
Indexed on
2010/06/16
2:02 UTC
Read the original article
Hit count: 263
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.
© Stack Overflow or respective owner