Hello BTers, I keep getting a "build fail" while running the iPhone sim. MAC-O linker error-command failed exit code 1. I deleted the entire project twice, thinking I might have dragged duplicate files into the project. Did a project clean, loaded a new project into Xcode and carefully dragged and dropped images, docs, plugins, sound & video folders into project. Made certain I didn't drag another project folder into Xcode and verified the radio button in the dialogue window was selected for, "create groups for any added folders". Clicked "finish" and then selected iPhone sim and "build fail" AGAIN! Cleaned project and still error. Some advice to proceed would help. Thank you.

It probably help you to take a look at the 'Debug' tutorial Chris1 cooked up. https://www.buzztouch.com/files/howtos/exception%20debugging%20how-to.pdf Also, Mark (GNW) did an earlier tutorial on Troublshooting basics. https://www.buzztouch.com/files/howtos/Problem_Reporting_and_Basic_Debug_v1.0.pdf https://www.buzztouch.com/files/howtos/Common_Apple_Errors_and_Solutions_v1.0.pdf Hope this helps! Cheers! -- Smug

Thank you, Smug. I'm updating my simulator downloads for Xcode to see if this helps, too.

Screen shot of error: http://i.imgur.com/TXaufja.jpg I seem to have 23 duplicates, if so, how do I get rid of them?

I had this same problem recently. I was able to solve it by downloading the code again. I "think" what happened was that I dragged one of the folders into Xcode when it was already there, thus duplicating the files. Might be something to check out. Mark

Well, I keep getting the same error. Even after I have blown out project file in finder to make sure the project was deleted from Xcode. Then I compiled another app file in the builder, downloaded, installed into Xcode again, carefully dragging folders in. It keeps saying I have 23 duplicated symbols in architecture i386. Clang error: linker command failed with exit code 1 (use -v to see invocation)

what about duplicate images? SDKs? It could be complaining about 'any' duplicate resource... find one of the offending statements, copy the file/resource name, and do a search in your project to see what it might be... Cheers! -- Smug

Where in the heck can I clean out the below duplicates? This was copied from the error report. duplicate symbol _OBJC_IVAR_$_BT_rssParser.xmlItemDescriptionName in: /Users/glennsmith/Library/Developer/Xcode/DerivedData/flyfishingutah-cyqmawcdgkdlmjczeupjitrjizxr/Build/Intermediates/flyfishingutah.build/Debug-iphonesimulator/flyfishingutah.build/Objects-normal/i386/BT_rssParser.o

Ah. hmm. Go to your Mac 'Finder', and up in the menu, select "Go To Folder" (shift + command + G) When the box pops up, type "~/Users/glennsmith/Library/Developer/Xcode/DerivedData" and feel free to delete those files/directories, specifically the "flyfishingXXXXXX" directories (while Xcode is NOT running). I guess that's the project you're working on. When you run the simulator, that is where all the temp files go. In theory, when you 'clean' your project, it should wipe that out, but I've seen odd cases where you just had to delete it manually. Maybe this is also one of them. Running an App in the simulator will generate a new set of temp files. Good Luck, let us know what transpires! Cheers! -- Smug

I have this problem sometimes. It happens when the RD RSS and BTM RSS are included in the same file. If you are not using the RSS plugin, I would delete it and your problem will be solved. Which Xcode are you using? (4.6.3?) Jake

+1 for Jake ... I have experienced the same thing. Remove one of your RSS reader plugins and things start to work better. I didn't get the Macho-o-link error but still had issues. I think they have duplicate method names from memory.

Done! It worked, Thank you Jake and ictguy! Appreciate the ongoing support here!

Ah. I don't use those. I would have never thought of that. Good on ya, Jake :) Cheers! -- Smug

I agree with ICTGuy: I think that the RD RSS was based off of BTM RSS which was based off of BT RSS and all of these use the same class names. I am glad the issue was resolved. Jake

Thank you again, everyone!