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

Question

I have an app built with Swift with pods(firebase). I have 18 triangle and 100 red 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 linker link static libraries with errors? iOS

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

Answer 1

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.