PDA

View Full Version : A 3.2.5 Project on Xcode 4 SIGBART error




JamerTheProgram
Aug 29, 2012, 10:02 AM
Hey guys!
I have this iOS iPhone project made in Xcode 3.2.5 for iOS 4.2 and Im trying to run it in Xcode 4 but it spits out this error:
2012-08-29 15:58:58.634 app1[1544:c07] *** Terminating app due to uncaught exception 'NSUnknownKeyException', reason: '[<UIApplication 0x6a1fcf0> setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key view.'
*** First throw call stack:
(0x18a8022 0x127ccd6 0x18a7ee1 0xd2022 0x43f6b 0x43edb 0x5ed50 0x5a471a 0x18a9dea 0x18137f1 0x5a326e 0x5a4eb7 0x381ce1 0x381ff8 0x38117f 0x390183 0x390c38 0x384634 0x1d9aef5 0x187c195 0x17e0ff2 0x17df8da 0x17ded84 0x17dec9b 0x380c65 0x382626 0x1d1d 0x1c95)
terminate called throwing an exception(lldb)
Any idea what this means?



Reason077
Aug 29, 2012, 10:48 AM
Try setting XCode to break at the point the exception is thrown.

See: http://blog.manbolo.com/2012/01/23/xcode-tips-1-break-on-exceptions

JamerTheProgram
Aug 29, 2012, 12:04 PM
Try setting XCode to break at the point the exception is thrown.

See: http://blog.manbolo.com/2012/01/23/xcode-tips-1-break-on-exceptions

This is where it breaks:

#import <UIKit/UIKit.h>

int main(int argc, char *argv[]) {

NSAutoreleasePool * pool = [[NSAutoreleasePool alloc] init];
int retVal = UIApplicationMain(argc, argv, nil, nil);
[pool release];
return retVal;
}

Every other thing is assembly.
Any ideas?

phantax
Aug 29, 2012, 02:35 PM
That is where the exception is caught, not where the actual exception is occurring in your code, which isn't very useful, and without more information it is pretty difficult to say what is happening in your project.

Did you actually read the link posted about adjusting the breakpoint for exceptions, or just dismiss it?

JamerTheProgram
Aug 29, 2012, 03:19 PM
I did read the article you sent me. The advice given in that article doesnt seem to be working for me. It just shows a bunch of stuff in assembly. The only bit in OBJc is the main.m.

phantax
Aug 29, 2012, 03:29 PM
You added a NEW breakpoint to break On Throw of ALL Exceptions and it still breaks in the same place?

The only other thing I can suggest is to go through your NIBs if you are using them and look for broken outlets and actions, that seems to be the most common cause for this error.

Since its coming from UIApplication and not a view controller, do you have any outlets or connections going to your App Delegate?

PhoneyDeveloper
Aug 29, 2012, 04:51 PM
You have a nib that is not set up correctly. The error says that it is trying to connect an IBOutlet named "view" to a UIApplication object. Obviously it's supposed to be connecting the view to a UIViewController.

Inspect all the connections in your nib til you find the problem.