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 Playlist Browser with Swift Using a Navigation Controller With Segues Passing Information Between Views

Posted by sirong hua
sirong hua
219 Points

error message: Thread 1: signal SIGABRT in class AppDelegate

this error message keeps on showing. Someone knows what is the cause? Thanks!

Fredrik Skjelvik
Fredrik Skjelvik
4,955 Points
Fredrik Skjelvik
Fredrik Skjelvik
4,955 Points

I am also having this problem and i have no clue what to do :(

3 Answers

agreatdaytocode
agreatdaytocode
24,757 Points

You have a lingering connection to a no-longer-existent outlet. Double check this via the main storyboard file.

sirong hua
sirong hua
219 Points

Thanks! That's wonderfully clear and helpful answer!

agreatdaytocode
agreatdaytocode
24,757 Points

Glad to help!

kaitlanlang
kaitlanlang
3,042 Points

I am getting this same message from xcode. I cant see any lingering one. I have made certain I removed the one connection as described in the video. I have an iboutlet left behind but thats for the 'press me' and was left behind in video. Pulling my hair out. Thread 1: signal SIGABRT is not meaning anything to me. im stuck

agreatdaytocode
agreatdaytocode
24,757 Points
agreatdaytocode
agreatdaytocode
24,757 Points

Hello Kaitlan,

Did you right click the button on the storyboard to see if you add any outlets that are not being used?

kaitlanlang
kaitlanlang
3,042 Points
kaitlanlang
kaitlanlang
3,042 Points

Hi Aaron, I did. Even did that 'clean' thing. Couldn't solve it. Whatever happened it was either me or an Xcode glitch. I just decided to start a new project and do it all again. When I got to point where I had problem first time around it never reappeared. So never resolved it but got around it by starting all over. Thanks for reply :)

agreatdaytocode
agreatdaytocode
24,757 Points

I'm happy to hear you worked it out. I'm Sorry that we did not figure out what the issue was.