Menu

Flutter Is Leaving CocoaPods. Our CI Isn’t Ready
📰

Flutter Is Leaving CocoaPods. Our CI Isn’t Ready

DEV Community: ios·Paul-S·3 days ago
#zbH2D2Ml
#devtoios#devto#dev#flutter#build
Reading 0:00
15s threshold

Our iOS pipeline was green.

That was the problem.

After upgrading to Flutter 3.50, every local build printed a warning about Swift Package Manager. The CI job printed no warning, installed pods from cache and produced a valid archive.

Nothing had failed, but the pipeline had not tested the dependency path Flutter was moving toward.

It had tested the fallback.

The Build That Hid the Migration

The relevant part of the CI workflow looked familiar:

- name : Install CocoaPods run : sudo gem install cocoapods

- name : Restore Pods cache uses : actions/cache@v4 with : path : | ios/Pods ~/.cocoapods key : pods-${{ hashFiles('ios/Podfile.lock') }}

- name : Install pods run : | cd ios pod install

- name : Build iOS run : flutter build ios --release --no-codesign

Enter fullscreen mode

Exit fullscreen mode

This pipeline was dependable because it made CocoaPods available before Flutter needed it.

It also meant we could not answer a more important question:

Can this application build when Swift Package…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.