Pass EXCLUDED_ARCHS from Xcode project to xcodebuild for macOS builds #176948

abdelaziz-mahdy · 2025-10-13T18:56:54Z

Passes EXCLUDED_ARCHS from Xcode project build settings to the xcodebuild command, fixing macOS builds when
dependencies don't support all architectures.

Problem

Release builds for macOS create universal binaries (arm64 + x86_64) by default. This causes build failures when
using native dependencies that only provide binaries for a single architecture. While developers can set
EXCLUDED_ARCHS in their Xcode project's xcconfig files, Swift Package Manager dependencies don't respect this
project-level setting.

Fixes: #176605

Solution

Instead of adding a CLI flag, pass EXCLUDED_ARCHS from the Xcode project's build settings directly to xcodebuild. This ensures Swift Package Manager dependencies respect architecture exclusions set in the project configuration.

How it works:
When macos/Runner/Configs/Release.xcconfig contains:

EXCLUDED_ARCHS = x86_64

The build command now includes EXCLUDED_ARCHS=x86_64, creating an arm64-only binary.

Usage

1. Edit your xcconfig file (e.g., macos/Runner/Configs/Release.xcconfig):

#include "../../Flutter/Flutter-Release.xcconfig"
#include "Warnings.xcconfig"

// Exclude x86_64 for dependencies that only support Apple Silicon
EXCLUDED_ARCHS = x86_64

2. Build normally:

flutter build macos --release

Without exclusions (default behavior):

# Creates universal binary (arm64 + x86_64)
flutter build macos --release

Implementation

Modified buildMacOS() to retrieve EXCLUDED_ARCHS from Xcode project build settings
Pass EXCLUDED_ARCHS to xcodebuild command when set and non-empty
Removed unused activeArch parameter
Added inline documentation explaining the SPM compatibility fix

Testing

Manual verification:

✅ Built ExecuTorch Flutter example with EXCLUDED_ARCHS = x86_64: arm64-only binary (518.6MB)
✅ Built without exclusions: universal binary (existing behavior)
✅ Verified architecture with lipo -info: arm64-only when excluded

Unit tests:

✅ Added test: "Passes EXCLUDED_ARCHS from Xcode project to xcodebuild command"
✅ Added test: "Does not pass EXCLUDED_ARCHS when not set in Xcode project"
✅ All 25 macOS build tests passing

If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.

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.

gemini-code-assist

Code Review

This pull request introduces a --macos-arch flag to the flutter build macos command, allowing developers to specify a target architecture (arm64 or x86_64) for macOS builds. This is implemented by adding a new command-line option, parsing it, and passing the corresponding architecture information to xcodebuild via the -destination and ARCHS build settings. The changes also include new tests to verify this functionality. The implementation looks solid, but I have a suggestion to improve the test coverage and maintainability.

packages/flutter_tools/test/commands.shard/hermetic/build_macos_test.dart

…arch

…specific builds

vashworth · 2025-10-23T17:37:17Z

If we can avoid adding any new flags, that would be preferred. Did you try setting the destination to platform=macOS to see if that fixed it?

abdelaziz-mahdy · 2025-10-25T14:03:23Z

If we can avoid adding any new flags, that would be preferred. Did you try setting the destination to platform=macOS to see if that fixed it?

I tested platform=macOS,arch=$arch as suggested. It works, but breaks backward compatibility by forcing all release builds to single-architecture only.

The problem:

Disables universal binary creation by default
Users wanting both architectures must build separately on Intel and Apple Silicon, then manually combine with lipo
No way to opt-out for projects without architecture constraints

Why the flag is better:

Preserves current behavior (universal binaries by default)
Provides explicit opt-in for architecture-limited dependencies: --macos-arch=arm64
Clear, documentable solution: "Use --macos-arch if your dependencies don't support both architectures"

The flag solves the edge case without breaking the common case.

vashworth · 2025-10-28T18:33:50Z

I tested platform=macOS,arch=$arch as suggested.

Try without an arch, just platform=macOS

abdelaziz-mahdy · 2025-11-11T22:52:44Z

I tested platform=macOS,arch=$arch as suggested.

Try without an arch, just platform=macOS

I tested just platform=macOS (without arch) as suggested. It still fails with the same error because xcodebuild
treats platform=macOS as ambiguous and attempts to build for both architectures.

The warning shows:
xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:macOS, arch:arm64, id:00006020-001820E60A33C01E, name:My Mac }
{ platform:macOS, arch:x86_64, id:00006020-001820E60A33C01E, name:My Mac }

Despite picking arm64 first, xcodebuild still tries to compile for x86_64, causing the build to fail. The
destination alone isn't sufficient—we must also specify ARCHS build settings to explicitly control which
architectures to build.

The --macos-arch flag approach works because it sets both the destination (platform=macOS,arch=arm64) and the
build settings (ARCHS=arm64, ONLY_ACTIVE_ARCH=YES), giving explicit control without breaking the default universal
binary behavior.

vashworth · 2025-11-13T18:56:44Z

I tested platform=macOS,arch=$arch as suggested.

Try without an arch, just platform=macOS

I tested just platform=macOS (without arch) as suggested. It still fails with the same error because xcodebuild treats platform=macOS as ambiguous and attempts to build for both architectures.

The warning shows: xcodebuild: WARNING: Using the first of multiple matching destinations: { platform:macOS, arch:arm64, id:00006020-001820E60A33C01E, name:My Mac } { platform:macOS, arch:x86_64, id:00006020-001820E60A33C01E, name:My Mac }

Despite picking arm64 first, xcodebuild still tries to compile for x86_64, causing the build to fail. The destination alone isn't sufficient—we must also specify ARCHS build settings to explicitly control which architectures to build.

The --macos-arch flag approach works because it sets both the destination (platform=macOS,arch=arm64) and the build settings (ARCHS=arm64, ONLY_ACTIVE_ARCH=YES), giving explicit control without breaking the default universal binary behavior.

Okay thank you for trying! I see now that it's not that the app binary is still compiling x86_64. It's SwiftPM and its dependencies

vashworth · 2025-11-13T18:57:41Z

packages/flutter_tools/lib/src/macos/build_macos.dart

+        if (activeArch != null) ...<String>[
+          'ONLY_ACTIVE_ARCH=${onlyActiveArch ? 'YES' : 'NO'}',
+          'ARCHS=${activeArch.name}',
+        ],


Okay so I played with this a little bit and I think a cleaner solution would be to pass EXCLUDED_ARCHS to the xcodebuild command so that developers can exclude the arch through Xcode. It seems like Swift Package Manager doesn't respect the EXCLUDED_ARCHS in the project unless it's sent with the command directly.

+ final String? excludedArches = buildSettings['EXCLUDED_ARCHS']; try { result = await globals.processUtils.stream( <String>[ '/usr/bin/env', 'xcrun', 'xcodebuild', '-workspace', xcodeWorkspace.path, '-configuration', configuration, '-scheme', scheme, '-derivedDataPath', flutterBuildDir.absolute.path, '-destination', destination, 'OBJROOT=${globals.fs.path.join(flutterBuildDir.absolute.path, 'Build', 'Intermediates.noindex')}', 'SYMROOT=${globals.fs.path.join(flutterBuildDir.absolute.path, 'Build', 'Products')}', if (verboseLogging) 'VERBOSE_SCRIPT_LOGGING=YES' else '-quiet', 'COMPILER_INDEX_STORE_ENABLE=NO', if (disabledSandboxEntitlementFile != null) 'CODE_SIGN_ENTITLEMENTS=${disabledSandboxEntitlementFile.path}', + if (excludedArches != null && excludedArches.trim().isNotEmpty) + 'EXCLUDED_ARCHS=$excludedArches', ...environmentVariablesAsXcodeBuildSettings(globals.platform), ],

What do you think?

I can give it a try, but why this instead of the command line arg? isnt that going to be a commandline arg too?

I can give it a try, but why this instead of the command line arg? isnt that going to be a commandline arg too?

No it wouldn't be a command line arg, the buildSettings['EXCLUDED_ARCHS'] would come from the Xcode project's build settings. No flag would be passed into the CLI

done, fixes my issue, updated PR title and description.

…build settings handling

…arch

vashworth

LGTM! Thank you for the changes!

vashworth · 2025-11-19T16:46:23Z

@bkonyi Can you do a second review?

bkonyi

LGTM

auto-submit · 2025-11-19T17:02:09Z

autosubmit label was removed for flutter/flutter/176948, because - The status or check suite Linux analyze has failed. Please fix the issues identified (or deflake) before re-applying this label.

vashworth · 2025-11-21T16:01:36Z

Test Linux analyze is failing due to build_macos_test.dart needs to be formatted:

 Found 1 Dart file which was formatted incorrectly.
 To fix, run `dart format packages/flutter_tools/test/commands.shard/hermetic/build_macos_test.dart` or:
 git apply <<DONE
 diff --git a/packages/flutter_tools/test/commands.shard/hermetic/build_macos_test.dart b/packages/flutter_tools/test/commands.shard/hermetic/build_macos_test.dart
 index 22e12e5f036..00000000000 100644
 --- a/packages/flutter_tools/test/commands.shard/hermetic/build_macos_test.dart
 +++ b/packages/flutter_tools/test/commands.shard/hermetic/build_macos_test.dart
 @@ -42,9 +42,7 @@ class FakeXcodeProjectInterpreterWithProfile extends FakeXcodeProjectInterpreter
  }
  
  class FakeXcodeProjectInterpreterWithBuildSettings extends FakeXcodeProjectInterpreter {
 -  FakeXcodeProjectInterpreterWithBuildSettings({
 -    this.overrides = const <String, String>{},
 -  });
 +  FakeXcodeProjectInterpreterWithBuildSettings({this.overrides = const <String, String>{}});
  
    final Map<String, String> overrides;
  
 @@ -61,10 +59,7 @@ class FakeXcodeProjectInterpreterWithBuildSettings extends FakeXcodeProjectInter
      XcodeProjectBuildContext? buildContext,
      Duration timeout = const Duration(minutes: 1),
    }) async {
 -    return <String, String>{
 -      ...overrides,
 -      'PRODUCT_BUNDLE_IDENTIFIER': 'com.example.test',
 -    };
 +    return <String, String>{...overrides, 'PRODUCT_BUNDLE_IDENTIFIER': 'com.example.test'};
    }
  }
  
 @@ -1066,9 +1061,9 @@ STDERR STUFF
          osUtils: FakeOperatingSystemUtils(),
        );
  
 -      await createTestCommandRunner(command).run(
 -        <String>['build', 'macos', '--release', '--no-pub'],
 -      );
 +      await createTestCommandRunner(
 +        command,
 +      ).run(<String>['build', 'macos', '--release', '--no-pub']);
  
        expect(fakeProcessManager, hasNoRemainingExpectations);
      },
 @@ -1110,9 +1105,9 @@ STDERR STUFF
          osUtils: FakeOperatingSystemUtils(),
        );
  
 -      await createTestCommandRunner(command).run(
 -        <String>['build', 'macos', '--release', '--no-pub'],
 -      );
 +      await createTestCommandRunner(
 +        command,
 +      ).run(<String>['build', 'macos', '--release', '--no-pub']);
  
        expect(fakeProcessManager, hasNoRemainingExpectations);
      },
 @@ -1129,3 +1124,4 @@ STDERR STUFF
      },
    );
  }
 DONE

abdelaziz-mahdy · 2025-11-21T18:55:08Z

I kept trying to find what was the issue and couldn't, can you show me how to figure it so I know in the future, and will fix it as soon I have access to the computer

vashworth · 2025-11-21T20:30:53Z

I kept trying to find what was the issue and couldn't, can you show me how to figure it so I know in the future, and will fix it as soon I have access to the computer

First click on the failing test, Linux analyze in this case
Click on "View more details on flutter-dashboard" at the bottom

Select the stdout of the step that failed

Scan the logs for failures

In this case, it says you need to run dart format packages/flutter_tools/test/commands.shard/hermetic/build_macos_test.dart

… into macos-arch

abdelaziz-mahdy · 2025-11-23T02:28:13Z

I kept trying to find what was the issue and couldn't, can you show me how to figure it so I know in the future, and will fix it as soon I have access to the computer

First click on the failing test, Linux analyze in this case

Click on "View more details on flutter-dashboard" at the bottom

3. Select the `stdout` of the step that failed 4. Scan the logs for failures
In this case, it says you need to run dart format packages/flutter_tools/test/commands.shard/hermetic/build_macos_test.dart

thank you, reformatted, now I can figure the ci/cd easily

…cOS builds (flutter/flutter#176948)

flutter/flutter@3f553f6...7b98d50 2025-11-26 98614782+auto-submit[bot]@users.noreply.github.com Reverts "Fix for win32 embedder failing to send all alt key downs to the flutter app (#179097)" (flutter/flutter#179136) 2025-11-26 [email protected] Fix for win32 embedder failing to send all alt key downs to the flutter app (flutter/flutter#179097) 2025-11-26 [email protected] Modernize framework lints (flutter/flutter#179089) 2025-11-25 98614782+auto-submit[bot]@users.noreply.github.com Reverts "Add framework-side hitTestBehavior support to Semantics (#178817)" (flutter/flutter#179100) 2025-11-25 [email protected] Add framework-side hitTestBehavior support to Semantics (flutter/flutter#178817) 2025-11-25 [email protected] Roll Packages from e019cf9 to cc3dca6 (1 revision) (flutter/flutter#179081) 2025-11-25 [email protected] Add tooltip windows to the windowing API alongside the window positioning logic (flutter/flutter#177404) 2025-11-25 [email protected] FlutterWindowsView::SendWindowMetrics now reliably sends the display_id (flutter/flutter#179053) 2025-11-25 [email protected] Remove semantics geometry shortcircuit (flutter/flutter#178680) 2025-11-25 [email protected] Add an assert message when OverlayEntry.remove is called twice (flutter/flutter#178163) 2025-11-25 [email protected] Roll Fuchsia Linux SDK from pOO9Jl9HTLsEmks6y... to nzuAxCJGeJbkZCTkr... (flutter/flutter#179066) 2025-11-25 [email protected] Dynamically set MinimumOSVersion in App.framework (flutter/flutter#178253) 2025-11-25 [email protected] Roll Skia from d83c30b090f4 to 925c311f4b37 (2 revisions) (flutter/flutter#179060) 2025-11-25 [email protected] Marks Linux build_android_host_app_with_module_aar to be unflaky (flutter/flutter#174864) 2025-11-25 [email protected] Marks Linux_mokey complex_layout__start_up to be unflaky (flutter/flutter#174865) 2025-11-25 [email protected] Manual Dart SDK roll to 3.11.0-169.0.dev (flutter/flutter#179054) 2025-11-25 [email protected] Bump Dart to 3.9 (flutter/flutter#179041) 2025-11-25 [email protected] Roll Skia from e298c2f93ebf to d83c30b090f4 (2 revisions) (flutter/flutter#179058) 2025-11-24 [email protected] updated licenses_cpp readme (flutter/flutter#178874) 2025-11-24 [email protected] Roll Skia from 43d2020be565 to e298c2f93ebf (5 revisions) (flutter/flutter#179046) 2025-11-24 [email protected] Refactor `_isLabel` method in `stepper.dart` to use `any` for better readablity (flutter/flutter#178909) 2025-11-24 49699333+dependabot[bot]@users.noreply.github.com Bump actions/checkout from 5 to 6 in the all-github-actions group (flutter/flutter#179049) 2025-11-24 [email protected] Disposes test restoration manager when accessed by bindings (flutter/flutter#176519) 2025-11-24 [email protected] [ Widget Preview ] Always generate scaffold under `$TMP` (flutter/flutter#179039) 2025-11-24 [email protected] Roll Packages from e67b6be to e019cf9 (9 revisions) (flutter/flutter#179035) 2025-11-24 [email protected] Update CHANGELOG.md for Flutter 3.38.3 (flutter/flutter#178935) 2025-11-24 [email protected] Remove unnecessary `String.valueOf` in `SettingsChannel.java‎` (flutter/flutter#178590) 2025-11-24 [email protected] Roll pub manually, pick up flutter_lints in examples/api (flutter/flutter#179030) 2025-11-24 [email protected] Roll Dart SDK from 24cc9a740bd3 to afca43095efa (1 revision) (flutter/flutter#179019) 2025-11-24 [email protected] Pass EXCLUDED_ARCHS from Xcode project to xcodebuild for macOS builds (flutter/flutter#176948) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-packages Please CC [email protected],[email protected] on the revert to ensure that a human is aware of the problem. To file a bug in Packages: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

…flutter#176948)  Passes `EXCLUDED_ARCHS` from Xcode project build settings to the xcodebuild command, fixing macOS builds when dependencies don't support all architectures. ### Problem Release builds for macOS create universal binaries (arm64 + x86_64) by default. This causes build failures when using native dependencies that only provide binaries for a single architecture. While developers can set `EXCLUDED_ARCHS` in their Xcode project's xcconfig files, Swift Package Manager dependencies don't respect this project-level setting. **Fixes**: flutter#176605 ## Solution Instead of adding a CLI flag, pass `EXCLUDED_ARCHS` from the Xcode project's build settings directly to xcodebuild. This ensures Swift Package Manager dependencies respect architecture exclusions set in the project configuration. **How it works:** When `macos/Runner/Configs/Release.xcconfig` contains: ```xcconfig EXCLUDED_ARCHS = x86_64 ``` The build command now includes `EXCLUDED_ARCHS=x86_64`, creating an arm64-only binary. ## Usage **1. Edit your xcconfig file** (e.g., `macos/Runner/Configs/Release.xcconfig`): ```xcconfig #include "../../Flutter/Flutter-Release.xcconfig" #include "Warnings.xcconfig" // Exclude x86_64 for dependencies that only support Apple Silicon EXCLUDED_ARCHS = x86_64 ``` **2. Build normally:** ```bash flutter build macos --release ``` **Without exclusions (default behavior):** ```bash # Creates universal binary (arm64 + x86_64) flutter build macos --release ``` ## Implementation - Modified `buildMacOS()` to retrieve `EXCLUDED_ARCHS` from Xcode project build settings - Pass `EXCLUDED_ARCHS` to xcodebuild command when set and non-empty - Removed unused `activeArch` parameter - Added inline documentation explaining the SPM compatibility fix ## Testing **Manual verification:** - ✅ Built ExecuTorch Flutter example with `EXCLUDED_ARCHS = x86_64`: arm64-only binary (518.6MB) - ✅ Built without exclusions: universal binary (existing behavior) - ✅ Verified architecture with `lipo -info`: arm64-only when excluded **Unit tests:** - ✅ Added test: "Passes EXCLUDED_ARCHS from Xcode project to xcodebuild command" - ✅ Added test: "Does not pass EXCLUDED_ARCHS when not set in Xcode project" - ✅ All 25 macOS build tests passing *If you had to change anything in the [flutter/tests] repo, include a link to the migration guide as per the [breaking change policy].* ## 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 --------- Co-authored-by: Victoria Ashworth <[email protected]>

Add macOS architecture option to build command and update tests

b049c53

abdelaziz-mahdy requested a review from a team as a code owner October 13, 2025 18:56

github-actions bot added tool Affects the "flutter" command-line tool. See also t: labels. a: desktop Running on desktop team-ios Owned by iOS platform team labels Oct 13, 2025

abdelaziz-mahdy mentioned this pull request Oct 13, 2025

SwiftPM macOS - Allow limiting architecture for release builds #176605

Open

gemini-code-assist bot reviewed Oct 13, 2025

View reviewed changes

packages/flutter_tools/test/commands.shard/hermetic/build_macos_test.dart Show resolved Hide resolved

abdelaziz-mahdy added 3 commits October 13, 2025 15:58

Merge branch 'main' of https://github.com/flutter/flutter into macos-…

ceb9311

…arch

Refactor macOS build tests to use a helper function for architecture-…

90d220c

…specific builds

Merge branch 'master' into macos-arch

7c5724c

LongCatIsLooong requested a review from vashworth October 16, 2025 21:58

vashworth reviewed Nov 13, 2025

View reviewed changes

abdelaziz-mahdy changed the title ~~Add macOS architecture option to build command and update tests~~ Pass EXCLUDED_ARCHS from Xcode project to xcodebuild for macOS builds Nov 15, 2025

abdelaziz-mahdy added 2 commits November 15, 2025 15:47

Refactor macOS build command to remove architecture flag and enhance …

71d224b

…build settings handling

Merge branch 'main' of https://github.com/flutter/flutter into macos-…

079e233

…arch

vashworth approved these changes Nov 19, 2025

View reviewed changes

vashworth requested a review from bkonyi November 19, 2025 16:45

Merge branch 'master' into macos-arch

be59ef0

bkonyi approved these changes Nov 19, 2025

View reviewed changes

bkonyi added the autosubmit Merge PR when tree becomes green via auto submit App label Nov 19, 2025

auto-submit bot removed the autosubmit Merge PR when tree becomes green via auto submit App label Nov 19, 2025

abdelaziz-mahdy added 2 commits November 22, 2025 17:33

reformat

b5b36d7

Merge branch 'macos-arch' of https://github.com/abdelaziz-mahdy/flutter…

dfcfa3d

… into macos-arch

vashworth added the autosubmit Merge PR when tree becomes green via auto submit App label Nov 24, 2025

auto-submit bot added this pull request to the merge queue Nov 24, 2025

Merged via the queue into flutter:master with commit 1b93620 Nov 24, 2025
141 checks passed

flutter-dashboard bot removed the autosubmit Merge PR when tree becomes green via auto submit App label Nov 24, 2025

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 25, 2025

1b936203a Pass EXCLUDED_ARCHS from Xcode project to xcodebuild for ma…

07fcd09

…cOS builds (flutter/flutter#176948)

engine-flutter-autoroll mentioned this pull request Nov 25, 2025

Roll Flutter from 3f553f6779cb to 68115a705fe2 (22 revisions) flutter/packages#10512

Closed

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 25, 2025

1b936203a Pass EXCLUDED_ARCHS from Xcode project to xcodebuild for ma…

ca10f88

…cOS builds (flutter/flutter#176948)

engine-flutter-autoroll mentioned this pull request Nov 25, 2025

Roll Flutter from 3f553f6779cb to 2778dfd2cb7b (23 revisions) flutter/packages#10513

Closed

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 25, 2025

1b936203a Pass EXCLUDED_ARCHS from Xcode project to xcodebuild for ma…

d06bc69

…cOS builds (flutter/flutter#176948)

engine-flutter-autoroll mentioned this pull request Nov 25, 2025

Roll Flutter from 3f553f6779cb to 084deda0ba3f (24 revisions) flutter/packages#10514

Closed

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 25, 2025

1b936203a Pass EXCLUDED_ARCHS from Xcode project to xcodebuild for ma…

d161a8b

…cOS builds (flutter/flutter#176948)

engine-flutter-autoroll mentioned this pull request Nov 25, 2025

Roll Flutter from 3f553f6779cb to 882c29a1947c (25 revisions) flutter/packages#10515

Closed

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 25, 2025

1b936203a Pass EXCLUDED_ARCHS from Xcode project to xcodebuild for ma…

25e5e37

…cOS builds (flutter/flutter#176948)

engine-flutter-autoroll mentioned this pull request Nov 25, 2025

Roll Flutter from 3f553f6779cb to 882c29a1947c (25 revisions) flutter/packages#10518

Closed

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 25, 2025

1b936203a Pass EXCLUDED_ARCHS from Xcode project to xcodebuild for ma…

9566813

…cOS builds (flutter/flutter#176948)

engine-flutter-autoroll mentioned this pull request Nov 25, 2025

Roll Flutter from 3f553f6779cb to 8f3f89f75e8c (26 revisions) flutter/packages#10519

Closed

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 26, 2025

1b936203a Pass EXCLUDED_ARCHS from Xcode project to xcodebuild for ma…

b88823d

…cOS builds (flutter/flutter#176948)

engine-flutter-autoroll mentioned this pull request Nov 26, 2025

Roll Flutter from 3f553f6779cb to fde117b7b144 (29 revisions) flutter/packages#10522

Closed

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 26, 2025

1b936203a Pass EXCLUDED_ARCHS from Xcode project to xcodebuild for ma…

2e94ee2

…cOS builds (flutter/flutter#176948)

engine-flutter-autoroll mentioned this pull request Nov 26, 2025

Roll Flutter from 3f553f6779cb to 7b98d50631e5 (30 revisions) flutter/packages#10523

Merged

Pass EXCLUDED_ARCHS from Xcode project to xcodebuild for macOS builds #176948

Pass EXCLUDED_ARCHS from Xcode project to xcodebuild for macOS builds #176948

Uh oh!

Conversation

abdelaziz-mahdy commented Oct 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Problem

Solution

Usage

Implementation

Testing

Pre-launch Checklist

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

Uh oh!

vashworth commented Oct 23, 2025

Uh oh!

abdelaziz-mahdy commented Oct 25, 2025

Uh oh!

vashworth commented Oct 28, 2025

Uh oh!

abdelaziz-mahdy commented Nov 11, 2025

Uh oh!

vashworth commented Nov 13, 2025

Uh oh!

vashworth Nov 13, 2025

Choose a reason for hiding this comment

Uh oh!

abdelaziz-mahdy Nov 13, 2025

Choose a reason for hiding this comment

Uh oh!

vashworth Nov 14, 2025

Choose a reason for hiding this comment

Uh oh!

abdelaziz-mahdy Nov 15, 2025

Choose a reason for hiding this comment

Uh oh!

vashworth left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

vashworth commented Nov 19, 2025

Uh oh!

bkonyi left a comment

Choose a reason for hiding this comment

Uh oh!

auto-submit bot commented Nov 19, 2025

Uh oh!

vashworth commented Nov 21, 2025

Uh oh!

abdelaziz-mahdy commented Nov 21, 2025

Uh oh!

vashworth commented Nov 21, 2025

Uh oh!

abdelaziz-mahdy commented Nov 23, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

abdelaziz-mahdy commented Oct 13, 2025 •

edited

Loading

vashworth left a comment •

edited

Loading