Thread 1: Signal SIGABRT” at the end.

Ok, so I think this "Thread 1: Signal SIGABRT" isn't the indicator to find out what is causing the error with the code. Most likely you'll need to scroll all the way up to get the comments from the compiler that will give you more clues as to what is wrong with the code.

For me, it turned out that my segue identifier was not named "showLogin" as it was supposed to, so as soon as i fixed this, the code succeeded.

I think I made the error of thinking that the "Thread 1: Signal SIGABRT" is in itself a universal error code for something specific

Thread 1: Signal SIGABRT” at the end.

I get same error, even using Xcode 8.1 same issue: 2016-12-01 10:57:52.455 Algorythm2[1253:86383] -[UIButton setText:]: unrecognized selector sent to instance 0x7ffbc3c063e0 2016-12-01 10:57:52.458 Algorythm2[1253:86383] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[UIButton setText:]: unrecognized selector sent to instance 0x7ffbc3c063e0' *** First throw call stack: ( 0 CoreFoundation 0x0000000107a4234b exceptionPreprocess + 171 1 libobjc.A.dylib 0x00000001074a321e objc_exception_throw + 48 2 CoreFoundation 0x0000000107ab1f34 -[NSObject(NSObject) doesNotRecognizeSelector:] + 132 3 CoreFoundation 0x00000001079c7c15 ___forwarding_ + 1013 4 CoreFoundation 0x00000001079c7798 CF_forwarding_prep_0 + 120 5 Algorythm2 0x0000000106ece56f -[PlaylistDetailViewController viewDidLoad] + 143 6 UIKit 0x0000000108006c99 -[UIViewController loadViewIfRequired] + 1258 7 UIKit 0x000000010800d102 -[UIViewController __viewWillAppear:] + 118 8 UIKit 0x0000000108037fbf -[UINavigationController _startCustomTransition:] + 1290 9 UIKit 0x0000000108048c34 -[UINavigationController _startDeferredTransitionIfNeeded:] + 697 10 UIKit 0x0000000108049dc7 -[UINavigationController __viewWillLayoutSubviews] + 58 11 UIKit 0x0000000108240d6f -[UILayoutContainerView layoutSubviews] + 223 12 UIKit 0x0000000107f29f50 -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 1237 13 QuartzCore 0x000000010c6a5cc4 -[CALayer layoutSublayers] + 146 14 QuartzCore 0x000000010c699788 _ZN2CA5Layer16layout_if_neededEPNS_11TransactionE + 366 15 QuartzCore 0x000000010c699606 _ZN2CA5Layer28layout_and_display_if_neededEPNS_11TransactionE + 24 16 QuartzCore 0x000000010c627680 _ZN2CA7Context18commit_transactionEPNS_11TransactionE + 280 17 QuartzCore 0x000000010c654767 _ZN2CA11Transaction6commitEv + 475 18 QuartzCore 0x000000010c6550d7 _ZN2CA11Transaction17observer_callbackEP19CFRunLoopObservermPv + 113 19 CoreFoundation 0x00000001079e6e17 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION_ + 23 20 CoreFoundation 0x00000001079e6d87 __CFRunLoopDoObservers + 391 21 CoreFoundation 0x00000001079cbb9e __CFRunLoopRun + 1198 22 CoreFoundation 0x00000001079cb494 CFRunLoopRunSpecific + 420 23 GraphicsServices 0x000000010b7a4a6f GSEventRunModal + 161 24 UIKit 0x0000000107e65964 UIApplicationMain + 159 25 Algorythm2 0x0000000106ece9cf main + 111 26 libdyld.dylib 0x000000010a82268d start + 1 27 ??? 0x0000000000000001 0x0 + 1 ) libc++abi.dylib: terminating with uncaught exception of type NSException (lldb)

/* Any ideas, especially from TeamTreeHouse experts welcome */

Guys please watch this, you'll feel like such an idiot :D https://www.youtube.com/watch?v=MkcqBIS8Swc a -/+10 year old kid solves this problem. I could kill myself...

Hi Juan,

can you please post the full error message. Have you already tried to clean your project? (SHIFT + CMD + A or 'Menue --> Product --> Clean')

Did you made the App yourself by following along with the tutorial or did you download one of the partially completed versions? (I'm asking because of the Xcode Version/Deployment Target)

Kind Regards Holger

I followed the tutorial Holger, also i just found the solution:

I have fixed this issue by following below steps:

Renaming "MainStoryboard.storyboard" to "MainStoryboard_1.storyboard" Click on main app file. "Info" tab. Edit "Main storyboard file base name" to "MainStoryboard_1.storyboard". Rerun the app, and it worked for me. I renamed my storyboard file back to its original "MainStoryboard.storyboard". Rerun the app,

and it worked. weird, huh!?

Good to hear you where able to solve your problem, Juan :)

...and by the way I'm looking forward to version 5.1 where everything is going to be just perfect (or may be it's just my positive thinking) :-)

solved the problem :)

@bohyeon an how did you solve this problem? I'm getting the same error, even if I changed the name of the mainstoryboard file.

2015-12-22 18:32:59.891 BlogReader[2367:79306] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Could not find a storyboard named 'MainStoryboard' in bundle NSBundle </Users/rmchallinor/Library/Developer/CoreSimulator/Devices/D9AB9888-B88E-4619-889F-5AFDDEB0BFED/data/Containers/Bundle/Application/EB886762-F265-4821-BE6A-0641BF435875/BlogReader.app> (loaded)' *** First throw call stack: ( 0 CoreFoundation 0x0000000110095e65 exceptionPreprocess + 165 1 libobjc.A.dylib 0x000000010fb0edeb objc_exception_throw + 48 2 UIKit 0x000000010e677669 -[UIStoryboard name] + 0 3 UIKit 0x000000010df52f82 -[UIApplication _loadMainStoryboardFileNamed:bundle:] + 58 4 UIKit 0x000000010df532d6 -[UIApplication _loadMainInterfaceFile] + 260 5 UIKit 0x000000010df51b54 -[UIApplication _runWithMainScene:transitionContext:completion:] + 1390 6 UIKit 0x000000010df4ee7b -[UIApplication workspaceDidEndTransaction:] + 188 7 FrontBoardServices 0x00000001105b8754 -[FBSSerialQueue _performNext] + 192 8 FrontBoardServices 0x00000001105b8ac2 -[FBSSerialQueue _performNextFromRunLoopSource] + 45 9 CoreFoundation 0x000000010ffc1a31 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 17 10 CoreFoundation 0x000000010ffb795c __CFRunLoopDoSources0 + 556 11 CoreFoundation 0x000000010ffb6e13 __CFRunLoopRun + 867 12 CoreFoundation 0x000000010ffb6828 CFRunLoopRunSpecific + 488 13 UIKit 0x000000010df4e7cd -[UIApplication _run] + 402 14 UIKit 0x000000010df53610 UIApplicationMain + 171 15 BlogReader 0x000000010dea192f main + 111 16 libdyld.dylib 0x000000011462592d start + 1 ) libc++abi.dylib: terminating with uncaught exception of type NSException

that is what i got and it is not loading up in the simulator please help

I was receiving the same error and was able to fix it. What was happening to me was that I had inconsistent names for an IBOutlet between the connections inspector via the main storyboard, and the IBOutlet in the ViewController.

@saphomaqhwazima is absolutely correct DO watch the video. Its really a simple little loophole! https://www.youtube.com/watch?v=MkcqBIS8Swc

well, I dont have any problem with a name of mainstoryboard but I got same message as her.. I cant figure it out. Please let me know how to solve this problem. I can`t just go to next stage.