Nsxmlparser Error 65
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 My NSXMLParser is not parsing and returning null up vote 0 down vote favorite 1 I was parsing my xml in some other view controller's button click but now i have changed it to the app delegate class (My app is a Universal app). so that as soon as i start my app is should parse all.My parsing methods are written in another ViewController and i am calling those methods from my appDelegate class, but it is returning me this :- NSXMLParser ERROR: The operation couldn’t be completed. (NSXMLParserErrorDomain error 65.) - (null) dont know what i have done now. any help will be appreciable. iphone objective-c ios ios4 nsxmlparser share|improve this question asked Nov 17 '11 at 5:19 mAc 1,71611030 Could you post your XML data so we can look. –Parag Bafna Nov 17 '11 at 6:42 Yes i found the answer parag... actually it is a Domain error.... not in my code.. that's y i haven't given my code. Actually we have bought a new server machine so are proxies are now gone... but in my network i was still linked with proxies, so it was giving me error (NSXMLParserErrorDomain.... Well Thanks for your reply and time. –mAc Nov 17 '11 at 7:05 add a comment| 2 Answers 2 active oldest votes up vote 0 down vote accepted Actually as it is a Domain error... it is not on your side. you must check your internet or Proxy settings. i hope you internet must be working on simulator but not in your app.... :) Try it. share|improve this answer answered Nov
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 http://stackoverflow.com/questions/8162477/my-nsxmlparser-is-not-parsing-and-returning-null 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 error trying to parse NSData using NSXMLParser delegates up vote 0 down vote favorite I have http://stackoverflow.com/questions/16704245/error-trying-to-parse-nsdata-using-nsxmlparser-delegates some xml that contains a BASE 64 ENCODED PNG IMAGE I am trying to parse this into an object of some type.. for the moment into a NSArray of NSDictionaries, however I am currently unsuccessful doing so. This is part of my parse delegate: - (void)parser:(NSXMLParser *)parser didStartElement:(NSString *)elementName namespaceURI:(NSString *)namespaceURI qualifiedName:(NSString *)qName attributes:(NSDictionary *)attributeDict { if([elementName isEqualToString:@"GUI"]){ parsedGUIMutableDictionary = [[NSMutableDictionary alloc] initWithDictionary:attributeDict]; } } - (void)parser:(NSXMLParser *)parser didEndElement:(NSString *)elementName namespaceURI:(NSString *)namespaceURI qualifiedName:(NSString *)qName { if ([elementName isEqualToString:@"GUI"]) { [parsedDataArrayOfDictionaries addObject:parsedGUIMutableDictionary]; } } Once this is done there are no values saved into the dictionary so it's just empty... I have added a breakpoint in both if statements and when the first if statement is entered attributeDict is empty. This is what the xml looks like:
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 https://ios.forums.wordpress.org/topic/understanding-nsxmlparsererrordomain-error-messages 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 https://github.com/OpenClemson/SwiftECP/issues/5 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 nsxmlparser error 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 nsxmlparser error 65 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, NSXMLParserIn
Sign in Pricing Blog Support Search GitHub This repository Watch 18 Star 9 Fork 0 OpenClemson/SwiftECP Code Issues 6 Pull requests 1 Projects 0 Pulse Graphs New issue Handle incorrect password #5 Open nawatts opened this Issue Mar 11, 2016 · 3 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 1 participant Open Clemson Software member nawatts commented Mar 11, 2016 When attempting to authenticate with an incorrect password, sendIdpRequest fails with: 2016-03-11 17:13:44.120 [Debug] [ECP.swift:67] sendIdpRequest > Error Domain=NSXMLParserErrorDomain Code=65 "(null)" UserInfo={ NSXMLParserErrorColumn=50, NSXMLParserErrorLineNumber=1, NSXMLParserErrorMessage=Space required after the Public Identifier } The operation couldn’t be completed. (NSXMLParserErrorDomain error 65.) It seems AEXML does not parse the response from the IDP in Alamofire+ReactiveCocoa's XMLResponseSerializer. The response from the IDP is:
Authorization Required
This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.
Apache/2.2.15 (Oracle) Server at idp.clemson.edu Port 443 It seems like the 401 response (assuming the IDP is actually sending 401 as the status code) should be caught and returned as an error with a user friendly message. nawatts added a commit that referenced this issue Mar 14, 2016 nawatts