Why linker link static libraries with errors? iOS

Question

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

1) I create a framework with Swift and Objective-C classes.

2) The main logic was stored in the Swift file. For example the class with a method that calls NSLog("Swift log was called").

3) Objective-C file has a class that has a method in which I create an instance of Swift class and call Swift-log method.

4) 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.

Answer 1

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

This should fix the problem

Answer 2

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

1. Adding a new Swift file and a Brigde header:

1) File -> New -> File

2) Select Swift File

3) Confirm Create Bridging Header

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

Answer 3

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

Answer 4

For XCode 11 beta 4 Library Search Paths should be:

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

Answer 5

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

Answer 6

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

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

Answer 7

An update to Alex's answer:

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

1. Adding a new Swift file and a Brigde header:

1. File -> New -> File

2. Select Swift File

3. Confirm Create Bridging Header

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

Answer 8

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.

1. $(SDKROOT)/usr/lib/swift
2. $(TOOLCHAIN_DIR)/usr/lib/swift/$(PLATFORM_NAME)
3. $(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.

Answer 9

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 :)

Answer 10

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

Answer 11

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

Answer 12

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:

Answer 13

Xcode 12.5, React Native. Adding iOS Widget or Apple Watch App caused linking errors.

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

Answer 14

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

Answer 15

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.

Answer 16

https://stackoverflow.com/a/56187043/1848929 works like a charm.

Just create empty swift file on your project then build your project. Thats it.

Answer 17

@AlVelig 's answer worked for me.

My case is a Flutter Project, and I add a package (searchable_dropdown), which is write by Swift.

The output warning is:

Could not find auto-linked library 'swiftObjectiveC'

Could not find auto-linked library 'swiftCore'

......

Answer 18

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

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

end

Answer 19

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 [email protected]

(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.

Answer 20

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.