Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

iOS Build a Simple iPhone App with Swift Improving Our User Interface Adding a Pop of Color

Sara Grim
Sara Grim
5,285 Points
Posted by Sara Grim
Sara Grim
5,285 Points

What do I do with the yellow warning called "thread 1: signal SIGABRT" after running the Fun Facts App?

Is there something wrong with my code here on the last step of making the Fun Facts app? @UIApplicationMain class AppDelegate: UIResponder, UIApplicationDelegate {

var window: UIWindow?


func application(application: UIApplication!, didFinishLaunchingWithOptions launchOptions: NSDictionary!) -> Bool {

    application.setStatusBarStyle(UIStatusBarStyle.LightContent, animated: false)
    // Override point for customization after application launch.
    return true
}

2 Answers

Stone Preston
Stone Preston
42,016 Points
Stone Preston
Stone Preston
42,016 Points

seeing thread 1: signal SIGABRT usually means you have an uncaught exception being thrown. look in the console. there should be more information about what is causing the exception. can you post what you find in the console (you may have to scroll around some)

Sara Grim
Sara Grim
5,285 Points
Sara Grim
Sara Grim
5,285 Points

Yes, here it is. SwiftFunFacts[24625:1139482] -[__NSCFBoolean length]: unrecognized selector sent to instance 0x1023443f0 (lldb)

Stone Preston
Stone Preston
42,016 Points
Stone Preston
Stone Preston
42,016 Points

select Debug -> Breakpoints -> add exception breakpoint. then run your code. it should break on the line thats throwing the exception. post the code that it breaks on.