Closed pneves001 closed 5 years ago
Most likely related to https://github.com/flutter/flutter/issues/16049
Will need to re-investigate
I haven't even added any code yet to use the library in my code. This is coming up when I install the package.
After creating a new flutter app with flutter create
, and adding the flutter_sodium
dependency in pubspec.yaml
, you'll need to manually edit ios/Podfile
:
use_frameworks!
as first line in target 'Runner' do
config.build_settings['SWIFT_VERSION'] = '3.2'
after line config.build_settings['ENABLE_BITCODE'] = 'NO'
in post_install do |installer|
Podfile.lock
, recompile and all should be goodSee also the attached Podfile for reference. I'm aware this is not ideal, but this is a one-time setup.
Eventually this issue needs to be addressed in the flutter tooling.
Taken from https://github.com/flutter/flutter/issues/16049#issuecomment-382629492
FYI: these manual steps are still required in Flutter v0.6.0
FYI: these manual steps are still required in Flutter v0.8.2 (preview 2)
Additionally, with Xcode 10 the iOS build of your flutter app will fail as well. See https://github.com/firstfloorsoftware/flutter_sodium/issues/9 for details
FYI: in Flutter 1.0 the following workaround is still required when creating a Flutter iOS app using ObjC (which is the default).
After creating a new flutter app with flutter create
, and adding the flutter_sodium
dependency in pubspec.yaml
, you'll need to manually edit ios/Podfile
:
use_frameworks!
as first line in target 'Runner' do
config.build_settings['SWIFT_VERSION'] = '4.2'
after line config.build_settings['ENABLE_BITCODE'] = 'NO'
in post_install do |installer|
Podfile.lock
, recompile and all should be goodStill required in v1.9.8-pre.3
?