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

Ios

What is a thread when it comes to the app delegate portion of Xcode?

3 Answers

From apple's Threaded Programming Guide:

Threads are a relatively lightweight way to implement multiple paths of execution inside of an application. At the system level, programs run side by side, with the system doling out execution time to each program based on its needs and the needs of other programs. Inside each program, however, exists one or more threads of execution, which can be used to perform different tasks simultaneously or in a nearly simultaneous manner. The system itself actually manages these threads of execution, scheduling them to run on the available cores and preemptively interrupting them as needed to allow other threads to run.

Did your app crash and throw an exception or something? if so can you post whats logged in the console?

Thank you for your help. I was doing the crystal ball app and when i go to animate the app, there are no errors shown but when it compiles it states at the bottom of the screen: terminating with uncaught exception of type NSException. Then it takes me to the app delegate page and highlights this in green: return UIApplicationMain(argc, argv, nil, NSStringFromClass([AppDelegate class])); and it says thread 1: signal SIGABRT. Im not sure what this all means or what i did wrong. Thank you again for your help!

What else does it say about the exception? There should be some more info in the console log about the exception after it mentions the termination. You may have to scroll down

No there was no information after the NSException, thank you for your help though