Repository navigation
Remove use_modular_headers! from Swift Podfiles #156259
Description
Background
We added use_modular_headers! to our Podfiles as we originally planned to phase out use_frameworks! (see #42204). However, our plans have now changed and we are instead phasing out CocoaPods entirely in favor of Swift Package Manager.
CocoaPods's use_frameworks! and use_modular_headers! are two different overlapping options that should not be used together. This change removes the use_modular_headers! from the macOS Podfile and the iOS Swift Podfile (the iOS Objective-C template was recently deprecated #155867).
Work
Remove use_modular_headers! from all Swift Podfiles.
Activity
navaronbracke commentedon Oct 5, 2024
Would including a project migrator for apps be a good thing here? And do we need to modify the SPM migration docs to tell developers to remove it there as well?
loic-sharma commentedon Oct 7, 2024
@navaronbracke While in theory this change is necessary, in practice we're not aware of any problems caused by this today. However, we are concerned that an automatic migration could break apps if not done well.
For now, we'll fix new apps but not existing apps. Long-term, all existing apps will migrate to SwiftPM and won't be affected by this problem (removing
use_modular_headers!is not a prerequisite for the SwiftPM migration). We want to put all our resources on getting the SwiftPM migration right :)Let me know if you have any concerns!
Clarify when `override: no versioning needed` label should be applied (…
Remove use_modular_headers! from Swift Podfiles (#156257)
Remove use_modular_headers! from Podfiles (#7796)
github-actions commentedon Dec 19, 2024
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.