Closed JordyLangen closed 1 year ago
Hi @JordyLangen,
If you remove the use_frameworks!
line altogether in your Podfile
, does this also address your issue? This was a manual step done for the Runner example project (shown here) and is something we will add as a migration step when updating to 3.0.0. Also, the use_frameworks
line is not required when importing the Braze Swift SDK (see native examples here).
I created a fork of the project and added
s.static_framework = true
on line 12 of ios/braze_plugin.podspec
This way there is no need to change the use_frameworks in the podFile
Hi @Icety,
Thanks for the suggestion. We will integrate the change directly in the podspec in the next release to save integrators from needing to do an additional migration step. When a new release is available, I'll respond to this thread.
In the meantime, please use the workarounds in this thread.
Thank you!
@Icety Can you link the fork you made? I tried to fork it with s.static_framework = true
but I'm facing Swift Compiler Error (Xcode): No such module 'Appboy_iOS_SDK'
.
Removing use_frameworks
from Podfile conflicts with other Google dependencies, didn't work for me.
Hi @JordyLangen @Icety @ggirotto,
We just released the Braze Flutter SDK version 3.0.1 which addresses the issues in this thread related to importing the static framework in the podspec. After updating to that version, you will no longer need to do a manual step to remove use_frameworks!
or to use use_frameworks! :linkage => :static
.
Thanks!
I'm getting the following error:
Changing
use_frameworks!
touse_frameworks! :linkage => :static
seems to be a workaround, would prefer to see a fix.