-
Notifications
You must be signed in to change notification settings - Fork 174
xcode 11.0 use pod build err " Showing All Messages Undefined symbol: __swift_FORCE_LOAD_$_swiftCompatibilityDynamicReplacements" and " Showing All Messages Undefined symbol: __swift_FORCE_LOAD_$_swiftCompatibility50" #80
Comments
project->build settings->search path->Library Search Paths add Code
build success |
Could you provide more details about your setup? Xcode version, CocoaPods version, how are you integrating SwiftMonkey and SwiftMonkeyPaws. Ideally, could you provide a sample project? Also Does the sample provided with the framework work for you? |
I have the same error with Xcode 11.2.1, cocoapods (1.8.4) |
Create an Empty Swift file using Xcode, such as named Void.swift, and every issue will be solved by Xcode automatically. If you want to know what Xcode has done, submit the code before creating the file, and check the changes after creating the file. |
Is there any way to fix it with out creating empty Swift file? |
Then remove the empty file as you wish. |
Thanks for the answer, but I'd like to know how dose it work? |
you saved my day, Thank you man! |
It works for me too ! Thanks buddy but yeah, why ? |
It is great solution. |
in which folder we have to create the file ?? |
i also have same doubt.. did u find answer? |
This function perfectly, but why works? |
This is the correct solution eventually in my case, but there is one more detail I found out which I think worth to mention. |
You need to create in the main project folder, in the same folder as the AppDelegate file. |
@ownself, did you ever find a solution to this problem? Thanks! |
So far for us, we found one way to deal it, which you need to manually copy the *.a file into your framework project and explicitly link with it. That will make sure no matter which version of XCode they use for their project, when they link with your framework it will always link with your local copied *.a library file. |
You are the real saver. Thanks a lot. |
Figured this out. There is a new library in Xcode 12 that needs to be added to the Link Binary with Libraries phase call libSwiftWebKit.tbd. Error went away after adding this. |
what the hell is this sorcery |
😂😂 hours wasted only to find out this is the fix. Wow 🤷🏻 |
out of curiosity, do we know if it will ever be safe to remove the Void.swift file again? or do we just accept that it will stay there for the project to work? |
Xcode 13.1: In my case, |
creating an empty swift file solved the issue for me. any explanations? 😳😳😂 |
Alternate for those who already have bridging header: |
@hstdt I have the same problem, did you solve it? |
Yep, just running this solved my issue:
If you still have the Xcode project built, you will need to reinstall the dependencies in the current project:
|
What?? I mean how does it work?? |
If you want to know what Xcode has done, submit the code before creating the file, and check the changes after creating the file. |
building err
The text was updated successfully, but these errors were encountered: