google's services "sabotage" local build

Troubleshooting

when I try to build using flutter build ios on my local computer, I am unable to install pod:

   W/"65d-mjv8UNq4TdpVq3/Rw685EgeY6lc"

      CDN: trunk Relative path downloaded: Specs/3/5/e/Google-Maps-iOS-Utils/6.0.0/Google-Maps-iOS-Utils.podspec.json, save ETag:

      W/"82c-z+agI5x8pjS34AGtBZpnBxQ9yNw"

      CDN: trunk Relative path: Specs/3/5/e/Google-Maps-iOS-Utils/6.0.0/Google-Maps-iOS-Utils.podspec.json modified during this run! Returning

      local

      CDN: trunk Relative path: Specs/0/3/5/Firebase/11.0.0/Firebase.podspec.json modified during this run! Returning local

    [!] CocoaPods could not find compatible versions for pod "Firebase/Messaging":

      In Podfile:

        Firebase/Messaging (= 11.00.0)

        firebase_messaging (from .symlinks/plugins/firebase_messaging/ios) was resolved to 15.1.1, which depends on

          Firebase/Messaging (= 11.0.0)

    None of your spec sources contain a spec satisfying the dependencies: Firebase/Messaging (= 11.00.0), Firebase/Messaging (= 11.0.0).

    You have either:

     * out-of-date source repos which you can update with pod repo update or with pod install --repo-update.

     * mistyped the name or version.

     * not added the source repo that hosts the Podspec to your Podfile.

    resolve_dependencies'

...

Error: CocoaPods's specs repository is too out-of-date to satisfy dependencies.

To update the CocoaPods specs, run:

  pod repo update

Error running pod install

What have you tried so far?

For hours I have been debugging it using claude, but it's an endless story involving the correction of packages' versions and their dependencies, which sometimes contradict each other.

I would much rather understand what the hack happens on FF's website that causes this. Based on the error message, it seems like the issue is with the Google Maps plugin. I will try to remove it now, but I would be happy if someone could tell me what could be the causes (because I suspect there would be more features that will lead to this error).

Did you check FlutterFlow's Documentation for this topic?
Yes
2
6 replies