Cannot fix "Could not find or use auto-linked library "

Question

I have an app built with Swift with pods(firebase). I have 18 warnings and 100 errors which weren't there before. They only appear when I try to archive my app.

I have tried all of these (Adding search paths, Adding blank swift files, deleting framework paths)

It gives errors when using Swift Static library with Objective-C project

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

ld: warning: Could not find or use auto-linked library 'swiftFoundation'
ld: warning: Could not find or use auto-linked library 'swiftsimd'
ld: warning: Could not find or use auto-linked library 'swiftGLKit'
ld: warning: Could not find or use auto-linked library 'swiftMetal'
ld: warning: Could not find or use auto-linked library 'swiftSpriteKit'
ld: warning: Could not find or use auto-linked library 'swiftDarwin'
ld: warning: Could not find or use auto-linked library 'swiftUIKit'
ld: warning: Could not find or use auto-linked library 'swiftCoreFoundation'
ld: warning: Could not find or use auto-linked library 'swiftObjectiveC'
ld: warning: Could not find or use auto-linked library 'swiftCore'
ld: warning: Could not find or use auto-linked library 'swiftQuartzCore'
ld: warning: Could not find or use auto-linked library 'swiftModelIO'
ld: warning: Could not find or use auto-linked library 'swiftDispatch'
ld: warning: Could not find or use auto-linked library 'swiftAVFoundation'
ld: warning: Could not find or use auto-linked library 'swiftCoreMedia'
ld: warning: Could not find or use auto-linked library 'swiftCoreGraphics'
ld: warning: Could not find or use auto-linked library 'swiftCoreImage'
ld: warning: Could not find or use auto-linked library 'swiftCoreAudio'

Environment: Xcode 11 beta 4 / Target: iOS 12 and up

score 20 · Accepted Answer · answered Jul 19 '19 at 12:58

20

Apple mentioned similar issue in known issues section:

Targets that contain Swift code with the Enable Bitcode build setting set to Yes fail to link correctly when built with the Archive action.

And give us a workaround:

Add a custom build setting with the name LD_VERIFY_BITCODE, and set it to NO. Make a note to yourself to delete this custom build setting once this issue is resolved.

answered Jul 19 '19 at 12:58

Dominique Stranz

378
3
6

Thanks. You made my day! – Muxor Jul 22 '19 at 13:34
1

For me actually, before I noticed this answer I deleted all of my pods and reinstalled them and that fixed it for me – Yuto Aug 05 '19 at 01:33
3

I am facing a similar issue while building my `react-native` code for iOS. This solution isn't working for me. Is there anything else that can be done? – LordAnari Apr 20 '20 at 21:03
Same issue as @LordAnari . Also getting this in react-native. Any pointers would be much appreciated. – KentAgent May 03 '20 at 21:47
@KentAgent which library are you manually linking? For me, I am trying `react-native-razorpay`. Just wondering if it has anything to do with this. – LordAnari May 10 '20 at 21:19
@LordAnari I managed to solve my issue. Please check my answer on another question here and see if that solves your problem: https://stackoverflow.com/a/61582562/8576909 – KentAgent May 11 '20 at 23:14

score 15 · Answer 2 · answered Jun 03 '20 at 12:23

My ObjectiveC project was including a Swift pod which was then throwing the above errors. I found all I had to do was add a swift header file into the base of my project and it suddenly all built.

What gave it away for me was when I went into the Build Settings of my Target project and did a search for 'swift' I was only seeing a very minimal amount of results when I knew I should be seeing more - after adding the header file I suddenly saw a lot more options here. Below are the steps I took.

Right click on your root project in the Project Navigator
Select 'New File'
Select a 'Swift File'
Give it a name of 'BridgeHeader' (you don't need to specify the .swift - it'll add the extension automatically)
Run a clean + build and hopefully the errors will have disappeared!

I'm unsure if the name is important, nor am I sure on the position of the file but this is what worked for me!

Works! should be the accepted answer. Had this issue when using #import and setting setAdvertiserTrackingEnabled and it fixed my issue as I was building in Objective C — AntiPawn79, Dec 01 '21 at 21:00

score 4 · Answer 3 · answered May 16 '20 at 13:50

4

I had a same error... my problem solved with -> add the library (framework) in the Frameworks and Libraries that you used in any target

for Example :

answered May 16 '20 at 13:50

Amir Ardalan

389
3
7

score 4 · Answer 4 · answered Nov 24 '21 at 16:25

4

In my case, it was a React-Native project after adding a Swift Pods library.

Solution 1:

Adding a new Swift file and a Bridge header:

File -> New -> File
Select Swift File
Confirm Create Bridging Header

Solution 2:

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

answered Nov 24 '21 at 16:25

Muhammad Numan

23,222
6
63
80

1

This is the solution :) Thanks mate – Chathuranga Kasthuriarachchi Dec 10 '21 at 15:08

score 2 · Answer 5 · answered Feb 02 '21 at 20:10

2

Create a swift file in the main project (File.swift) and add the following code to the same

//
// File.swift
//
import Foundation

answered Feb 02 '21 at 20:10

AliRehman7141

873
3
12
33

score 2 · Answer 6 · answered Feb 04 '22 at 09:28

2

In my case I accidentally added a test file to the main swift target. Removing it solves the problem

Here are what I did

1. go to compile source for the main target

2. search for test

3. remove it

answered Feb 04 '22 at 09:28

Piakkaa

740
6
12

score 1 · Answer 7 · answered Mar 19 '21 at 06:06

In case you see the issue after updating React Native from 0.63.x to 0.64.x, try this solution:

Create a new 0.64.x project:

npx react-native init MyApp --template react-native-template-typescript

Compare package.json of the new project and of your old 0.63.x project, and modify the old one.
Do similarly with ios/Podfile.
Run yarn install or npm install.
Run pod install in ios directory. Probably you need to remove the old Podfile.lock file.
Now, when you rebuild your project, hopefully the issue will be fixed.

score 0 · Answer 8 · answered Nov 09 '20 at 11:33

0

I recently faced this issue but the offending class was a unit test class. It turned out that a pod reference in my podfile was not included in the test target.

answered Nov 09 '20 at 11:33

Kai

186
2
10

score 0 · Answer 9 · answered Jun 12 '22 at 15:07

0

I had added a new test target. I forgot to update my Podfile for the test target. Make sure you add your new target to Podfile. Run "pod deintegrate" and "pod install" after it.

answered Jun 12 '22 at 15:07

Hemanshu Liya

611
6
10

score 0 · Answer 10 · answered Mar 18 '23 at 19:25

0

After trying all of these and the suggestions here I reverted and made two simple changes. I added import Foundation to the test file and then I added the offending pod to my testing target in the podfile. That resolved the issue.

answered Mar 18 '23 at 19:25

Mark

765
8
12