Skip to content

Conversation

@vashworth
Copy link
Contributor

@vashworth vashworth commented Nov 21, 2025

The main purpose of this PR is to add the Flutter framework as a Swift Package dependency. As such, Xcode will now handle the copying, thinning, and codesigning of the framework and therefore the Flutter Xcode Run Scripts shouldn't.

This will allow plugins to declare a dependency on the Flutter framework package and eliminate the need for the Pre-Action "prepare" script.

This PR does not technically make the Flutter framework a local package override, that will be added in a follow up PR: #179512

This change includes:

  • Generation of the FlutterFramework swift package (this will generate a Package.swift and symlink to the Flutter framework in the artifact cache)
    Screenshot 2025-12-04 at 4 54 43 PM
  • Adding the FlutterFramework as a dependency to the FlutterGeneratedPluginSwiftPackage (which the the Swift package the Xcode project has a dependency on)
    Screenshot 2025-12-04 at 4 55 13 PM

Change to Flutter Run Scripts

Flutter currently has 3 Xcode Run Scripts:

  • prepare (happens in a scheme pre-action)
    • [PREVIOUS] Via flutter assemble - copies the Flutter framework from engine build cache to BUILT_PRODUCTS_DIR
    • [NEW] Same as previous except skips codesigning. This is still included to accommodate plugins that don't have a dependency declared on the Flutter framework.
  • build (happens in first Run Script in the Xcode build phases that happens before compiling)
    • [PREVIOUS] Via flutter assemble - copies, thins, and codesigns Flutter framework into BUILT_PRODUCTS_DIR
    • [NEW] Is skipped, Xcode now does this
  • embed_and_thin (happens in second Run Script in the Xcode build phases after compiling, linking, and embedding)
    • [PREVIOUS] Copies Flutter framework from BUILT_PRODUCTS_DIR to TARGET_BUILD_DIR
    • [NEW]
      • Validates Flutter framework in BUILT_PRODUCTS_DIR & TARGET_BUILD_DIR (which would have been put there by Xcode via SwiftPM) matches the Flutter framework in the engine cache.
      • If it matches, do not copy. Xcode now does this.
      • If it doesn't:
        • Call flutter assemble to copy the correct Flutter framework into BUILT_PRODUCTS_DIR
        • Then copy from BUILT_PRODUCTS_DIR to TARGET_BUILD_DIR.

Fixes #166489.

Pre-launch Checklist

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

@github-actions github-actions bot added a: tests "flutter test", flutter_test, or one of our tests platform-ios iOS applications specifically tool Affects the "flutter" command-line tool. See also t: labels. framework flutter/packages/flutter repository. See also f: labels. a: desktop Running on desktop f: integration_test The flutter/packages/integration_test plugin team-ios Owned by iOS platform team labels Nov 21, 2025
Comment on lines +414 to +418
final String? sdkRoot = environment['SDKROOT']?.toLowerCase();
if (sdkRoot == null || !sdkRoot.contains('iphone')) {
return null;
}
final bool simulatorSDK = sdkRoot.contains('simulator');
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is mimicking:

EnvironmentType? environmentTypeFromSdkroot(String sdkroot, FileSystem fileSystem) {
// iPhoneSimulator.sdk or iPhoneOS.sdk
final String sdkName = fileSystem.path.basename(sdkroot).toLowerCase();
if (sdkName.contains('iphone')) {
return sdkName.contains('simulator') ? EnvironmentType.simulator : EnvironmentType.physical;
}
assert(false);
return null;
}

Comment on lines +419 to +427
for (final FileSystemEntity entity in xcframework.listSync()) {
final String platformBaseName = Uri.parse(entity.path).pathSegments.last;
if (entity is Directory && platformBaseName.startsWith('ios-')) {
final bool isSimulatorDirectory = platformBaseName.endsWith('-simulator');
if (simulatorSDK == isSimulatorDirectory) {
return File('${entity.path}/${platform.infoPlistPath}');
}
}
}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is mimicking:

for (final Directory platformDirectory
in xcframeworkDirectory.listSync().whereType<Directory>()) {
if (!platformDirectory.basename.startsWith('ios-')) {
continue;
}
// ios-x86_64-simulator, ios-arm64_x86_64-simulator, or ios-arm64.
final bool simulatorDirectory = platformDirectory.basename.endsWith('-simulator');
if ((environmentType == EnvironmentType.simulator && simulatorDirectory) ||
(environmentType == EnvironmentType.physical && !simulatorDirectory)) {
return platformDirectory;
}
}
throwToolExit('No iOS frameworks found in ${xcframeworkDirectory.path}');

Comment on lines +429 to +434
for (final FileSystemEntity entity in xcframework.listSync()) {
final String platformBaseName = Uri.parse(entity.path).pathSegments.last;
if (entity is Directory && platformBaseName.startsWith('macos-')) {
return File('${entity.path}/${platform.infoPlistPath}');
}
}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is mimicking:

final Directory? platformDirectory = xcframeworkDirectory
.listSync()
.whereType<Directory>()
.where((Directory platformDirectory) => platformDirectory.basename.startsWith('macos-'))
.firstOrNull;
if (platformDirectory == null) {
throwToolExit('No macOS frameworks found in ${xcframeworkDirectory.path}');
}

@vashworth vashworth marked this pull request as ready for review December 5, 2025 19:31
@vashworth vashworth requested a review from a team as a code owner December 5, 2025 19:31
Copy link
Contributor

@stuartmorgan-g stuartmorgan-g left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor comments, but LGTM. The large caveat is that I have limited familiarity with this part of the code, so am unlikely to notice subtle implementation mistakes, but the structure makes sense to me and matches my understanding of the design doc, and the tests look thorough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

a: desktop Running on desktop a: tests "flutter test", flutter_test, or one of our tests f: integration_test The flutter/packages/integration_test plugin framework flutter/packages/flutter repository. See also f: labels. platform-ios iOS applications specifically team-ios Owned by iOS platform team tool Affects the "flutter" command-line tool. See also t: labels.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[SwiftPM] Flutter generates a local Flutter framework swift package

2 participants