Why do I get iOS linker errors with my static libraries?

Question

I have a problem with linking my mixed language framework to a project.

I create a framework with Swift and Objective-C classes.
The main logic was stored in the Swift file. For example the class with a method that calls NSLog("Swift log was called").
Objective-C file has a class that has a method in which I create an instance of Swift class and call Swift-log method.
I link this framework with my Objective-C project, I can call all that I need in this project, but when I want to build this project I receive error linker command failed with exit code 1 (use -v to see invocation)

And warnings:

ld: warning: Could not find auto-linked library 'swiftFoundation'
ld: warning: Could not find auto-linked library 'swiftDarwin'
ld: warning: Could not find auto-linked library 'swiftCoreFoundation'
ld: warning: Could not find auto-linked library 'swiftCore'
ld: warning: Could not find auto-linked library 'swiftCoreGraphics'
ld: warning: Could not find auto-linked library 'swiftObjectiveC'
ld: warning: Could not find auto-linked library 'swiftDispatch'
ld: warning: Could not find auto-linked library 'swiftSwiftOnoneSupport'

I also saw the solution with importing empty Swift-file, but it necessary to make a project without any trash.

@PhilippHolly I need a solution that will not include empty files. — Yaroslav Skachkov, Oct 01 '18 at 07:22
I am sorry, I have not found any solution so far. let me know if you find something. — phips28, Oct 02 '18 at 18:10

score 194 · Answer 1 · answered Feb 08 '19 at 06:16

194

Open ios/YourAppName.xcodeproj in Xcode
Right-click on Your App Name in the Project Navigator on the left, and click New File…
Create a single empty Swift file to the project (make sure that Your App Name target is selected when adding)
when Xcode asks, press Create Bridging Header and do not remove Swift file then. re-run your build.

This should fix the problem

answered Feb 08 '19 at 06:16

Hussam Kurd

8,066
2
43
38

2

What If I already have an existing bridging header and the problem persists? I'm running on `MacOS Mojave` and `XCode 11.3.1` – blastervla Mar 02 '20 at 13:45
what if you're already have bridging file, can someone explain please – bona912 Oct 06 '20 at 09:41
4

Xcode does not ask 'Create Bridging Header' , Xcode version: 12.4 – John Stuart Jul 26 '21 at 18:49

score 99 · Answer 2 · answered May 16 '19 at 21:41

99

In my case it was a React-Native project after adding a Swift Pods library. Maybe just the step 2 can work:

Adding a new Swift file and a Brigde header:

1) File -> New -> File

2) Select Swift File

3) Confirm Create Bridging Header

Go to Build Settings and set Always Embed Swift Standard Libraries to YES

answered May 16 '19 at 21:41

AlVelig

1,989
15
9

Where will i put the file, under pods or the project? – lutakyn Aug 20 '19 at 18:37
@lutakyn I've put it in the project – AlVelig Aug 21 '19 at 20:55
Do not remove the dummy Swift file after the bridging file is created! Keep it or build fails – Nader Ghanbari Jan 19 '20 at 02:59
2

Step `Create Bridging Header` does not appear for me. It says `Save File` for me. – dcangulo Mar 11 '20 at 07:18
1

@dcangulo that steps appears only if your filename contains "bridging-header" – Luca Davanzo Mar 13 '20 at 09:04

score 93 · Answer 3 · edited May 07 '19 at 14:59

93

Apparently for pure objective-c projects you will need to add this $(TOOLCHAIN_DIR)/usr/lib/swift/$(PLATFORM_NAME) to the library search paths of your target. This worked for me when I was including a library written in swift to a project in objective-c

edited May 07 '19 at 14:59

blastervla

539
6
19

answered Nov 01 '18 at 12:47

Nathan

1,013
6
6

can you give us an example how we can added, as i am trying it but i don't really work for me , maybe aim placing it in a wrong place – Amr Angry Jan 07 '19 at 22:07
@Nathan How to set this in podspec, and not need add it manually? – huangxinyu Feb 25 '19 at 08:58
11

This worked perfectly! For anyone wondering how exactly to do this; click your xcode project in the file explorer -> under `Targets` select your target -> select the `Build Settings` tab -> search for `Library Search Paths` and add `$(TOOLCHAIN_DIR)/usr/lib/swift/$(PLATFORM_NAME)` to the debug and release sections. – LarryFisherman Mar 06 '19 at 00:54
6

Unfortunately this trick seems to have stopped working when using Swift 5 with Xcode 10.2 - probably because there are now system-wide Swift libs with iOS 12.2. – megastep Mar 30 '19 at 02:04
4

For those who are new to Xcode make sure "All" is selected and is blue else you might not find Library search path – amar Aug 12 '19 at 04:54
@megastep so how do fix it? – Almas Adilbek Sep 10 '19 at 12:40
1

Try adding the following to your target's library search path: $(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME) – gom1 Sep 17 '19 at 22:25
1

It compiles but then I got a crash at the launch of the application: "This copy of libswiftCore.dylib requires an OS version prior to 12.2.0". If you want to solve it just add an empty swift file in the project, keep it forever and it will work. (The problem come from the fact that you are using both objective-c and swift code in your app) – Fantasim Sep 18 '19 at 12:00

score 26 · Answer 4 · answered Jan 06 '21 at 19:49

26

I have export my unity project. Earlier it was working just to add empty swift file with press create Bridging Header.

but recently i have updated my xCode to 12.3 and it stop working.

So, tried few other ways.

I have added $(SDKROOT)/usr/lib/swift to Build settings > Search paths > Library search paths.

but still it doesn't work. So, i have added in same path i.e Build settings > Search paths > Library search paths.

$(TOOLCHAIN_DIR)/usr/lib/swift/$(PLATFORM_NAME)

$(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)

Now it working perfect. Didn't get exact problem or solution but it works well with this way.

I just add these three in Build settings > Search paths > Library search paths.

$(SDKROOT)/usr/lib/swift
$(TOOLCHAIN_DIR)/usr/lib/swift/$(PLATFORM_NAME)
$(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)

Separately TOOLCHAIN_DIR directories doesn't work. If i add $(SDKROOT)/usr/lib/swift then only it work.

answered Jan 06 '21 at 19:49

Saveen

4,120
14
38
41

14

Tested in Xcode 12.5, `$(SDKROOT)/usr/lib/swift` needs to be the first – xhg May 09 '21 at 09:52
2

Thanks, it work for Xcode 13.1 – Anonimys Dec 07 '21 at 11:57
1

Thanks, it work for Xcode 13.2 – moralejaSinCuentoNiProverbio Mar 02 '22 at 15:29
1

Xcode 13.4.1 - it worked. Thanks! I tried empty swift files, creating bridging headers manually, removing those lines - nothing worked. The final solution included adding these 3 lines to the main target and *removing* those lines from another target which was a dependency to the main one – Ruzard Jul 13 '22 at 07:06

score 22 · Answer 5 · answered Jul 20 '19 at 16:24

22

For XCode 11 beta 4 Library Search Paths should be:

$(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)

answered Jul 20 '19 at 16:24

Aleksey Gotyanov

510
4
8

1

I had to add this to each of my targets Library Search Paths property. Not just the main app. So, including my watch kit and Siri Intents targets. – Tap Forms Jul 24 '19 at 18:04
1

Any targets with Swift code need to have the above mentioned path for XCode 11 – gom1 Sep 17 '19 at 22:23
1

Note if you have this in Xcode 12 still, it can f* your build.]\ – scaly Jan 27 '21 at 08:26

score 15 · Answer 6 · answered May 06 '20 at 04:18

15

Right click project name and add a new swift file leave it as File.swift
it will ask you to create a new bridging header accept
Run the project again

answered May 06 '20 at 04:18

Chinedu Ofor

707
9
11

score 13 · Answer 7 · answered Oct 22 '18 at 23:29

13

Try this workaround https://stackoverflow.com/a/50495316/1658268

Basically just add a dummy swift file in your project, and re-run your build.

answered Oct 22 '18 at 23:29

SudoPlz

20,996
12
82
123

3

You are the second who suggest this solution :). As I said in comments to description of my question, I need solution without empty Swift-files. – Yaroslav Skachkov Oct 24 '18 at 08:46

score 10 · Answer 8 · edited Nov 11 '20 at 21:45

10

If you have issue after update xCode to version 12 and errors

Could not find or use auto-linked library 'swiftWebKit'

and two more.

Just addd $(SDKROOT)/usr/lib/swift to the Build settings > Search paths > Library search paths.

Hope its help :)

edited Nov 11 '20 at 21:45

Niko

3,412
26
35

answered Sep 24 '20 at 06:44

SerhiiVolynets

101
1
2

1

@SehiiVolynets, Please use italics (use `*` brackets) for pathways. – maciejwww Sep 24 '20 at 09:47
@maciejwww, what do you mean by "italics" and "asterisk brackets"? Which one should be used? – easytarget Feb 20 '21 at 13:50
I mean formatting policy on StackOverflow. Using asterisk brackets formats text into italics: `*text*` --> *text*. For pathways in GUI, it's recommended to use *italics* or **bold** (double asteriks: `**text**`) font. However, in this case is better to use **bold** font than *italics*, I suppose. Now, my comment is no longer needed because @Niko have edited yours answer. Check it out and compare with your version. Short info about text fotmatting and example you can find [here](https://askubuntu.com/revisions/1269857/2). – maciejwww Feb 21 '21 at 16:15
Worked for me! Thanks Xcode 12.5 iOS 14.5 – Robert Bentley May 08 '21 at 20:09

score 9 · Answer 9 · edited Jan 04 '21 at 13:41

9

If your Xcode version is >=12.2

Go to

BuildSettings -> Linking -> runpath search path

and add /usr/lib/swift as your 1st argument like this:

edited Jan 04 '21 at 13:41

dylan-myers

323
3
18

answered Nov 01 '19 at 08:42

ahcodes

109
1
3

Can someone explain to me why the -1? Because I tried this and now I no longer need to constantly Clean => Rebuild whenever I change a single line. Note: I also needed to set "Enable Bitcode" as "No" – Cristiano Santos Jul 16 '20 at 09:45
Worked fine for me, thanks a lot!! – Patrick DaVader Nov 08 '21 at 09:34
When linking on command line, `-L /usr/lib/swift` worked great. It's much shorter than using the equivalent of `-L $(SDKROOT)/usr/lib/swift`. Thanks! – tompark Mar 16 '23 at 20:59

Erik Dreifaldt · Answer 10 · 2021-09-21T21:27:04.253

7

Xcode 12.5, React Native.

Change: 'Library Search Paths' from Swift-5.0 to Swift-5.2

edited Sep 21 '21 at 21:27

answered May 30 '21 at 12:15

Erik Dreifaldt

773
7
13

Hey thanks a lot for this! Changing the Library Search Paths from swift-5.0 to swift-5.2 made my app finally build and run (it has nothing to do with watch apps or widgets). – Pauli Kettunen Aug 17 '21 at 10:21

score 6 · Answer 11 · answered Mar 21 '22 at 10:01

6

What worked for me in a React Native project is to move $(inherited) to the bottom of the list in Build Settings -> Library Search Paths

answered Mar 21 '22 at 10:01

B. Mohammad

2,152
1
13
28

worked for me too. can you tell us why it works? – meowmeowmeow Jan 19 '23 at 04:42
I have no idea, maybe an iOS dev can answer that. – B. Mohammad Jan 19 '23 at 17:14

score 3 · Answer 12 · answered Jan 30 '19 at 13:57

3

I've got the same errors when accidentally compiling a project with a Swift 5.0 Snapshot configured in the Xcode preferences » Components » Toolchain.

answered Jan 30 '19 at 13:57

Ralf Ebert

3,556
3
29
43

I've changed it on purpose...any way I can compile it on arm64 (works fine on simulator)? – Kirow May 03 '19 at 14:39

score 2 · Answer 13 · answered Apr 12 '22 at 10:17

I am getting this error after installing Lottie-react-native?

The solution only works if it is caused by adding Lottie package.

This worked for me:

yarn add lottie-react-native
yarn add lottie-ios@3.2.3

And then must run:

pod install or pod update

I am using:

"lottie-ios": "3.2.3",
"lottie-react-native": "^5.0.1",
"react": "17.0.2",
"react-native": "0.67.3"

score 1 · Answer 14 · answered Dec 16 '19 at 11:29

XCode 11.3 beta, Swift 5.0

I just add my targets to the podfile:

platform :ios, '9.0' 
use_frameworks! 
inhibit_all_warnings!

def shared_pods
    # Pods for NamaIOS
    pod 'Alamofire'
    pod 'RxSwift'
end

target 'MyApp' do
  use_frameworks!

  shared_pods

end

target 'MyApp-Test' do
  use_frameworks!

  shared_pods

end

target 'MyApp-Development' do
  use_frameworks!

  shared_pods

end

score 1 · Answer 15 · answered Feb 23 '20 at 07:05

1

if you come from lottie-react-native install instructions just add use_frameworks! to podFile #536 (comment)

answered Feb 23 '20 at 07:05

JimmyWj4EHiM

393
4
12

score 1 · Answer 16 · answered Mar 02 '22 at 15:28

I am android programmer. It took me a while understand what they were doing. I have currently Xcode 13.2.1 And flutter 1 awful combination I know. Please edit in other side xcode will take the enter like "I end" I change Build settings > Search paths > Library search paths.: From:

$(inherited) $(PROJECT_DIR)/Flutter

to:

$(inherited) $(PROJECT_DIR)/Flutter $(SDKROOT)/usr/lib/swift $(TOOLCHAIN_DIR)/usr/lib/swift/$(PLATFORM_NAME) $(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)

Thats all, I hope to help some folk.

score 0 · Answer 17 · answered Jul 22 '19 at 11:59

In case you encounter this error while using Xcode 11 beta 4 in combination with carthage see this workaround:

https://github.com/Carthage/Carthage/issues/2825

Basically it consists of creating a xcconfig with the fixes and inject these into each build.

score 0 · Answer 18 · answered Apr 25 '20 at 19:07

0

I only forget to Add the new Framework to my pod file :)

 target 'Data' do
inherit! :search_paths
 pod 'AlamofireObjectMapper', '~> 5.2'

end

answered Apr 25 '20 at 19:07

Amir Ardalan

389
3
7

score 0 · Answer 19 · answered Nov 27 '20 at 09:37

0

for Xcode 12.2

Create an Empty Swift file using Xcode, such as named Void.swift, and every issue will be solved by Xcode automatically.

answered Nov 27 '20 at 09:37

Nrv

280
1
6

score 0 · Answer 20 · answered Aug 31 '21 at 14:48

0

I ran into this issue with our project and the issue was that there were orphaned references to lottie in our xcode project file. Opening that in a text editor and removing them fixed the issue for me.

answered Aug 31 '21 at 14:48

TALE

960
13
22

score -1 · Answer 21 · answered May 03 '20 at 22:38

-1

What solved it for me when trying to integrate Lottie in my React Native project was to uninstall the lottie-ios and lottie-react-native modules with npm.

npm uninstall lottie-react-native lottie-ios

Make sure the files are unlinked as well

npx react-native unlink lottie-react-native lottie-ios

I also had the bridging-file in my project from previously trying that method without success so in order to replicate my process, follow the suggested answer and add that file to your project as well.

After these steps, I went ahead and deleted my Pods folder, cleaned my build from xcproject and xcworkspace (maybe one of these is enough). After that I went ahead and installed the modules again

npm i --save lottie-react-native lottie-ios@3.1.3

(Make sure to check the current docks over at the lottie repo for the up-to-date versions.)

After you have reinstalled the modules, cd into your ios folder and run pod install.

Open up your xcworkspace in Xcode and run your project (make sure your build is clean).

This solved my issue.

Best of luck.

answered May 03 '20 at 22:38

KentAgent

413
1
4
14

what lottie-react-native version you install – Engr.Aftab Ufaq Aug 28 '21 at 07:15
1

Hello @AftabAmin , thanks for the downvote . If you read my post you'll see I follow the documentation over at the lottie RN docs: https://github.com/lottie-react-native/lottie-react-native At the time of posting this a year ago I'm not too sure the version but give it a go with the latest stable release. Good luck! – KentAgent Aug 28 '21 at 08:24
1

I have tried all the updated version but non is working. when I remove these libraries it works fine. tow months later my app was running. today I was updating my app and suddenly got this issue. also faced this a month ago but then I solved it. – Engr.Aftab Ufaq Aug 28 '21 at 09:47
@AftabAmin I see, that's too bad. let the devs over at lottie RN know about this by opening a through issue perhaps. Might help more people than yourself. Too bad I can't be of anymore help. Been a while since I worked with lottie. – KentAgent Aug 28 '21 at 12:00
@AftabAmin, how you fix it?? – Jamal Ud Din Apr 12 '22 at 10:08

Why do I get iOS linker errors with my static libraries?

21 Answers21

Linked