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 Views and View Controllers View Controllers and IBAction

Matt Sikorski
Matt Sikorski
2,402 Points

When I click on the button my app crashes and goes to code "class AppDelegate: UIResponder, UIApplicationDelegate "

It goes to this line of code and has an error message that says Thread 1: signal SIGARBT"

3 Answers

Jon Uland
Jon Uland
1,880 Points

Hey Matt Sikorski I think I figured out what was wrong. When I went through the challenge, I accidentally added the function as an outlet first, and having duplicate roles for the same function was blowing everything up.

Here's how I fixed it:

Navigate to the "Connection Inspector" inside the Utilities pane (circle icon with an arrow in it). Look at your "Sent Events." If you notice you have two referencing the same function, that's probably your problem.

I don't know why the problem happens. Perhaps someone with more understanding and time could enlighten us. Thanks!

Sam Chaudry
Sam Chaudry
25,519 Points

Check your outlets on your storyboard are all connected. An app can build fine but if it isn't connected then it can cause an error like this. Also check that your optionals are being unwrapped properly sometimes a nil value with a force unwrap with a bang can cause the app to stall out and crash.

Sam Chaudry
Sam Chaudry
25,519 Points

Check your outlets on your storyboard are all connected. An app can build fine but if it isn't connected then it can cause an error like this. Also check that your optionals are being unwrapped properly sometimes a nil value with a force unwrap with a bang can cause the app to stall out and crash.