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 Self-Destructing Message iPhone App Using Parse.com as a Backend and Adding Users Creating an Account and App on Parse.com

Creating and Account and App on Parse: Build failed with no explanation?

Hi,

Any help will be appreciated. I am having trouble with the Creating and Account and App on Parse.com section of the self destructing app track. I have downloaded and included all the frameworks needed as Ben said to do, including the parse framework. I have followed both Ben and Parse's instructions with the code. However every time I try and run the app I see that the build has failed and am presented with 4 error messages!

"OBJC_CLASS$_BFExecutor", referenced from:

"OBJC_CLASS$_BFTask", referenced from:

"OBJC_CLASS$_BFTaskCompletionSource", referenced from:

clang: error: linker command failed with exit code 1 (use -v to see invocation)

^^ Have just copied and pasted from Xcode. Please can someone explain why this is happening and outline what steps can be taken to rectify the problem.

Many thanks

1 Answer

Francisco Navarro
Francisco Navarro
14,185 Points

Hi! I think this question is already answered in other post in this forum! Take a look at Parse.com as it seems now instructions added are required!

Here the post: https://teamtreehouse.com/forum/did-you-get-4-errors-when-you-added-in-the-parse-library1-to-you-code-urgent

Thanks a lot Francisco, I should have looked at the Teacher Notes. Problem resolved