Undefined symbols for architecture x86_64 about drift-sdk-ios

[eoinoconnell]

Hello, how strange. Does this happen when using the example app in the repo? What version of the SDK are you using? I assume 1.8.4 is your cocoa pods version

[vuhoangha]

No, I'm using my project. I used version 2.2.11 of drift-sdk-ios. My cocoa pods version is 1.8.4

[eoinoconnell]

Can you please try the example project to see if it happens there also?

It sounds like it might be a conflict with dependencies

[vuhoangha]

I try running the example but I see errors

[eoinoconnell]

Just to confirm you opened the workspace and not the project file ye?

[vuhoangha]

I am not an ios programmer, I am a react native developer. So there are many things I don't understand about ios. If you need me to provide any additional information so you can spot the error, I'd be happy to. Thank you!

[vuhoangha]

Just to confirm you opened the workspace and not the project file ye?

I went to SDKExample folder and run "Pod install". Then I opened SDKExample.xcworkspace and run it. Is it right?

[eoinoconnell]

Yeah that should be it. Have you made any changes to your system or anything. It seems to be not able to find String.swift which seems rather strange. Do you have a custom installation of swift on your machine?

[vuhoangha]

I add lines on file Podfile

   pod 'SVProgressHUD', :modular_headers => true
   pod 'Drift', '~> 2.2.11'

Then I deleted Pods folder, ran "pod install" and built it. I tried running on 3 different computer but I got the same error

[eoinoconnell]

is there any other dependencies in your pod file? how come you are using modular_headers for the progress hud?

[vuhoangha]

I added modular_headers because I got an error when I ran pod install

[!] The following Swift pods cannot yet be integrated as static libraries:

The Swift pod `Drift` depends upon `SVProgressHUD`, which does not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set `use_modular_headers!` globally in your Podfile, or specify `:modular_headers => true` for particular dependencies.

[eoinoconnell]

Ah ok, do you have use_frameworks! at the top of your podfile? If not could you add it, remove the modular_headers and try again?

[Phu-Hoang]

Currently most libraries discourage using use_frameworks!. Do you have any other solutions?

[eoinoconnell]

Hi, currently we only support use_frameworks I'm afraid

[eoinoconnell]

Hi, as of 2.4.0 we now support static building the library so you should no longer need use_frameworks!