Linker command failed with exit code 1 error in Xcode project

Question

I was working on my project and suddenly after editing the code and compiling gave this error:

ld: warning: directory not found for option '-
L/Users/mani/Documents/Classes/Twitter+OAuth/Libraries & Headers' ld: duplicate symbol _OBJC_CLASS_$_playSiew in /Users/mani/Library/Developer/Xcode/DerivedData/learn-aktrtiwswclovoatyweyquoxmypa/Build/Intermediates/learn.build/Debug-iphonesimulator/learn.build/Objects-normal/i386/playSiew.o and /Users/mani/Library/Developer/Xcode/DerivedData/learn-aktrtiwswclovoatyweyquoxmypa/Build/Intermediates/learn.build/Debug-iphonesimulator/learn.build/Objects-normal/i386/Thumb.o for architecture i386 clang: error: linker command failed with exit code 1 (use -v to see invocation)

I never touched the project settings, just edited the code.

What's more strange is that I took out last revised code from svn but still I got the the same error.

There may be some ivars which you have declared in your playSiew.m file and with the same name you have declared in another .m file.May be this helps you cause i have also faced this duplicate symebol error and it did the trick for me — superGokuN
– superGokuN, Commented May 30, 2012 at 6:36
but why I am facing this error now? I never had this problem before and it suddenly appeared? — user1374408
– user1374408, Commented May 30, 2012 at 6:40
Check you import statement, seems like you have imported two library which has same named symbol — TeaCupApp
– TeaCupApp, Commented May 30, 2012 at 6:47
I think u have changed the code from the location.so that refference is not there i think that is causing the problem — hacker
– hacker, Commented May 30, 2012 at 12:26
Similar issue, I found stackoverflow.com/questions/33499570/xcode-duplicate-symbol — Phoenix Haroz
– Phoenix Haroz, Commented Nov 4, 2015 at 7:29

CodaFi · Accepted Answer · 2012-05-30 06:49:18Z

26

You may be accidentally #import'ing a .m file instead of a .h. Use Cmd+Shift+F and search for ".m" (without quotes). It will most likely lie in one of the classes mentioned in the warning. If not, clean and run again.

answered May 30, 2012 at 6:49

CodaFi

43.5k8 gold badges110 silver badges154 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

user1374408 Over a year ago

as I said....the previous revised code in svn is also not working...so definately its not a problem with code. Moreover the same code in which I am facing problem is running fine on my team member's mac

Elsa Over a year ago

actually searching for .m" (with the ending quote) might help to find it faster

Brian Tompsett - 汤莱恩 · Accepted Answer · 2015-07-01 09:25:18Z

22

I was also having same issue and I did following and issue is gone.

Go to Product -> Clean and re-run the project.

I hope it might be useful for some other developers.

edited Jul 1, 2015 at 9:25

Brian Tompsett - 汤莱恩

5,92772 gold badges63 silver badges135 bronze badges

answered Jul 1, 2015 at 8:59

Narendra Ojha

6939 silver badges18 bronze badges

1 Comment

user462990 Over a year ago

I found the same thing. Always a good thing to try for a mysterious failure.

Dan · Accepted Answer · 2013-01-02 14:24:56Z

7

After running into this problem a few minutes ago (yes, I know it's been 7 months since the original thread) I found that the root of my issue was due to me dragging & dropping files into my project within XCode instead of right-clicking and choosing Add Files to Project.

answered Jan 2, 2013 at 14:24

Dan

5,1534 gold badges33 silver badges42 bronze badges

1 Comment

PruitIgoe Over a year ago

Two years later...I always drag and drop image files into my project. I just had this happen and cleaning the project resolved it. Of course, since this is basically a dice roll error message who knows if that'll work for anyone else.

Dashzaki · Accepted Answer · 2012-05-30 06:55:10Z

4

Check playSiew.m is in Compile Sources section. isn't it?

You can find Compile Sources section follow this step

Select YourProjectName
Select TARGETS
Select Build Phases

If don't have playSiew.m in this section . You must to add it to this section.

answered May 30, 2012 at 6:55

Dashzaki

5682 gold badges6 silver badges13 bronze badges

Comments

Cesare · Accepted Answer · 2015-05-09 14:05:10Z

4

As I said the problem wasn't the code but some settings. So what I did was copying the code from my friends' Mac (it was working fine), and installed a fresh copy of the project to my Mac. It worked.

edited May 9, 2015 at 14:05

Cesare

9,45516 gold badges82 silver badges136 bronze badges

answered May 30, 2012 at 9:30

user1374408

3211 gold badge4 silver badges16 bronze badges

Comments

BrianHenryIE · Accepted Answer · 2017-05-04 22:46:41Z

3

I was importing a library in a test case which I had specified in my pod file for the main target but not for the test target.

answered May 4, 2017 at 22:46

BrianHenryIE

5675 silver badges15 bronze badges

1 Comment

JerryZhou Over a year ago

Saved my life. I was thinking I missing import some files which added by other guys. But actually it was this, one lib in pod file move a place and not included in test target!

ScottyB · Accepted Answer · 2015-10-06 18:50:03Z

2

I also got this error because I had accidentally included two versions of the same source file. Deleted the wrong one and the problem went away...

answered Oct 6, 2015 at 18:50

ScottyB

2,5371 gold badge36 silver badges50 bronze badges

Comments

Thyselius · Accepted Answer · 2017-04-11 13:23:14Z

2

If you're working in Unity and export to iOS and you are using a plugin, go to Xcode Build Settings and set ENABLE BITCODE = NO. I'm guessing this might apply to other situations as well

answered Apr 11, 2017 at 13:23

Thyselius

9741 gold badge11 silver badges14 bronze badges

1 Comment

BinaryNate Over a year ago

I too ran into this issue while building a Unity project, after I had added a compiler flag to a .m file in the Unity editor. I eventually noticed the message in the Unity editor that says: > "Once a native plugin is loaded from script, it's never unloaded. If you deselect a native plugin and it's already loaded, please restart Unity." After reading this, I restarted Unity and rebuilt the project, and the linker error went away.

shri · Accepted Answer · 2015-04-04 09:43:43Z

1

Faced similar issue, while running the code on a simulator, tried all the above mentioned options, still got the same error. Tried connecting the iOS device and build the code, it worked for us. This can be a quick workaround.

answered Apr 4, 2015 at 9:43

shri

8741 gold badge10 silver badges26 bronze badges

Comments

Community · Accepted Answer · 2017-05-23 11:47:06Z

0

the same error i faced. so, i just removed reference of that classes which are generating the errors and than again gave reference and the error was gone...

as D80Buckeye says there should be problem of dragging and dropping files instead of Clicking on "Add Files"

edited May 23, 2017 at 11:47

CommunityBot

11 silver badge

answered Nov 13, 2014 at 11:17

Vatsal Shukla

1,28213 silver badges28 bronze badges

2 Comments

Alex Over a year ago

This does not really answer the question. If you have a different question, you can ask it by clicking Ask Question. You can also add a bounty to draw more attention to this question once you have enough reputation.

Vatsal Shukla Over a year ago

@Pinal , i tried my self with the same issue on Xcode 6.0.1. and with that trick the issue was solved so, i shared my experience. so it is really not the answer of that Question.

Christina · Accepted Answer · 2015-06-10 17:43:33Z

0

In case this comes in useful for anyone else--I just had this same error, and turns out the cause was initializing a variable in my header file rather than in the main file.

answered Jun 10, 2015 at 17:43

Christina

1

Comments

Florian-Rh · Accepted Answer · 2015-09-24 12:20:51Z

0

I just encountered the same error. If you are using embedded Libraries, make sure your Deployment Target is set to iOS 8.0 or higher.

answered Sep 24, 2015 at 12:20

Florian-Rh

8171 gold badge9 silver badges28 bronze badges

Comments

Tala · Accepted Answer · 2016-01-11 14:33:03Z

0

you only need to add the following framework: quartzcore.framework

answered Jan 11, 2016 at 14:33

Tala

191 silver badge7 bronze badges

Comments

user441058 · Accepted Answer · 2017-01-28 00:14:38Z

0

The only way we can get past this bug on our project is to do a Clean and then build for iPad Retina. After that it will build successfully for any device. Weird.

answered Jan 28, 2017 at 0:14

user441058

1,2782 gold badges19 silver badges33 bronze badges

Comments

Surjeet Rajput · Accepted Answer · 2017-05-05 12:49:42Z

0

In my case i have add reference of FacebookLoginSDK framework but forget to give search path in build setting. After removing its reference everything was fine.

So conclusion is if you are adding any external framework be careful.

answered May 5, 2017 at 12:49

Surjeet Rajput

1,31118 silver badges26 bronze badges

Comments

Florian · Accepted Answer · 2017-06-03 23:30:58Z

0

If this happens to you with CoreData generated classes, combine the +CoreDataProperties and +CoreDataClass into the +CoreDataProperties class and delete the +CoreDataClass. Make sure to search Derived Data for leftovers of the +CoreDataClass. Even after deleting the Derived Data and cleaning I sometimes had Xcode just generate the +CoreDataClass again and again. Deleting it manually in Finder and then re-bulding helped me solve this.

answered Jun 3, 2017 at 23:30

Florian

3361 silver badge9 bronze badges

Comments

NIranjan Gajipara · Accepted Answer · 2017-06-27 14:11:13Z

0

try this, go to Target -> Build Settings,then search these three as following,

GCC_NO_COMMON_BLOCKS,

CLANG_WARN_INFINITE_RECURSION,

CLANG_WARN_SUSPICIOUS_MOVE,

set NO to each value then clean and build.

edited Jun 27, 2017 at 14:11

answered Jun 27, 2017 at 13:15

NIranjan Gajipara

213 bronze badges

Comments

M. Black · Accepted Answer · 2017-07-20 18:33:26Z

0

I tried several of the answers listed but none worked for me. I got the error after updating XCode (while it was still open which may have contributed to the problem)

First, I deleted my Derived Data folder: XCode => Preferences => Locations => Double Click on arrow next to path indicating where the Derived Data folder is. Then "Move to Trash" I don't think that's what the problem was, but it's amazing how many times this has been an issue for me working on different problems.

Second, I 'Quit' the simulator.

Third, I 'Quit' XCode.

Fourth, I opened up my project in XCode again and then did a Clean and Build (found in the Product menu)

Fifth, I ran my project and it worked fine

answered Jul 20, 2017 at 18:33

M. Black

3531 gold badge4 silver badges21 bronze badges

Comments

Yuchao Zhou · Accepted Answer · 2017-08-10 18:37:03Z

0

Cleaning the project not works for me. Restart the Xcode works for me...

answered Aug 10, 2017 at 18:37

Yuchao Zhou

1,07214 silver badges19 bronze badges

Comments

Wissa · Accepted Answer · 2018-04-23 11:56:35Z

0

For me it was different. I had the same error when I removed a Pod and solved it by removing this pod from the Other Linker Flags in the Build Settings

then clean your project [Product > Clean] and rebuild

answered Apr 23, 2018 at 11:56

Wissa

1,60025 silver badges26 bronze badges

Comments

Simon H · Accepted Answer · 2017-07-06 13:42:21Z

-2

Go to general and linked frameworks and libraries in xcode and remove all the files there.

enter image description here

edited Jul 6, 2017 at 13:42

Simon H

2,4954 gold badges33 silver badges38 bronze badges

answered Jul 6, 2017 at 12:55

Ishaan Gupta

112 bronze badges

Collectives™ on Stack Overflow

Linker command failed with exit code 1 error in Xcode project

21 Answers 21

2 Comments

1 Comment

1 Comment

Comments

Comments

1 Comment

Comments

1 Comment

Comments

2 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

21 Answers 21

2 Comments

1 Comment

1 Comment

Comments

Comments

1 Comment

Comments

1 Comment

Comments

2 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related