Add Flutter as a Swift Package dependency by vashworth · Pull Request #178931 · flutter/flutter

vashworth · 2025-11-21T17:09:49Z

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)
Adding the FlutterFramework as a dependency to the FlutterGeneratedPluginSwiftPackage (which the the Swift package the Xcode project has a dependency on)

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

I read the Contributor Guide and followed the process outlined there for submitting PRs.
I read the Tree Hygiene wiki page, which explains my responsibilities.
I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
I signed the CLA.
I listed at least one issue that this PR fixes in the description above.
I updated/added relevant documentation (doc comments with ///).
I added new tests to check the change I am making, or this PR is test-exempt.
I followed the breaking change policy and added Data Driven Fixes where supported.
All existing and new tests are passing.

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.

…er_dependency

vashworth · 2025-12-05T19:28:38Z

+        final String? sdkRoot = environment['SDKROOT']?.toLowerCase();
+        if (sdkRoot == null || !sdkRoot.contains('iphone')) {
+          return null;
+        }
+        final bool simulatorSDK = sdkRoot.contains('simulator');


This is mimicking:

flutter/packages/flutter_tools/lib/src/macos/xcode.dart

Lines 285 to 293 in f63cf73

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;

}

vashworth · 2025-12-05T19:29:12Z

+        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}');
+            }
+          }
+        }


This is mimicking:

flutter/packages/flutter_tools/lib/src/artifacts.dart

Lines 954 to 966 in f63cf73

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}');

vashworth · 2025-12-05T19:29:41Z

+        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}');
+          }
+        }


This is mimicking:

flutter/packages/flutter_tools/lib/src/artifacts.dart

Lines 1026 to 1033 in f63cf73

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}');

}

stuartmorgan-g

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.

jmagman · 2026-01-02T22:20:21Z

@vashworth is this ready to merge?

…er_dependency

…8931)

This PR creates a FlutterFramework swift package with no real content. This is a placeholder so that plugins may add a dependency on the FlutterFramework in their Package.swift before #178931 lands in stable. See go/swiftpm-flutter-release. Impacted Users: Flutter iOS with SwiftPM feature flag enabled Impact Description: Allows plugins to add a dependency on the FlutterFramework in their Package.swift. Workaround: See Problem 2 alternatives in [go/swiftpm-flutter-release](http://goto.google.com/swiftpm-flutter-release) Risk: This PR by itself is low risk. It just generates a couple files in an ephemeral directory. It only is actually used if a plugin adds a dependency on it in it's Package.swift. If a plugin does this, it's still low risk since it's basically just an empty Swift package. It's also behind a feature flag (`flutter config --enable-swift-package-manager`), which can be disabled. Test Coverage: Yes Validation Steps: - `flutter config --enable-swift-package-manager` - `flutter create my_plugin && cd my_plugin/example` - Add `FlutterFramework` to Package.swift (see [example](https://github.com/flutter/flutter/blob/master/packages/integration_test/ios/integration_test/Package.swift#L15-L21)) - `flutter build ios` **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). 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.

This PR keeps the FlutterFramework swift package introduced in #178931, but removes the Flutter.xcframework as a dependency, essentially making it empty. As such, it also restores the build scripts to copy and codesign the framework instead of letting Xcode do it. This is a temporary solution while we decide a long-term strategy: [go/flutter-ios-privacy-impacting-sdks-codesign-requirement](http://goto.google.com/flutter-ios-privacy-impacting-sdks-codesign-requirement) Fixes #181630. ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. 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](https://developers.google.com/gemini-code-assist/docs/review-github-code). 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.  [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md

This PR keeps the FlutterFramework swift package introduced in flutter#178931, but removes the Flutter.xcframework as a dependency, essentially making it empty. As such, it also restores the build scripts to copy and codesign the framework instead of letting Xcode do it. This is a temporary solution while we decide a long-term strategy: [go/flutter-ios-privacy-impacting-sdks-codesign-requirement](http://goto.google.com/flutter-ios-privacy-impacting-sdks-codesign-requirement) Fixes flutter#181630. ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. 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](https://developers.google.com/gemini-code-assist/docs/review-github-code). 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.  [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md

This PR creates a FlutterFramework swift package with no real content. This is a placeholder so that plugins may add a dependency on the FlutterFramework in their Package.swift before flutter#178931 lands in stable. See go/swiftpm-flutter-release. Impacted Users: Flutter iOS with SwiftPM feature flag enabled Impact Description: Allows plugins to add a dependency on the FlutterFramework in their Package.swift. Workaround: See Problem 2 alternatives in [go/swiftpm-flutter-release](http://goto.google.com/swiftpm-flutter-release) Risk: This PR by itself is low risk. It just generates a couple files in an ephemeral directory. It only is actually used if a plugin adds a dependency on it in it's Package.swift. If a plugin does this, it's still low risk since it's basically just an empty Swift package. It's also behind a feature flag (`flutter config --enable-swift-package-manager`), which can be disabled. Test Coverage: Yes Validation Steps: - `flutter config --enable-swift-package-manager` - `flutter create my_plugin && cd my_plugin/example` - Add `FlutterFramework` to Package.swift (see [example](https://github.com/flutter/flutter/blob/master/packages/integration_test/ios/integration_test/Package.swift#L15-L21)) - `flutter build ios` **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). 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.

This PR keeps the FlutterFramework swift package introduced in flutter/flutter#178931, but removes the Flutter.xcframework as a dependency, essentially making it empty. As such, it also restores the build scripts to copy and codesign the framework instead of letting Xcode do it. This is a temporary solution while we decide a long-term strategy: [go/flutter-ios-privacy-impacting-sdks-codesign-requirement](http://goto.google.com/flutter-ios-privacy-impacting-sdks-codesign-requirement) Fixes flutter/flutter#181630. ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. 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](https://developers.google.com/gemini-code-assist/docs/review-github-code). 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.  [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md

Flutter does not require a plugin's Package.swift to depend on the FlutterFramework SwiftPM wrapper: flutter_tools only emits a warning (validatePluginSupportsSwiftPackageManager in darwin_dependency_management.dart) when it's missing, and xcode_backend.dart keeps the legacy embed/codesign run-script path ("to accommodate plugins that don't have a dependency declared on the Flutter framework") for exactly this case. oidc_ios 0.8.0+3 itself shipped with an empty Package.swift dependencies list and compiled `import Flutter` fine, proving the dependency was never load-bearing. The FlutterFramework mechanism also doesn't exist before Flutter 3.44.0 (flutter/flutter#178931), so the floor this previously raised to Flutter >=3.41.0 / Dart ^3.11.0 was both unnecessary and wrong - and it broke the 0.8.x release branch's CI, which still pins Flutter 3.35.4 in .github/actions/flutter_base. Drop the FlutterFramework dependency, restore the original SDK floor (sdk >=3.5.0 <4.0.0, flutter >=3.22.0) from the 0.8.0+3 tag, and revert the test file reformat that the floor bump had required. The Package.swift relocation, Sources/ layout, and podspec path fix from the original backport are kept, since those are the actual fix for Flutter not finding the plugin's SwiftPM manifest. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_0126i8ymDVXbifp6LrbCiyQL

Flutter does not require a plugin's Package.swift to depend on the FlutterFramework SwiftPM wrapper: flutter_tools only emits a warning (validatePluginSupportsSwiftPackageManager in darwin_dependency_management.dart) when it's missing, and xcode_backend.dart keeps the legacy embed/codesign run-script path ("to accommodate plugins that don't have a dependency declared on the Flutter framework") for exactly this case. oidc_macos 0.8.0+3 itself shipped with an empty Package.swift dependencies list and compiled `import FlutterMacOS` fine, proving the dependency was never load-bearing. The FlutterFramework mechanism also doesn't exist before Flutter 3.44.0 (flutter/flutter#178931), so the floor this previously raised to Flutter >=3.41.0 / Dart ^3.11.0 was both unnecessary and wrong - and it broke the 0.8.x release branch's CI, which still pins Flutter 3.35.4 in .github/actions/flutter_base. Drop the FlutterFramework dependency, restore the original SDK floor (sdk >=3.5.0 <4.0.0, flutter >=3.22.0) from the 0.8.0+3 tag, and revert the test file reformat that the floor bump had required. The Package.swift relocation, Sources/ layout, and podspec path fix from the original backport are kept, since those are the actual fix for Flutter not finding the plugin's SwiftPM manifest. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_0126i8ymDVXbifp6LrbCiyQL

Add Flutter as a Swift Package dependency

46366e5

vashworth and others added 5 commits November 21, 2025 14:55

fix tests

cde7a2a

++

6d47031

++

38bbd73

Merge remote-tracking branch 'upstream/main' into swiftpm_local_flutt…

b71b75e

…er_dependency

Merge branch 'master' into swiftpm_local_flutter_dependency

4258f2b

vashworth commented Dec 5, 2025

View reviewed changes

vashworth marked this pull request as ready for review December 5, 2025 19:31

vashworth requested a review from a team as a code owner December 5, 2025 19:31

vashworth requested a review from stuartmorgan-g December 5, 2025 19:31

stuartmorgan-g approved these changes Dec 10, 2025

View reviewed changes

renaming, clean up, better logs

776faa7

vashworth and others added 2 commits January 5, 2026 11:01

Merge branch 'master' into swiftpm_local_flutter_dependency

3db482e

Merge remote-tracking branch 'upstream/main' into swiftpm_local_flutt…

cbeb608

…er_dependency

vashworth added the autosubmit Merge PR when tree becomes green via auto submit App label Jan 13, 2026

auto-submit Bot added this pull request to the merge queue Jan 13, 2026

Merged via the queue into flutter:master with commit d316469 Jan 13, 2026
142 checks passed

flutter-dashboard Bot removed the autosubmit Merge PR when tree becomes green via auto submit App label Jan 13, 2026

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Jan 14, 2026

d316469 Add Flutter as a Swift Package dependency (flutter/flutter#17…

ad37256

…8931)

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Jan 19, 2026

d316469 Add Flutter as a Swift Package dependency (flutter/flutter#17…

fa1dba3

…8931)

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Jan 20, 2026

d316469 Add Flutter as a Swift Package dependency (flutter/flutter#17…

952d67f

…8931)

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Jan 20, 2026

d316469 Add Flutter as a Swift Package dependency (flutter/flutter#17…

4dce829

…8931)

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Jan 20, 2026

d316469 Add Flutter as a Swift Package dependency (flutter/flutter#17…

33884da

…8931)

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Jan 20, 2026

d316469 Add Flutter as a Swift Package dependency (flutter/flutter#17…

bad0b5a

…8931)

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Jan 20, 2026

d316469 Add Flutter as a Swift Package dependency (flutter/flutter#17…

0c8fb90

…8931)

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Jan 21, 2026

d316469 Add Flutter as a Swift Package dependency (flutter/flutter#17…

c9a2c0c

…8931)

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Jan 21, 2026

d316469 Add Flutter as a Swift Package dependency (flutter/flutter#17…

568b56c

…8931)

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Jan 21, 2026

d316469 Add Flutter as a Swift Package dependency (flutter/flutter#17…

99fa3b3

…8931)

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Jan 22, 2026

d316469 Add Flutter as a Swift Package dependency (flutter/flutter#17…

65f0baf

…8931)

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Jan 22, 2026

d316469 Add Flutter as a Swift Package dependency (flutter/flutter#17…

7f141c1

…8931)

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Jan 22, 2026

d316469 Add Flutter as a Swift Package dependency (flutter/flutter#17…

8f5b5c7

…8931)

tarrinneal mentioned this pull request Jan 22, 2026

Flutter/Packages "Mac_arm64 macos_platform_tests master" codesign failure #181056

Closed

1 of 4 tasks

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Jan 23, 2026

d316469 Add Flutter as a Swift Package dependency (flutter/flutter#17…

bb099b0

…8931)

This was referenced Jan 27, 2026

Generate Flutter framework swift package #181554

Closed

Generate Flutter framework swift package #181578

Merged

vashworth mentioned this pull request Jan 30, 2026

Remove the Flutter.xcframework as a swift dependency #181739

Merged

9 tasks done

Shpaner mentioned this pull request Jun 17, 2026

Fix iOS SwiftPM integration for newer Flutter dotintent/flutter_blue_ultra#12

Closed

3 tasks

charlesoj6205 mentioned this pull request Jul 27, 2026

Add SwiftPM support, empty-config bypass mode, and isInitialized/isApproovEnabled APIs approov/approov-service-flutter-httpclient#35

Merged

6 of 7 tasks

This was referenced Oct 4, 2026

fix(oidc_macos): backport Flutter SwiftPM plugin layout to 0.8.x (#450) Bdaya-Dev/oidc#463

Merged

fix(oidc_ios): backport Flutter SwiftPM plugin layout to 0.8.x (#450) Bdaya-Dev/oidc#458

Merged

Navigation Menu

Repository navigation

Add Flutter as a Swift Package dependency - #178931

Add Flutter as a Swift Package dependency#178931
auto-submit[bot] merged 9 commits into
flutter:masterfrom
vashworth:swiftpm_local_flutter_dependency

vashworth commented Nov 21, 2025 •

edited

Loading

Uh oh!

vashworth Dec 5, 2025

Uh oh!

vashworth Dec 5, 2025

Uh oh!

vashworth Dec 5, 2025

Uh oh!

stuartmorgan-g left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

jmagman commented Jan 2, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

	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;
	}

	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}');

	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}');
	}

Conversation

vashworth commented Nov 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Change to Flutter Run Scripts

Pre-launch Checklist

Uh oh!

vashworth Dec 5, 2025

Choose a reason for hiding this comment

Uh oh!

vashworth Dec 5, 2025

Choose a reason for hiding this comment

Uh oh!

vashworth Dec 5, 2025

Choose a reason for hiding this comment

Uh oh!

stuartmorgan-g left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

jmagman commented Jan 2, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

vashworth commented Nov 21, 2025 •

edited

Loading