An update of the FAQ - a first draft

.github/workflows/codeql-analysis.yml

@@ -36,7 +36,7 @@ jobs:
 
     # Initializes the CodeQL tools for scanning.
     - name: Initialize CodeQL
-      uses: github/codeql-action/init@cdf488f595d80d6e07e03d4674febd5ab45fa938
+      uses: github/codeql-action/init@b96794f015dfd88f77b49b1c93e0fa7110f94c63
       with:
         languages: ${{ matrix.language }}
         # If you wish to specify custom queries, you can do so here or in a config file.
@@ -47,7 +47,7 @@ jobs:
     # Autobuild attempts to build any compiled languages  (C/C++, C#, or Java).
     # If this step fails, then you should remove it and run the build manually (see below)
     - name: Autobuild
-      uses: github/codeql-action/autobuild@cdf488f595d80d6e07e03d4674febd5ab45fa938
+      uses: github/codeql-action/autobuild@b96794f015dfd88f77b49b1c93e0fa7110f94c63
 
     # ℹ️ Command-line programs to run using the OS shell.
     # 📚 https://git.io/JvXDl
@@ -61,4 +61,4 @@ jobs:
     #   make release
 
     - name: Perform CodeQL Analysis
-      uses: github/codeql-action/analyze@cdf488f595d80d6e07e03d4674febd5ab45fa938
+      uses: github/codeql-action/analyze@b96794f015dfd88f77b49b1c93e0fa7110f94c63

sites/docs/firebase.json

@@ -202,6 +202,7 @@
       { "source": "/platform-integration/ios/install-ios", "destination": "/platform-integration/ios/setup", "type": 301 },
       { "source": "/platform-integration/ios/install-ios/:rest*", "destination": "/platform-integration/ios/setup", "type": 301 },
       { "source": "/platform-integration/ios/splash-screen", "destination": "/platform-integration/ios/launch-screen", "type": 301 },
+      { "source": "/platform-integration/ios/ios-latest", "destination": "/platform-integration/ios", "type": 301 },
       { "source": "/platform-integration/linux/install-linux", "destination": "/platform-integration/linux/setup", "type": 301 },
       { "source": "/platform-integration/linux/install-linux/:rest*", "destination": "/platform-integration/linux/setup", "type": 301 },
       { "source": "/platform-integration/macos/c-interop", "destination": "/platform-integration/legacy-ffi-plugin", "type": 301 },
@@ -226,6 +227,7 @@
       { "source": "/release/release-notes/supported-platforms", "destination": "/reference/supported-platforms", "type": 301 },
       { "source": "/release/breaking-changes/can-request-focus", "destination": "https://github.com/flutter/flutter/issues/149067", "type": 301 },
       { "source": "/release/breaking-changes/scrollable_alert_dialog", "destination": "/release/breaking-changes/scrollable-alert-dialog", "type": 301 },
+      { "source": "/release/breaking-changes/uiscene-lifecycle-ios", "destination": "/release/breaking-changes/uiscenedelegate", "type": 301 },
       { "source": "/release/breaking-changes/win_lifecycle_process_function", "destination": "/release/breaking-changes/win-lifecycle-process-function", "type": 301 },
       { "source": "/release/archive", "destination": "/install/archive", "type": 301 },
       { "source": "/release/upgrade", "destination": "/install/upgrade", "type": 301 },

sites/docs/src/content/platform-integration/index.md

@@ -220,14 +220,6 @@ Learn how to add custom integrations with iOS to your Flutter app.
       <p>Learn how to add an iOS app extension to your app.</p>
     </div>
   </a>
-  <a class="card outlined-card" href="/platform-integration/ios/ios-latest">
-    <div class="card-header">
-      <span class="card-title">Support new iOS features</span>
-    </div>
-    <div class="card-content">
-      <p>Learn about Flutter's support for new or upcoming iOS features.</p>
-    </div>
-  </a>
 </div>
 
 ### Integrate with the web {:#web}

sites/docs/src/content/platform-integration/ios/setup.md

@@ -95,23 +95,19 @@ an iOS physical device or on the iOS Simulator.
 
 ## Set up an iOS device {: #set-up-devices}
 
-We recommend starting with the iOS Simulator as
-it's easier to get set up than a physical iOS device.
-However, you should also test your app on an actual
-physical device.
+It's easiest to first set up the simulator,
+but be sure to also test your app on a physical device.
 
 <Tabs key="ios-simulator-or-physical-device">
 <Tab name="Simulator">
 
-To start the simulator, run the command for your Xcode version.
-
-If you're using Xcode 27 or later, start the Device Hub app:
+Start the simulator (renamed to Device Hub on Xcode 27):
 
 ```console
 $ open -a DeviceHub
 ```
 
-If you're using Xcode 26 or earlier, start the Simulator app:
+On Xcode 26 or earlier, start the Simulator app:
 
 ```console
 $ open -a Simulator
@@ -126,8 +122,6 @@ on the Apple Developer site.
 </Tab>
 <Tab name="Physical device">
 
-[Flutter on latest iOS]: /platform-integration/ios/ios-latest
-
 Set up each iOS device on which you want to test.
 
  1. <h3>Configure your physical iOS device</h3>

sites/docs/src/content/platform-integration/macos/building.md

@@ -33,6 +33,15 @@ pop-up buttons, and modal dialogs.
 
 ## Building macOS apps
 
+:::warning macOS Intel (x64) deprecation
+As Apple phases out Intel-based Macs,
+Flutter is phasing out support for Intel (x64) hardware.
+For details on the timeline and impact,
+refer to the [macOS Intel deprecation strategy][].
+
+[macOS Intel deprecation strategy]: {{site.main-url}}/go/macos-intel-deprecation
+:::
+
 To distribute your macOS application, you can either
 [distribute it through the macOS App Store][],
 or you can distribute the `.app` itself,

sites/docs/src/content/reference/supported-platforms.md

@@ -35,7 +35,7 @@ Flutter supports deploying to the following platforms.
     name="iOS"
     icon="mobile"
     arch="Arm64"
-    supported="15 to 26"
+    supported="15 to 27"
     ci-tested="18 and 26"
     unsupported="14 and earlier"
     deploy-to-link="/deployment/ios"
@@ -48,14 +48,9 @@ Flutter supports deploying to the following platforms.
 As Apple phases out Intel-based Macs,
 Flutter is phasing out support for Intel (x64) hardware.
 For details on the timeline and impact,
-check out the [macOS Intel deprecation strategy][].
-
-If you can't migrate to an [Apple Silicon Mac][],
-you can continue using older Flutter releases from the [SDK archive][].
+refer to the [macOS Intel deprecation strategy][].
 
 [macOS Intel deprecation strategy]: {{site.main-url}}/go/macos-intel-deprecation
-[Apple Silicon Mac]: https://support.apple.com/en-us/116943
-[SDK archive]: /install/archive
 :::
 
 <PlatformsGrid>
@@ -72,7 +67,7 @@ you can continue using older Flutter releases from the [SDK archive][].
     name="macOS"
     icon="laptop_mac"
     arch="x64, Arm64"
-    supported="Monterey (12) to Tahoe (26)"
+    supported="Monterey (12) to Golden Gate (27)"
     ci-tested="Sequoia (15)"
     unsupported="Big Sur (11) and earlier"
     deploy-to-link="/deployment/macos"

sites/docs/src/content/release/breaking-changes/uiscenedelegate.md

@@ -13,6 +13,17 @@ As of the Flutter 3.41 release,
 eligible apps are migrated automatically.
 :::
 
+:::version-note
+Beginning with Xcode 27 (iOS 27 SDK), Apple mandates the `UIScene`
+lifecycle for UIKit apps. Flutter apps built with Xcode 27 that
+do not adopt `UIScene` fail to launch on startup.
+
+In Flutter 3.41 and later, if your project uses an unmodified `AppDelegate`,
+Flutter migrates it automatically. If your project uses a custom `AppDelegate`
+or a Flutter version earlier than 3.41, complete the following manual
+migration steps.
+:::
+
 ## Summary
 
 Apple now requires iOS developers to adopt the `UIScene` lifecycle.
@@ -1088,10 +1099,8 @@ When you're ready to re-enable `UIScene` support, remove the underscore.
 Landed in version: 3.38.0-0.1.pre<br>
 In stable release: 3.38
 
-Apple hasn't yet announced when it will enforce the `UIScene` requirement.
-Once Apple changes its warning to an assertion,
-Flutter apps that haven't adopted the `UIScene` lifecycle will
-crash on startup when built with the latest SDK.
+Flutter apps that haven't adopted the `UIScene` lifecycle
+will crash on startup when built with Xcode 27 (iOS 27 SDK).
 
 ## References