Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3405092
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 18, 20262026-05-18T05:27:47+00:00 2026-05-18T05:27:47+00:00

I am new to iPhone/Objective-C development, I am successfully parsing XML with NSXMLParser but

  • 0

I am new to iPhone/Objective-C development, I am successfully parsing XML with NSXMLParser but I can’t get exceptions to work properly. I’d like to use exceptions to deal with unexpected XML.

I’m wrapping the code for creating the NSXMLParser object and sending the setDelegate and parse messages to the object inside a @try @catch block, catching @NSException.

If I put NSAssert(FALSE, @"error) inside the @try block, the exception is caught properly. If, however, I have an NSAssert fail inside the delegate calls (eg, didStartElement, didEndElement, foundCharacters), then the program dies (in iPhone Simulator, haven’t tried device yet). The debugger stack trace shows the assertion was raised into an exception but it doesn’t pull back out into the top level code where the @try block is around the [parser parse] message call. Instead I get “Terminating app due to uncaught exception.”

Please let me know if this is a known problem or if I’m doing something silly here.

Thanks — Alex

Some code to make more concrete; no attempt to make this code correct for memory/releases/etc.

@implementation XMLTester

+(void)runXMLTester
{
    BOOL success = FALSE;
    XMLTester *tester = [[XMLTester alloc] init];
    NSData *data = [NSData dataWithContentsOfURL:[NSURL URLWithString:@"http://api.wunderground.com/auto/wui/geo/WXCurrentObXML/index.xml?query=KSFO"]];
    NSXMLParser *parser = [[NSXMLParser alloc] initWithData:data];
    [parser setDelegate:tester];
    @try {
        //NSAssert(FALSE, @"error"); // this assertion works fine
        success = [parser parse];
    }
    @catch (NSException * e) {
        success = FALSE;
        NSLog(@"Exception caught %@: %@", [e name], [e reason]);
    }
    @finally {
        NSLog(@"runXMLTester @finally block hit");
    }
}

- (void)parser:(NSXMLParser *)parser didStartElement:(NSString *)elementName namespaceURI:(NSString *)namespaceURI qualifiedName:(NSString *)qualifiedName attributes:(NSDictionary *)attributeDict
{
    NSLog(@"Starting element %@", elementName);
    NSAssert(FALSE, @"error"); // this assertion does not work - does not hit @try block around parse message
}
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-18T05:27:47+00:00Added an answer on May 18, 2026 at 5:27 am

    According to Bill Bumgarner, catching exceptions in the iPhone Simulator doesn’t work correctly. Your best bet is to stop using exceptions here, as it’s not really appropriate anyway. You should be calling -[NSXMLParser abortParsing] instead.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

The thing is I'm new on iPhone and Objective C development and I'd like
I'm new to Objective-C and iPhone development, and I'm trying to store floating-point values
I'm new to iPhone/Objective-C development. I jumped the gun and started reading and implementing
I'm new to iPhone development, so apologies if this is a silly question, but
I am new to Objective C and iPhone development. I am using CoreData on
I'm pretty new to iPhone development and I'm still getting my head around Objective-C,
i'm new here, i'm new in iphone development, i'm new in Objective-c and i'm
I am relatively new to Objective C/iPhone Development. I am developing a simple app
I'm new to iPhone development and Objective-C. Using the ZBar SDK I've developed a
I'm kinda new to Objective-C and iPhone development and I've come across a problem

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.