Identical to #71764 except now it's on top of the engine change flutter/engine#22979

$ dart bin/run.dart -t hot_mode_dev_cycle_macos_target__benchmark
...
Task result:
{
  "success": true,

Description

macOS version of #51453. See details and discussion there.

Push linker and embedding logic into the tool so future changes (like distributing as an XCFramework, renaming FlutterMacOS.framework, etc) do not require changes in the user's project.

At some point FlutterMacOS.framework will ship with x86 and ARM slices. With this change, we will be able to introduce thinning (as iOS does) in the script without requiring a user project migration.

This change would also set us up to stop copying FlutterMacOS.framework to Flutter/ephemeral. On iOS, for example, the framework is copied directly from the artifacts directory to the BUILT_PRODUCTS_DIR so there's never a mismatch between a Release build and a Debug version of Flutter.

Changes

• Remove App.framework and FlutterMacOS.framework link step in template build phase.
• Remove App.framework and FlutterMacOS.framework from the framework embedding build phase.
• Add migrator to do this automatically based on the Xcode identifiers. I confirmed these are the original template identifiers introduced in Support create for macOS (app and plugin) #40851.
• Build the example and integration test macOS apps and see them migrate.
• Remove disable_input_output_paths from the generated Podfile, and from the example projects. Now that FlutterMacOS.framework isn't being technically emitted by a build phase, the Disable CocoaPods input and output paths in Xcode build phase and adopt new Xcode build system #33684 workaround is no longer necessary.

Future Documentation

• Add a macOS doc like https://flutter.dev/docs/development/ios-project-migration and include in the error message.
• Add a website note like Add tip to remove disable_input_output_paths from Podfile website#4019 that disable_input_output_paths can be deleted. We decided not to automatically migrate this for existing iOS projects.

Related Issues

Fixes #56581
Part of #70413
Will make #60113 easier.

Tests

macos_project_migration_test