Nsxmlparser Error Code 9
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up iPhone NSXMLParser (Error 9) up vote 3 down vote favorite 1 i try to parse within my iPhone SDK 4 http://de.news.search.yahoo.com/news/rss?p=iphone&ei=UTF-8&fl=0&x=wrt there are some german umlaute
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each http://stackoverflow.com/questions/3352027/iphone-nsxmlparser-error-9 other. Join them; it only takes a minute: Sign up ASIHTTPClasses and iOS6 up vote 0 down vote favorite My app has been working correctly on previous iOS versions. I just upgraded to iOS6 and now the app is returning an error while processing an XML request/response. The app sends an XML request to a server and receives http://stackoverflow.com/questions/12524384/asihttpclasses-and-ios6 an XML response, but now the response is empty "<>" causing the NSXMLParser to fail. Here is how the app is sending the request (this used to work, prior ios6): [request setURL:[NSURL URLWithString:url]]; [request setHTTPMethod:@"POST"]; [request setValue:postLength forHTTPHeaderField:@"Content-Length"]; [request setValue:@"text/xml" forHTTPHeaderField:@"Content-Type"]; //[request setValue:@"application/x-www-form-urlencoded charset=utf-8" forHTTPHeaderField:@"Content-Type"]; [request setHTTPBody:postData]; NSURLConnection *conn=[[NSURLConnection alloc] initWithRequest:request delegate:self]; if (conn) { receivedData = [[NSMutableData data] retain]; } But the response is now empty "<>". parser error is Error Domain=NSXMLParserErrorDomain Code=9 "The operation couldn’t be completed. (NSXMLParserErrorDomain error 9.)", path to file is : /Users/ronluna/Library/Application Support/iPhone Simulator/6.0/Applications/5BA74D89-1967-4B9E-A1C0-B076F7BB9064/Documents/Menus.xml Any ideas what could be the problem? ios6 nsxmlparsererrordomain share|improve this question edited Sep 25 '12 at 4:20 Brad Werth 11.2k63357 asked Sep 21 '12 at 4:43 ronluna 43 add a comment| 2 Answers 2 active oldest votes up vote 0 down vote Hi ive also encountered the same problem. Try changing the format of your xml file to UTF-8 without BOM or if you are populating your xml on a server side script try changing the character set to UTF-8. Hop
error messages jb6262 Moderator Aug 31, 2009, 8:01 PM I've been doing some work recently working to make the WP iPhone app a bit more user-friendly when it comes https://ios.forums.wordpress.org/topic/understanding-nsxmlparsererrordomain-error-messages to error messages and adding a blog for the first time. This has resulted in several fixes are available in the 2.0 version. One will give you the ability to enter your xmlrpc endpoint manually if it can't be found by the app. Another catches HTML errors and presents them for a clearer understanding of what's going on. However, it will nsxmlparser error always be possible to get NSXMLParserErrorDomain errors (especially from a self-hosted blog) because they refer to errors in the parsing of the XML returned from the blog. Themes or custom php code that results in malformed XML are the common causes. Even if the iPhone application is going to ignore the specific "component" the parsing can break if XML is malformed. nsxmlparser error code In the 1.3 version, these errors can occur because the server HTML error message was processed by the XML Parser. This is fixed in 2.0. Once you're using WP for iPhone 2.0 or later, the error should be a hint about the way in which XML is malformed. A good test is to remove custom code or turn off themes and then try to connect again. In order to understand these errors, I've provided a link for you techies to the Apple web page which documents them. For those of you who just want to know the meaning of the message, please look for the number in the list below and read the associated (terse) description further down the page. This list is a copy from the Apple page, and therefore is subject to any changes made by Apple since it was posted. Here is the link . Here is the list from the link as of this post's date: Parser Error Constants The following error types are defined by NSXMLParser. typedef enum { NSXMLParserInternalError = 1, NSXMLParserOutOfMemoryError = 2, NSXMLParserDocumentStartError