Edit 4
for those who improve your flutter and cocoa pods and flutter plugins and nonetheless have this challenge,
A very easy and environment friendly resolution is to edit your Podfile
platform :ios, '14.0'
# CocoaPods analytics sends community stats synchronously affecting flutter construct latency.
ENV['COCOAPODS_DISABLE_STATS'] = 'true'
mission 'Runner', {
'Debug' => :debug,
'Profile' => :launch,
'Launch' => :launch,
}
def flutter_root
generated_xcode_build_settings_path = File.expand_path(File.be part of('..', 'Flutter', 'Generated.xcconfig'), __FILE__)
until File.exist?(generated_xcode_build_settings_path)
elevate "#{generated_xcode_build_settings_path} should exist. In the event you're working pod set up manually, ensure flutter pub get is executed first"
finish
File.foreach(generated_xcode_build_settings_path) do |line|
matches = line.match(/FLUTTER_ROOT=(.*)/)
return matches[1].strip if matches
finish
elevate "FLUTTER_ROOT not present in #{generated_xcode_build_settings_path}. Strive deleting Generated.xcconfig, then run flutter pub get"
finish
require File.expand_path(File.be part of('packages', 'flutter_tools', 'bin', 'podhelper'), flutter_root)
flutter_ios_podfile_setup
goal 'Runner' do
use_frameworks!
use_modular_headers!
flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
goal 'RunnerTests' do
inherit! :search_paths
finish
finish
post_install do |installer|
installer.pods_project.targets.every do |goal|
goal.build_configurations.every do |config|
if Gem::Model.new(config.build_settings['IPHONEOS_DEPLOYMENT_TARGET']) < Gem::Model.new('11.0')
config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '11.0'
finish
finish
flutter_additional_ios_build_settings(goal)
finish
finish
The adjustments that I made, is to outline the platform ios model as minimal to 14, and ensure all of the pods have not less than 11 minimal model, in any other case ignore it, the adjustments are to the second line and the post_install
Edit 3:
The difficulty come again once more within the flutter 3.10
with some packages, so please use the best way I present bellow
Edit 2:
Strive replace flutter for the reason that challenge ought to be fastened in 3.7.11
flutter improve
I fastened the difficulty, regardless that I am undecided if that may be a good resolution,
run the next:
flutter clear
flutter pub get
cd ios/
pod deintegrate
pod set up
pod repo replace
pod set up (once more)
Simply open the ios mission contained in the flutter mission in Xcode, go to Pods within the folders (recordsdata) tab, go to the targets, go to the targets (it pod I assume, one dependency) that causes the difficulty, in my case FMDB and App auth, improve the minimal deployments for each from the present model (in my case 9.0) to 13.0 and take a look at run the app once more by construct it and run it in Xcode or utilizing flutter run with the chosen ios gadget, and the difficulty ought to be gone
nonetheless generally whenever you clear the mission in flutter (utilizing flutter clear), it is going to reset these adjustments, or whenever you delete the pods and deintegrate Cocapods and re-install the app, all of the adjustments shall be reverted again to the default, it not likely an environment friendly resolution, however not less than you possibly can run the app
and if the difficulty continues to be exists, replace the minimal deployment for the pods goal once more and run the app utilizing Xcode, for those who nonetheless have the difficulty, check out the opposite solutions or you possibly can attempt replace cocapods by
sudo gem set up cocoapods
in case your mac machine is apple silicon (m1, m2), you additionally want run
sudo gem uninstall ffi && sudo gem set up ffi -- --enable-libffi-alloc
The official documentation mentioned that
Edit: This resolution thought come to me, all due to @Siyu
If you’re from the future, you may wish to attempt to improve the packages and cocapods, flutter and so forth…
