Repository navigation
Fix Xcode 27 lipo verification failure for Darwin frameworks - #188625
Merged
Merged
Conversation
github-actions
Bot
added
tool
okorohelijah
marked this pull request as ready for review
June 26, 2026 12:46
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates the Darwin build target to verify each architecture individually using lipo -verify_arch in a loop, rather than verifying all architectures in a single command. The corresponding unit tests are updated to match this new behavior. The reviewer suggests improving the error message thrown during verification failure to specify the exact architecture that failed, aligning with the style guide's principle that error messages should be useful.
Contributor
Author
|
I think the issue might be a regression from apple and may be fixed in an official release because based on the official documentation when i ran |
vashworth
approved these changes
Jun 26, 2026
Contributor
|
@okorohelijah If you haven't already, please make sure to verify locally that it fixes the issues with Xcode 27. You'll need to download it from go/xcode if you haven't already. |
Contributor
Author
|
yup, i already verified that it works |
okorohelijah
added
the
autosubmit
flutter-dashboard
Bot
removed
the
autosubmit
This was referenced Jun 27, 2026
This was referenced Jun 29, 2026
okorohelijah
added
the
cp: stable
marcobazzani
pushed a commit
to marcobazzani/FinanceCopilot
that referenced
this pull request
Sep 16, 2026
Xcode 27 raises the minimum macOS deployment target to 12.0 and changes lipo -verify_arch to one architecture per call; Flutter 3.41.6 fails on both. Move to Flutter 3.47.4 (contains flutter/flutter#188625) and align the project: - .flutter-version + CI: 3.41.6 -> 3.47.4 - macOS minimum 10.15 -> 12.0 (Podfile, Runner.xcodeproj), matching flutter/flutter#187762 - pdfrx ^2.4.1 -> ^2.6.1: pdfrx_engine 0.4.2 does not compile on Dart 3.13; drop the now-inert dismissPdfiumWasmWarnings flag - ReorderableListView.onReorder -> onReorderItem (deprecated in 3.47; the callback already delivers the post-removal index) - analysis_options: declare the platform-directory excludes that the 3.47 AnalysisOptionsMigration otherwise rewrites on every pub get - Swift Package Manager scaffolding generated by 3.47 (Package.resolved, scheme, plugin registrant, Podfile.lock)
|
For anyone else looking at this issue and can't upgrade to 3.47.x yet, this was shipped as a patch in 3.44.8 #189792 |
MylioScott
pushed a commit
to mylollc/flutter
that referenced
this pull request
Sep 29, 2026
…#188625) This PR fixes a blocking build failure encountered when building iOS and macOS apps using the Xcode 27 toolchain. *List which issues are fixed by this PR. You must list at least one issue. An issue is not required if the PR fixes something trivial like a typo.* Fixes flutter#188346, flutter#188461 *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 [AI contribution guidelines] and understand my responsibilities, or I am not using AI tools. - [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. - [ ] 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. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. If this change needs to override an active code freeze, provide a comment explaining why. The code freeze workflow can be overridden by code reviewers. See pinned issues for any active code freezes with guidance. **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. <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [AI contribution guidelines]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#ai-contribution-guidelines [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 file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes a blocking build failure encountered when building iOS and macOS apps using the Xcode 27 toolchain.
List which issues are fixed by this PR. You must list at least one issue. An issue is not required if the PR fixes something trivial like a typo.
Fixes #188346, #188461
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
///).If you need help, consider asking for advice on the #hackers-new channel on Discord.
If this change needs to override an active code freeze, provide a comment explaining why. The code freeze workflow can be overridden by code reviewers. See pinned issues for any active code freezes with guidance.
Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the
gemini-code-assistbot 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.