Linker Command failed with exit code 1 (use -v to see invocation), Xcode 8, Swift 3

Question

I can't get rid of this error!

I have tried all sorts of things like clearing Derived Data(Preferences->Locations->click gray arrow to open Derived Data folder in Finder->right-click, move to trash), cleaning the project(CMD+Shift+K or Product->Clean), updating carthage and dependencies, checked other answers on StackOverflow (mostly adjustments in Build Settings/Phases), and recloned the app from github, etc.

The same project works on my collaborators computers..

EDIT: From the current top-rated answer, I was able to debug a little further...I am still not sure how to fix though. It looks like I have something in the project twice? I looked and can't find anything showing up twice!

Here's a picture of the log:

https://stackoverflow.com/questions/44601404/apple-mach-o-linker-error-clang-error-linker-command-failed-with-exit-code-1 — Naresh, Mar 02 '19 at 09:25
why did you accept the top rated answer if it didn't resolve your issue...? — benomatis, Apr 09 '19 at 09:07
@umairqureshi_6's answer is not proper for this question. I can't understand how it can be the accepted answer of this question. It didn't give any hint. — SatelBill, Sep 06 '21 at 09:12

score 165 · Accepted Answer · answered May 05 '17 at 09:34

165

i was facing same issue today in xcode 8 version 8.3.2

right click on issue --> reveal in log

then you are able to check what is causing that issue

answered May 05 '17 at 09:34

umairqureshi_6

1,786
1
12
10

Thanks for that! Here's what I get in the log: http://imgur.com/vFkNJzZ – Jake Dobson May 13 '17 at 20:42
I finally solved this. You helped lead me in the right direction! It really sucked that Xcode didn't reveal the log when clicked on...Could have saved me some time! – Jake Dobson May 17 '17 at 00:11
Thanks for the Reveal in Log tip. I didn't know I could use it – KarenAnne Jun 19 '17 at 11:00
1

@JakeDobson Can you please tell me how did you solve this? – Ghasem Tabatabaei Aug 06 '17 at 07:57
1

@GhasemTabatabaei Check my answer below – Jake Dobson Aug 07 '17 at 02:49
124

Why is this the accepted answer? It doesn't actually answer the question, only potentially assist in reaching the solution. – Tom Oakley Sep 05 '18 at 10:29
This is not an answer. – Zach Folwick May 13 '20 at 18:40

score 119 · Answer 2 · answered Sep 07 '17 at 16:13

119

Maybe you installed a pod file and you are still trying to build from the .xcodeproj file instead of .xcworkspace

answered Sep 07 '17 at 16:13

Aashish

2,532
2
23
28

4

No, I used Carthage for that reason. That's a legitimate answer that could help other people with this same error, though! – Jake Dobson Sep 07 '17 at 23:39
1

I added m$ AppCenter code to an existing project and it needed Pods. No idea what was going on and had been doing it with the `.xcodeproj` for over a year.. Something this simple! – Dennis Smolek Jun 19 '18 at 06:10
1

My fix was somewhat related to this. I had recently upgraded some dependencies and the project now used CocoaPods. Previously I was always working from the project file. I opened the workspace file, which had both my project and Pods in it, and everything worked fine. – Rozgonyi Feb 05 '20 at 16:36

score 42 · Answer 3 · answered Jul 25 '17 at 18:30

42

the only thing that worked for me was to run pod deintegrate and pod install

answered Jul 25 '17 at 18:30

Charles Harring

997
8
8

The question has been answered. If you see my comment below, I had imported a file that had already been imported into that file. The project was in a race condition trying to reference the file twice. – Jake Dobson Jul 25 '17 at 18:39
ok yeah it jsut didnt work for me and when i googled it this is what came up, so i thought id try and help someone else...im new to this, should i delete my answer? – Charles Harring Jul 26 '17 at 00:17
I guess not since it's already there. I'm sure somebody might find it useful. The app I was using did not use cocoapods. The thing is, this error is very common and gives little information about itself. So many solutions can be found, depending on each project. – Jake Dobson Jul 26 '17 at 15:47
It saves my day! God bless you! – user2612604 Aug 06 '20 at 00:21

score 20 · Answer 4 · answered May 05 '17 at 02:17

20

did you try a clean? cmd + shift + k

answered May 05 '17 at 02:17

Francisco Perez

245
1
4

9

Oh yeah..plenty of times! – Jake Dobson May 05 '17 at 02:28
That's literally all I get...Clicking on the text does not send me to any extra information or the location of the file where it happened like it does for most errors. Nothing in the console, it doesn't ever get to running the app because of this error.. – Jake Dobson May 05 '17 at 02:38
FWIW, I encountered this issue recently when building with an SDK and @FranciscoPerez's suggestion did the trick. Definitely recommend it as a first step before you get too deep into debugging. – riastrad Feb 26 '19 at 20:03

score 11 · Answer 5 · answered May 17 '17 at 00:09

Okay...So here is what solved my problem...

in App Delegate File:

#import "AppDelegate.h"
#import "DarkSkyAPI.h"
//#import "Credentials.h"

I had imported Credentials.h already in the DarkSkyAPI.m file in my project. Commenting out the extra import made the error go away!

Some things to mention and maybe help anyone in the future. @umairqureshi_6's answer did help me along the process, but did not solve it. He led to where I was able to dig out the info. I kept seeing AppDelegate and DarkSkyAPI files showing up in the error log and the information it was pulling from Credentials file was causing the error. I knew it had to be in one of these 3 files, so I immediately checked imports, because I remembered hearing that the .h carries all the imports from its .m file. Boom!

score 6 · Answer 6 · answered Sep 11 '17 at 07:39

I k now the question has already been answered. But if this helps somebody save some time : I had the same error. I checked everything to find a very small and stupid mistake from my side. I imported a core data ManagedObject custom file in a view controller of my project. I accidentally imported the .m file instead of the .h file which was causing the duplicate symbol in architecture error (linker command failed) because my .m file of properties class imports the .h file of core data class and hence causing duplicate import.

So just check if u have imported the right files before you try multiple solutions.!

Yes! This was very similar to my problem. I had the same file imported twice in my project. Rather, I imported a "fileA.h" into "fileB.h", but then imported "fileA.h" and "fileB.h" into "fileC.h", or something along those lines...So the app crashes because it does not know which to use. Definitely a good place to have a reminder for others to double check their file imports! — Jake Dobson, Sep 11 '17 at 14:36

score 6 · Answer 7 · answered Apr 27 '18 at 20:35

A lot of solutions are mentioned above. No one worked for me(but please try above first).

Select Project -> Select Target -> Linked Framework and Libraries -> Add all pod libraries . (remove if they exist in embedded binaries)

Now remove these from Framework Folder in left file explorer of xcode.

This solved my issue.

score 6 · Answer 8 · answered Jun 07 '18 at 09:47

6

Select the project-> Build Phase->Link Binary with libraries and add all pod libraries.

answered Jun 07 '18 at 09:47

K Prasad

67
1
5

Yes! This one solves it in 2023, confirmed and many thanks! – Okhan Okbay Jul 10 '23 at 11:59

score 4 · Answer 9 · edited Jun 13 '18 at 07:50

4

I had the same problem using Carthage for dependencies.

Just go to Select Project -> Build Settings -> Search for Enable Bitcode -> If it is selected to Yes, select No.

That solved this problem for me.

edited Jun 13 '18 at 07:50

Pang

9,564
146
81
122

answered Jun 13 '18 at 07:20

Adri Silva

111
2
2

score 4 · Answer 10 · answered Feb 07 '19 at 08:52

4

In my case the reason of the error is library which was linked two times.

I use react-native so it was linked automatically using react-native link and manually in xcode.

answered Feb 07 '19 at 08:52

Stanislav Mayorov

4,298
5
21
44

can you elaborate pls on the fix? – Hagai Harari Feb 14 '21 at 11:26
@HagaiHarari I don't remember a lot of details. I would try to unlink manually in xcode and check. – Stanislav Mayorov Feb 14 '21 at 19:47

score 2 · Answer 11 · edited Jul 03 '18 at 13:09

2

I had same problem.

The cause was that I declared same global variable in 2 files. So it was showing same error saying 2 duplicate symbols.

The solution was to remove those variables.

edited Jul 03 '18 at 13:09

Jean-François Corbett

37,420
30
139
188

answered Jul 03 '18 at 12:50

ajitspyd

754
5
8

1

why did you remove both and not just one? – Jake Dobson Apr 10 '19 at 15:19

score 2 · Answer 12 · edited Nov 26 '18 at 17:07

2

For any one having this issue with Flurry framework. This is what fixed my issue. For me the issue was that i had imported the following files but never used them. "libFlurryTVOS_9.2.3" "libFlurryWatch_9.2.3"

So all I had to do was go to project target settings and remove these 2 files from the "Linked framework and libraries" section and the problem was solved.

edited Nov 26 '18 at 17:07

Miriam Farber

18,986
14
61
76

answered Nov 26 '18 at 16:49

Cedan Misquith

1,134
9
20

score 2 · Answer 13 · answered Feb 16 '19 at 22:35

2

Make sure the Find Implicit Dependencies checkbox is checked.

(Product -> Scheme -> Edit Scheme -> Build -> Find Implicit Dependencies)

answered Feb 16 '19 at 22:35

llama591

453
5
15

score 2 · Answer 14 · edited Oct 31 '19 at 21:37

2

I was testing the Sparkle framework with CocoaPods.

Sadly, I put pod 'Sparkle', '~> 1.21' in the PodFile in the wrong place. I put it underneath Testing (for unit tests).

Once placed in correct spot in PodFile, everything's fine.

edited Oct 31 '19 at 21:37

pkamb

33,281
23
160
191

answered Mar 03 '19 at 21:26

pdq

159
4

score 1 · Answer 15 · answered Oct 02 '17 at 03:23

1

I just had to do import Foundation!

I was using Kitura for Swift server side and kept forgetting this!

answered Oct 02 '17 at 03:23

mfaani

33,269
19
164
293

Ha. Yeah, you will always need to at least import Foundation before you do anything! I usually import UIKit instead of Foundation, because almost always I will need to use features of UIKit and UIKit has inherits everything from Foundation for you. Imports with Objc can be pretty tricky, but it looks like you were using Swift? – Jake Dobson Oct 02 '17 at 18:05
Yes I was using Swift, the file at hand wasn't showing any compiler issues, but only during running the file, I ran into this issue! – mfaani Oct 02 '17 at 18:10
1

Yeah, I don't think it really checks for that until runtime, I could be wrong. But, it seems like it wouldn't have an issue until you were trying to access something from Foundation, couldn't find the import, then couldn't continue the process -- crash! – Jake Dobson Oct 02 '17 at 18:49

score 1 · Answer 16 · answered Oct 23 '17 at 11:35

1

Here is my problem and solution:

I removed two files from the source code using source tree(Version controller). After applying the diff, that contains the two classes I removed, Xcode didn't add it automatically. So I got linker error.

I manually added the files, by right click on group name and select "Add files to ". Now my error got resolved.

If anyone faced the linker error regarding class file, then try to add it manually.

answered Oct 23 '17 at 11:35

Sujananth

635
1
10
24

1

It definitely seems like a file issue they are trying to hint at...Files elsewhere are not retrieving information from one another seems commonly found on this page. Thanks for your reply. Hoping it helps someone down the road! – Jake Dobson Oct 23 '17 at 17:13

score 1 · Answer 17 · answered Nov 10 '18 at 00:50

1

Did not have this problem when I built and ran on my own device. Only had this problem with simulators. I just simply restarted my computer and ran it. It worked.

answered Nov 10 '18 at 00:50

jamryu

668
10
24

score 1 · Answer 18 · answered Feb 13 '19 at 05:11

In my case I have change the Target name in my Podfile So it's create the same Error for me.

Solution

Just go project-> Build Phase->Link Binary with libraries Remove the old FrameWorks by click on minus button(-) And clean and Run again. It's work me.

Remove Unwanted .framework.

score 1 · Answer 19 · answered Feb 13 '19 at 13:54

The other answers didn't work for me so here I share my solution in case it might help somebody else:

My problem was that I was configuring the Podfile of my XCode-Project for the wrong platform. Changing "platform :ios" at the beginning of my Podfile to "platform :macos" worked for me to get rid of the error.

score 0 · Answer 20 · answered Apr 11 '19 at 10:30

0

I had the same problem. If you are checking out any github project, then instead of using git clone, use git lfs clone, as sometimes, some large files are not properly cloned by using git only. Also, make sure your bitcode is disabled.

answered Apr 11 '19 at 10:30

Aman pradhan

258
5
12

good note..but usually the console will let you know that some files are too large to be transferred? – Jake Dobson Apr 21 '19 at 01:01

score 0 · Answer 21 · answered Jul 25 '19 at 01:10

0

For me, the gem lock file was specifying an older version of cocoapods than the one I had installed. I had to re-branch and run bundle exec pod install instead of pod install

answered Jul 25 '19 at 01:10

Jason

808
6
25

score 0 · Answer 22 · answered Oct 05 '19 at 01:39

It seems like the issue is different for most of us, and the error message has decent info. In my case, the Deployment Target was set to 10.13 by the export MACOSX_DEPLOYMENT_TARGET=10.13 line, but I was running 10.14. So I had to switch my Deployment Target to 10.14 in General > Deployment Info, in order for the ITLibrary-related symbols to be available again.

cd /Users/foo/src/scrobble/macos/itunes-scrobble
    export MACOSX_DEPLOYMENT_TARGET=10.13

... SNIP ...

Undefined symbols for architecture x86_64:
  "_OBJC_CLASS_$_ITLibMediaItem", referenced from:
      objc-class-ref in AppDelegate.o
  "_OBJC_CLASS_$_ITLibPlaylist", referenced from:
      objc-class-ref in AppDelegate.o
  "_OBJC_CLASS_$_ITLibrary", referenced from:
      objc-class-ref in AppDelegate.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

score 0 · Answer 23 · answered Jul 04 '20 at 00:41

In my case, I was producing multiple products from the same project. For one of the products, the main.m file imported a header file from another folder under the same project. But that file was not included in "Complied Sources" under "Build Phase". This caused a linker error.

After carefully comparing the "Build Phases" settings for a product that could be built successfully, I realized that the .m file of the header needs to be included in the list of "Compiled Source". My issue was resolved after adding that file. Attaching a picture for clarity. The highlighted file had to be added.

temirtator · Answer 24 · 2021-01-13T09:42:09.307

0

One of the reasons of this problem might be "Build Active Architecture Only". You need set to true.

edited Jan 13 '21 at 09:42

answered Jan 13 '21 at 09:00

temirtator

116
1
2
8

score 0 · Answer 25 · answered Jun 01 '21 at 22:37

0

IOS version in build phases of pod(in xcode) and ios version in pod file should be same (Try with 9.0)

answered Jun 01 '21 at 22:37

Zaid Munir

13
4

score 0 · Answer 26 · answered Apr 05 '23 at 09:48

for me the issue occurred with xcode 14, some frameworks on pods had minimum deployment target on ios 8.0, to fix the issue I added the following to pod file:

post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = "12.0"
     end
  end
end

score -1 · Answer 27 · answered Aug 08 '23 at 14:53

The solution that worked for me is changing all podfiles minimum deployable version to 11.0

You can also do this by adding a script to the bottom of our podfile:

    post_install do |installer|
    installer.generated_projects.each do |project|
          project.targets.each do |target|
              target.build_configurations.each do |config|
                  config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = 
    '11.0'
               end
          end
       end
    end

score -5 · Answer 28 · answered Aug 18 '18 at 15:46

Ok, I had the same problem just today and started googling it, when I came across this thread. I haven't finished reading the question when the answer struck my mind: I declared a class with an empty constructor

class MyClass{
    MyClass();

    void func_one(){
    // code
    }

    void func_two(){
    // code
    }

    ~MyClass(){
        cout << "Deleting object" << endl;
     }
};

Then I thought why not terminating (not sure if I'm correct with word selection here, but who cares) the constructor of my class with curly braces ({}). So I did:

class MyClass{
    MyClass(){}

    void func_one(){
    // code
    }

    void func_two(){
    // code
    }

    ~MyClass(){
        cout << "Deleting object" << endl;
     }
};

The problem eliminated, my code started working perfectly.

I know, the good practice is to investigate the issue and find the real cause, but this worked for me.

I do not think this is helpful for this thread...It seems like the error is trying to get at a file issue, like importing the same thing in separate files. I find it strange you would get this error, because this is an Objective-C specific error... — Jake Dobson, Aug 20 '18 at 17:16
I got this error in C++ too. The linker error in your case was probably that the linker couldn't find the code for your constructor. I had a similar error with a function that I renamed but because Xcode 10 wouldn't open the linker log on its own, and I didn't know you could right-click and "reveal in log", I was stumped for a few minutes trying to locate the error. — Matt Parkins, Oct 13 '18 at 07:12

Linker Command failed with exit code 1 (use -v to see invocation), Xcode 8, Swift 3

28 Answers28

Linked