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

Question

I need to make swift static library for my requirement. I made swift static library which uses swift and Obj-c code. I have included Obj-c files via bridge file. I am able to compile swift static library without any error and get libMySwift.a file. I use Xcode9.3 with Swift4 to compile library.

I include libMySwift.a in obj-c project and also included obj-c compatible header to access my lib in the project. When I try to compile the project it give below warning and more than 200 errors.

Auto-Linking library not found for -lswiftSwiftOnoneSupport
Auto-Linking library not found for -lswiftCore
Auto-Linking library not found for -lswiftQuartzCore
Auto-Linking library not found for -lswiftCoreImage
Auto-Linking library not found for -lswiftCoreGraphics
Auto-Linking library not found for -lswiftObjectiveC
Auto-Linking library not found for -lswiftDispatch
Auto-Linking library not found for -lswiftMetal
Auto-Linking library not found for -lswiftFoundation
Auto-Linking library not found for -lswiftUIKit
Auto-Linking library not found for -lswiftDarwin
Auto-Linking library not found for -lswiftCoreFoundation

Please let me know if I am missing any steps or need to add anything.

Solution 1

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

Solution 2

I've got the same error on my demo project when added first Swift file in my pod compiled as static library. For me solution was simple - just added empty Swift file to my demo project which was previously in Objective-C only. This solved all linker errors.

Comments

[Antony Raphel]

by creating Objective-C bridging Header is resolved the issue.

[fct]

Sweet. Kind of elegant solution. Xcode shows as warnings not errors. This solution fixed warnings and all erros caused by warnings.

[jdnichollsc]

but the issue still present if you remove that swift file later :/

[Naveen Raju]

Thank you so much, it solved my issue. By the way, I'm trying to build using react-native.

[romin21]

I've been spending two days trying to fix this issue and you saved me!

[Tuan Nguyen]

why i cant see Confirm Create Bridging Header dialog?

[Kamil Lewandowski]

@TuanNguyen just create an empty header file by yourself. In the same directory and targets as your empty swift file. It worked for me.

[Curtis]

I did this and still get the same error. Trying to ad adMob. Could not find auto-linked framework 'FBLPromises'

[lambinator]

I had to perform this again when upgrading from xcode 11 to 12.

[papacostas]

if a bridging header dialog doesn't prompt, follow this. (to remove old one) stackoverflow.com/questions/31716413/…

[Dan]

For me, with an ejected Expo/react-native project, I simply added the empty swift file and it worked. No bridge dialog needed. Thanks for this!