nsexception

Why doesn't @try block work? It crashed the app, but it was supposed to be caught by the @try block. NSString* test = [NSString stringWithString:@"ss"]; @try { [test characterAtIndex:6]; } @catch (NSException * e) { NSLog(@"Exception: %@", e); } @finally { NSLog(@"finally"); } All work perfectly :) NSString *test = @"test"; unichar a; int index = 5; @try { a = [test characterAtIndex:index]; } @catch (NSException *exception) { NSLog(@"%@", exception.reason); NSLog(@"Char at index %d cannot be found", index); NSLog(@"Max index is: %lu", [test length] - 1); } @finally { NSLog(@"Finally condition"

My application crashes when clicking a button to go to segue into a new view. This comes up: int main(int argc, char * argv[]) { @autoreleasepool { return UIApplicationMain(argc, argv, nil, NSStringFromClass([AppDelegate class])); } } "return UIApplicationMain..." is highlighted in green with "Thread 1: Signal SIGABRT" at the end. The error also includes this in the output: **Terminating app due to uncaught exception *** 'NSUnknownKeyException reason:'[<SlopeViewController 0x8b68c70> setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key m.' *** First throw call

This question already has an answer here: Xcode - How to fix 'NSUnknownKeyException', reason: … this class is not key value coding-compliant for the key X" error? 66 answers Terminating app due to uncaught exception 'NSUnknownKeyException', reason: '[ setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key buttonOfFirstView.' Why do I get this error? I am trying to make a table cell though XIB. After I add this code it throws the above exception. - (UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath{ static NSString

One of my friends asked me not to use NSException in iPhone Apps. The reason he gave was "performance bottleneck". But I am not convinced of it. Can someone confirm me that we should restrain from using NSException in iPhone App? If you have best practices for using NSException, please provide that too. UPDATE: This link requests us to use Exception handling at the app level. Have someone ever done it? Please give the advantages of it and any other performance hitches it could create. In short: Do not use exceptions to indicate anything but unrecoverable errors It is only appropriate to use

Every time my app crashes Xcode highlights the UIApicationMain() call in the main() function as the line that caused the crash. In some cases that used to be normal (segmentation fault for example) but the crash I am trying to deal with is a simple SIGABRT with detailed information logged in the console: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFDictionary setObject:forKey:]: attempt to insert nil value (key: Date)' Xcode used to show the line just right with older SDKs but since i upgraded to Xocde 4.2 that changed. It is pretty obvious that

The following code in Swift raises NSInvalidArgumentException exception: task = NSTask() task.launchPath = "/SomeWrongPath" task.launch() How can I catch the exception? As I understand, try/catch in Swift is for errors thrown within Swift, not for NSExceptions raised from objects like NSTask (which I guess is written in ObjC). I'm new to Swift so may be I'm missing something obvious... Edit : here's a radar for the bug (specifically for NSTask): openradar.appspot.com/22837476 freytag Here is some code, that converts NSExceptions to Swift 2 errors. Now you can use do { try ObjC.catchException {