XCode 7 iOS 9 produces 'Thread 1: signal SIGABRT' error in main.m

Question

When I run my app, it produces the Thread 1: signal SIGBART error message with the detail below:

TappingGame[767:9324] *** Terminating app due to uncaught exception 'NSUnknownKeyException', reason: '[<ViewController 0x7fe5d0f12130> setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key tapButton.'
*** First throw call stack:
 (
0   CoreFoundation                      0x000000010b07ee65 __exceptionPreprocess + 165
1   libobjc.A.dylib                     0x000000010aaf7deb objc_exception_throw + 48
2   CoreFoundation                      0x000000010b07eaa9 -[NSException raise] + 9
3   Foundation                          0x000000010a6c49bb -[NSObject(NSKeyValueCoding) setValue:forKey:] + 288
4   UIKit                               0x000000010b5ba320 -[UIViewController setValue:forKey:] + 88
5   UIKit                               0x000000010b7e8f41 -[UIRuntimeOutletConnection connect] + 109
6   CoreFoundation                      0x000000010afbf4a0 -[NSArray makeObjectsPerformSelector:] + 224
7   UIKit                               0x000000010b7e7924 -[UINib instantiateWithOwner:options:] + 1864
8   UIKit                               0x000000010b5c0eea -[UIViewController _loadViewFromNibNamed:bundle:] + 381
9   UIKit                               0x000000010b5c1816 -[UIViewController loadView] + 178
10  UIKit                               0x000000010b5c1b74 -[UIViewController loadViewIfRequired] + 138
11  UIKit                               0x000000010b5c22e7 -[UIViewController view] + 27
12  UIKit                               0x000000010b498ab0 -[UIWindow addRootViewControllerViewIfPossible] + 61
13  UIKit                               0x000000010b499199 -[UIWindow _setHidden:forced:] + 282
14  UIKit                               0x000000010b4aac2e -[UIWindow makeKeyAndVisible] + 42
15  UIKit                               0x000000010b423663 -[UIApplication _callInitializationDelegatesForMainScene:transitionContext:] + 4131
16  UIKit                               0x000000010b429cc6 -[UIApplication _runWithMainScene:transitionContext:completion:] + 1760
17  UIKit                               0x000000010b426e7b -[UIApplication workspaceDidEndTransaction:] + 188
18  FrontBoardServices                  0x000000010ddf7754 -[FBSSerialQueue _performNext] + 192
19  FrontBoardServices                  0x000000010ddf7ac2 -[FBSSerialQueue _performNextFromRunLoopSource] + 45
20  CoreFoundation                      0x000000010afaaa31 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
21  CoreFoundation                      0x000000010afa095c __CFRunLoopDoSources0 + 556
22  CoreFoundation                      0x000000010af9fe13 __CFRunLoopRun + 867
23  CoreFoundation                      0x000000010af9f828 CFRunLoopRunSpecific + 488
24  UIKit                               0x000000010b4267cd -[UIApplication _run] + 402
25  UIKit                               0x000000010b42b610 UIApplicationMain + 171
26  TappingGame                         0x000000010a5f89ef main + 111
27  libdyld.dylib                       0x000000010d7ba92d start + 1
)
libc++abi.dylib: terminating with uncaught exception of type NSException
(lldb)

I have looked at other questions asked but none of these solutions work. Does anyone have any idea from the errors listed as to why it isn't working?

Thanks

The most significant information is: `this class is not key value coding-compliant for the key tapButton`. Find out what `tapButton` does. It looks like a broken connection to an `IBOutlet` at runtime. — vadian, Dec 16 '15 at 19:38
It depends. KVC errors could have several reasons. The error message assumes there is no key `tapButton` — vadian, Dec 16 '15 at 19:48
Would there be any piece of information that would help identify the problem? — peterbonar, Dec 16 '15 at 19:49
As mentioned in my first comment look for the key in the class and check its functionality. It could be a simple typo for example/ — vadian, Dec 16 '15 at 19:51

score 1 · Answer 1 · answered Dec 16 '15 at 19:40

1

The problem described in your error is due to a incorrect linked class in your storyboard or nib.

answered Dec 16 '15 at 19:40

bipsa

351
2
8

score 1 · Answer 2 · answered Dec 16 '15 at 19:51

1

You have an incorrect link. Probably you delete or changed name.

Check if your IBOutlet are correct link as image:

and remove invalid links.

answered Dec 16 '15 at 19:51

Haroldo Gondim

7,725
9
43
62

XCode 7 iOS 9 produces 'Thread 1: signal SIGABRT' error in main.m

2 Answers2