Nsxmlparser Error Code 512
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 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 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. 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 = 3, NSXMLParserEmptyDocumentError = 4, NSXMLParserPrematureDocumentEndError = 5, NSXMLParserInvalidHexCharacterRefError = 6, NSXMLParserInvalidDecimalCharacterRefError = 7, NSXMLParserInvalidCharacterRefError = 8, NSXMLParserInvalidCharacterError = 9, NSXMLParserCharacterRefAtEOFError = 10, NSXMLParserCharacterRefInPrologError = 11, NSXMLParserCharacterRefInEpilogError = 12, NSXMLParserCharacterRefInDTDError = 13, NSXMLParserEntityRefAtEOFError = 14, NSXMLParserEntityRefInPrologError = 15, NSXMLParserEntityRefInEpilogError = 16, NSXMLParserEntityRefInDTDError = 17, NSXMLParserParsedEntityRefAtEOFError = 18, NSXMLParserParsedEntityRefInPrologError = 19, NSXMLParserParsedEntityRefInEpil
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 https://ios.forums.wordpress.org/topic/understanding-nsxmlparsererrordomain-error-messages programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Better illustrating error message for NSXMLParser up vote 1 down vote favorite Now the user only get a error message like "Error code 5". NSString *errorString = [NSString stringWithFormat:@"Error code %i", [parseError code]]; UIAlertView *errorAlert = [[UIAlertView alloc] initWithTitle:@"Error loading http://stackoverflow.com/questions/3583702/better-illustrating-error-message-for-nsxmlparser content" message:errorString delegate:self cancelButtonTitle:@"OK" otherButtonTitles:nil]; [errorAlert show]; So the NSXMLParserError code is not enough for me. I rather would like something like "NSXMLParserPrematureDocumentEndError" or "The document ended unexpectedly." Is there an easy way to do this? Cheers iphone objective-c xcode nsxmlparser share|improve this question asked Aug 27 '10 at 11:31 testing 5,5322096207 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote Check NSError's localizedDescription, localizedFailureReason etc etc methods in NSError class reference NSString *errorString = [parserError localizedDescription]; share|improve this answer answered Aug 27 '10 at 12:18 lukya 7,88612249 I've tried localizedDescription & Co before, but wasn't successful. I didn't get errorWithDomain:code:userInfo: working. localizedDescription shows "The operation couldn’t be completed. (NSXMLParserErrorDomain error 512." localizedFailureReason shows "null". So no method left? –testing Aug 27 '10 at 12:32 well if you can list down all the errors from the NSXMLParserErrorDomain which you specifically want to describe to the user, you can write a switch case comparing those
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 http://stackoverflow.com/questions/6177978/ios-xml-parsing-error-domain-nsxmlparsererrordomain-code-76-on-some-devices 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 https://developer.apple.com/reference/foundation/xmlparser minute: Sign up ios XML parsing : Error Domain=NSXMLParserErrorDomain Code=76 on some devices up vote 2 down vote favorite I get this error in my app on one specific iPhone 4 device while parsing an XML Feed: error parsing XML: Error nsxmlparser error Domain=NSXMLParserErrorDomain Code=76 I am not able to determine why it's happening on this particular device and not others: this is the same feed. There are no XML errors in the feed XML structure and all devices have the same global general settings. According to the docs, Error 76 is NSXMLParserTagNameMismatchError. iphone ios nsxmlparser nsxmlparsererrordomain share|improve this question edited May 30 '11 at 15:28 Matthew Crumley 68k1976113 asked May 30 '11 at 15:11 Nico AD 73231237 add a comment| 3 Answers 3 active oldest nsxmlparser error code votes up vote 2 down vote Your xml may be inconsistent. Validate it against http://validator.w3.org/#validate_by_input share|improve this answer answered May 30 '11 at 15:35 Praveen S 8,96123462 no, the problem only oocurs on one device. after some tests, it seems related to the 3G connection quality. the problem does not occurs on the same device with Wifi. –Nico AD Jun 1 '11 at 7:50 So you may be getting partial document. –Praveen S Jun 1 '11 at 7:57 add a comment| up vote 2 down vote Cut and paste your xml here to validate. The error messages are pretty solid. share|improve this answer answered Jul 13 '12 at 14:23 Eric Brotto 26k1690152 add a comment| up vote 2 down vote this error happens when the closing tag doesn't match the opening tag, like so: or
(including DTD declarations) in an event-driven manner. An NSXMLParser notifies its delegate about the items (elements, attributes, CDATA blocks, comments, and so on) that it encounters as it processes an XML document. It does not itself do anything with those parsed items except report them. It also reports parsing errors. For convenience, an NSXMLParser object in the following descriptions is sometimes referred to as a parser object. Unless used in a callback, the NSXMLParser is a thread-safe class as long as any given instance is only used in one thread.LanguageSwiftObjective-CSDKsiOS 8.0+macOS 10.10+tvOS 9.0+watchOS 2.0+On This PageOverviewNested TypesSymbolsRelationshipsOverviewNoteNamespace support was implemented in NSXMLParser for OS X v10.4. Namespace-related methods of NSXMLParser prior to this version have no effect.Nested TypesNSXMLParserErrorThe following error codes are defined by NSXMLParser. For error codes not listed here, see the