Skip to content

Xcode 26 beta 4 #9748

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 8 commits into
base: main
Choose a base branch
from
Draft

Xcode 26 beta 4 #9748

wants to merge 8 commits into from

Conversation

jmagman
Copy link
Member

@jmagman jmagman commented Aug 4, 2025

Xcode 26 beta 4 #9703 but with #9746 and #9431 instead of #9428
Also #9666

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the CI configuration to use Xcode 16. The changes include updating the macOS version, SDK version, and handling new deprecations. However, there appears to be a critical typo across multiple files where the iOS version is set to 26.0. Given that Xcode 16 is paired with the iOS 18 SDK, this should likely be 18.0. This error will cause CI jobs to fail and needs to be corrected.

@jmagman jmagman changed the title Xcode 26 Xcode 26 beta 4 Aug 4, 2025
stuartmorgan-g and others added 2 commits August 4, 2025 16:47
Until flutter/flutter#172427 is resolved,
`xcode-analyze` doesn't work as desired with SwiftPM enabled (it
analyzes only the test code, not the plugin code). To avoid losing
analysis coverage in the meantime, this disabled SwiftPM temporarily
while running analysis.

This PR also updates `build-examples` to use the newer pubspec-based
config option to set the SwiftPM flag state instead of setting global
state, to avoid future issues where we are unintentionally bleeding flag
changes across different tests, and to make local runs not impact
developer machine state.

To unit test this functionality, this adds a new feature to the existing
process mock system that allows running an arbitrary test callback at
the ponit where a process is being run, which in this case allows
reading the temporarily-modified pubspec contents at the right point in
the command execution.

Fixes flutter/flutter#171442
@jmagman
Copy link
Member Author

jmagman commented Aug 6, 2025

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

Successfully merging this pull request may close these issues.

3 participants