Cocapods не может найти совместимую версию для Firebase

Question

Я только что перешел на Mac с Windows 10. Я выпустил версию Android своего приложения Flutter для Android. Сейчас я работаю над IOS-версией моего приложения Flutter. Когда я пытаюсь запустить свое приложение на Mac, я получаю сообщение об ошибке ниже.

[!] CocoaPods could not find compatible versions for pod "Firebase/Core":
  In Podfile:
  cloud_firestore (from `.symlinks/plugins/cloud_firestore/ios`) was resolved to 0.0.1, which depends on
  Firebase/Core

  mlkit (from `.symlinks/plugins/mlkit/ios`) was resolved to 0.8.3, which depends on
  Firebase/Core (~> 5.11.0)

  CocoaPods could not find compatible versions for pod "Firebase/CoreOnly":
  In Podfile:
  firebase_auth (from `.symlinks/plugins/firebase_auth/ios`) was resolved to 0.0.1, which depends on
  Firebase/Auth (~> 5.19) was resolved to 5.19.0, which depends on
  Firebase/CoreOnly (= 5.19.0)

  mlkit (from `.symlinks/plugins/mlkit/ios`) was resolved to 0.8.3, which depends on
  Firebase/Core (~> 5.11.0) was resolved to 5.11.0, which depends on
  Firebase/CoreOnly (= 5.11.0)

  CocoaPods could not find compatible versions for pod "FirebaseCore":
  In Podfile:
  mlkit (from `.symlinks/plugins/mlkit/ios`) was resolved to 0.8.3, which depends on
  Firebase/Core (~> 5.11.0) was resolved to 5.11.0, which depends on
  Firebase/CoreOnly (= 5.11.0) was resolved to 5.11.0, which depends on
  FirebaseCore (= 5.1.6)

  mlkit (from `.symlinks/plugins/mlkit/ios`) was resolved to 0.8.3, which depends on
  Firebase/Core (~> 5.11.0) was resolved to 5.11.0, which depends on
  FirebaseAnalytics (= 5.3.0) was resolved to 5.3.0, which depends on
  FirebaseCore (~> 5.1)

Answer 1

Я исправил это, выполнив ручное 'pod update' & Flutter 'Packages get' ...

В терминале измените каталог на:

cd FLUTTER_PROJECT_FOLDER_PATH/ios

Выполнитьpod update:

pod update

Запустите пакеты Flutter get

// In Android Studio, open 'pub spec.yaml', press 'Packages get' 

• Тогда вы сможете собрать на iOS

• Первая сборка заняла примерно на 3 минуты больше времени, чем обычно, но при следующих сборках возвращалась к нормальной.