Merge branch 'main' into CaoGiaHieu-dev/main

* main: (56 commits)
  [go_router_builder] Support extension types (flutter#9458)
  Roll Flutter from e2a347b14a18 to 34c2a3b158b2 (41 revisions) (flutter#9803)
  [go_router_builder] Migrate to Element2 API and update dependencies (flutter#9649)
  [in_app_purchase_storekit] Add support for quantity in consumable product purchases (#171570) (flutter#9698)
  [pigeon] Improves documentation of `ProxyApi` and moves helper functions to a separate file (flutter#9756)
  Roll Flutter from 1590543f6794 to e2a347b14a18 (1 revision) (flutter#9784)
  [camera_avfoundation] Implementation swift migration - part 11 (flutter#9690)
  [camera_avfoundation] Fix crash when streaming while recording (flutter#9691)
  Roll Flutter from 38217906e95c to 1590543f6794 (14 revisions) (flutter#9780)
  Roll Flutter from 92a6bfbfd6ef to 38217906e95c (17 revisions) (flutter#9778)
  [video_player] Improve KVO handling on iOS (flutter#9718)
  [dependabot]: Bump the test-dependencies group across 15 directories with 7 updates (flutter#9736)
  Roll Flutter from 9de63a03428f to 92a6bfbfd6ef (11 revisions) (flutter#9769)
  [google_maps_flutter_platform_interface] Add Advanced markers support (flutter#9737)
  [camera_android_camerax] Re-land "Force new Surface for each SurfaceRequest" (flutter#9760)
  [google_maps_flutter] Add ability to perform Google Maps SDK warmup (flutter#9674)
  Roll Flutter from 59fc766c6fdf to 9de63a03428f (6 revisions) (flutter#9764)
  [webview_flutter_wkwebview] Extended Web View API on iOS to add flexibility when working with local HTML content (flutter#8787)
  [local_auth] Differentiate iOS authentication errors (flutter#9705)
  manual roll to 59fc766c6fdfd03d0983fc95ce8b76793a300dd5 (flutter#9758)
  ...

# Conflicts:
#	packages/go_router_builder/lib/src/type_helpers.dart
#	packages/go_router_builder/pubspec.yaml

Author: CaoGiaHieu-dev

.ci.yaml

@@ -250,9 +250,6 @@ targets:
 
   # Wasm unit tests in master
   - name: Linux_web web_dart_unit_test_wasm_shard_1 master
-    # Broken on master. See flutter/flutter#170433 and
-    # flutter/flutter#170434
-    bringup: true
     recipe: packages/packages
     timeout: 60
     properties:
@@ -268,9 +265,6 @@ targets:
         }
 
   - name: Linux_web web_dart_unit_test_wasm_shard_2 master
-    # Broken on master. See flutter/flutter#170433 and
-    # flutter/flutter#170434
-    bringup: true
     recipe: packages/packages
     timeout: 60
     properties:
@@ -400,7 +394,7 @@ targets:
   ### Android tasks ###
   - name: Linux_android android_build_all_packages master
     recipe: packages/packages
-    timeout: 30
+    timeout: 60
     properties:
       version_file: flutter_master.version
       # This builds the all_packages app only in a current JDK.
@@ -413,7 +407,7 @@ targets:
 
   - name: Linux_android android_build_all_packages stable
     recipe: packages/packages
-    timeout: 30
+    timeout: 60
     properties:
       add_recipes_cq: "true"
       version_file: flutter_stable.version
@@ -1437,7 +1431,6 @@ targets:
     recipe: packages/packages
     presubmit: false
     timeout: 30
-    bringup: true # https://github.com/flutter/flutter/issues/134083
     properties:
       add_recipes_cq: "true"
       target_file: windows_build_all_packages.yaml
@@ -1472,7 +1465,6 @@ targets:
     recipe: packages/packages
     presubmit: false
     timeout: 30
-    bringup: true
     properties:
       target_file: windows_build_all_packages.yaml
       channel: stable

.ci/flutter_master.version

@@ -1 +1 @@
-70cdc0c933d6b84817d216891953b6eb56e22007
+34c2a3b158b2b395cd31351c1e8a94ed4d9892b4

.ci/flutter_stable.version

@@ -1 +1 @@
-d7b523b356d15fb81e7d340bbe52b47f93937323
+edada7c56edf4a183c1735310e123c7f923584f1

.ci/legacy_project/README.md

@@ -41,13 +41,17 @@ and then deleting everything but `android/` from it:
   `build.gradle` to maintain compatibility with plugins that use
   Flutter's most recently supported API version.
 - Modifies `gradle-wrapper.properties` to upgrade the Gradle version
-  from 6.7 to 8.4. If a user runs into an error with the Gradle
+  from 8.4 to 8.7. If a user runs into an error with the Gradle
   version, the warning is clear on how to upgrade the version to
   one that we support.
 - Modifies `settings.gradle` to upgrade the Android Gradle Plugin (AGP)
-  from version 4.1.0 (originally set in `build.gradle`; see bullet below)
-  to 8.3.0. If a user runs into an error with the AGP version, the warning
+  from version 8.3.0 (originally set in `build.gradle`; see bullet below)
+  to 8.6.0. If a user runs into an error with the AGP version, the warning
   is clear on how to upgrade the version to one that we support.
 - Refactor plugin to use declarative Gradle apply instead of the
   imperative apply (this includes moving where the Android Gradle
   Plugin (AGP) version is set from `build.gradle` to `settings.gradle`).
+- Modifies `settings.gradle` to upgrade the Kotlin Gradle Plugin (KGP)
+  from version 1.9.0 to 2.1.0. If a user runs into an error with the AGP version,
+  the warning is clear on how to upgrade the version to one that we support.
+- Modifies `gradle.properties` to not set android.enableJetifier=true.

.ci/legacy_project/all_packages/android/gradle.properties

@@ -1,3 +1,2 @@
 org.gradle.jvmargs=-Xmx4G
 android.useAndroidX=true
-android.enableJetifier=true

.ci/legacy_project/all_packages/android/gradle/wrapper/gradle-wrapper.properties

@@ -3,4 +3,4 @@ distributionBase=GRADLE_USER_HOME
 distributionPath=wrapper/dists
 zipStoreBase=GRADLE_USER_HOME
 zipStorePath=wrapper/dists
-distributionUrl=https\://services.gradle.org/distributions/gradle-8.4-all.zip
+distributionUrl=https\://services.gradle.org/distributions/gradle-8.7-all.zip

.ci/legacy_project/all_packages/android/settings.gradle

@@ -19,8 +19,8 @@ pluginManagement {
 // See https://github.com/flutter/flutter/blob/master/docs/ecosystem/Plugins-and-Packages-repository-structure.md#gradle-structure for more info.
 plugins {
     id "dev.flutter.flutter-plugin-loader" version "1.0.0"
-    id "com.android.application" version "8.3.0" apply false
-    id "org.jetbrains.kotlin.android" version "1.9.0" apply false
+    id "com.android.application" version "8.6.0" apply false
+    id "org.jetbrains.kotlin.android" version "2.1.0" apply false
 }
 
 include ":app"

.ci/targets/macos_repo_checks.yaml

@@ -13,5 +13,5 @@ tasks:
     always: true
   - name: validate iOS and macOS podspecs
     script: .ci/scripts/tool_runner.sh
-    args: ["podspec-check"]
+    args: ["podspec-check", "--exclude=script/configs/exclude_xcode_deprecation.yaml"]
     always: true

AGENTS.md

@@ -0,0 +1,153 @@
+# Agent Guide for the Flutter Packages Repository
+
+This document provides guidance for AI agents to effectively contribute to the `flutter/packages` repository.
+
+## Guiding Principles for Contributions
+
+- **Format All Code**: Every code change must be formatted using the repository's tools.
+- **Pass All Tests**: All changes must pass linting, analysis, and relevant tests.
+- **Update CHANGELOGs**: Any user-facing change or bug fix in a package requires an update to its `CHANGELOG.md` and `pubspec.yaml` version.
+- **Follow Conventions**: Adhere to the repository's specific conventions, such as federated plugin structure and code generation steps.
+
+## Agent Environment Setup
+
+To ensure a consistent and functional environment, configure your VM with the following setup. This provides the necessary Flutter SDK and dependencies for building and testing packages.
+
+```bash
+curl -L https://storage.googleapis.com/flutter_infra_release/releases/stable/linux/flutter_linux_3.32.8-stable.tar.xz | tar -xJ -C $HOME
+export FLUTTER_HOME=$HOME/flutter
+export PATH=$FLUTTER_HOME/bin:$PATH
+flutter --disable-analytics
+flutter precache --force
+# Sanity check the configuration.
+flutter doctor --verbose
+```
+
+## Repository Overview
+
+This is a monorepo containing many Flutter packages.
+- First-party packages developed entirely by the Flutter team are in `packages/`.
+- Packages that were originally developed by a third party, but are now maintained by the Flutter team are in `third_party/packages/`.
+- The repository tooling is in `script/tool/`.
+
+Many packages are part of **federated plugins**. A federated plugin has a main package (e.g., `path_provider`) that defines the API used by plugin clients, a platform interface package (e.g., `path_provider_platform_interface`) that defines the interface that each platform implementation must implement, and one or more platform implementation packages (e.g., `path_provider_android`, `path_provider_ios`) that implement that platform interface. When working on a federated plugin, you may need to modify multiple packages.
+
+For more details, see the main `README.md` and `CONTRIBUTING.md`.
+
+## Core Tooling and Workflows
+
+The primary tool for this repository is `flutter_plugin_tools.dart`.
+
+### Initial Setup
+
+First, initialize the tooling:
+```bash
+cd $REPO_ROOT/script/tool # $REPO_ROOT is the repository root
+dart pub get
+```
+
+### Identifying Target Packages
+
+Most tool commands take a `--packages` argument. You must correctly identify all packages affected by your changes. You can derive this from git diff.
+
+For example, to find changed files against the main branch of the upstream remote (assuming the upstream remote is named `origin`):
+
+```bash
+git diff --name-only origin/main...HEAD
+```
+
+Then, for each file path, find its enclosing package. A package is a directory containing a `pubspec.yaml` file. The directory name is usually the package name. Ignore `pubspec.yaml` files within `example/` directories when determining the package for a file.
+
+#### Targeting All Packages
+
+Running a tool command without a `--packages` argument will run the command on all packages. For example, a dependency can be updated for all packages in the repository:
+
+```bash
+dart run $REPO_ROOT/script/tool/bin/flutter_plugin_tools.dart update-dependency --pub-package <dependency_name>
+```
+
+### Common Commands
+
+- **Formatting**: Always format your changes.
+
+  ```bash
+  dart run $REPO_ROOT/script/tool/bin/flutter_plugin_tools.dart format --packages <changed_packages>
+  ```
+- **Testing**: All changes must pass analysis and tests:
+
+  ```bash
+  # Run static analysis
+  dart run $REPO_ROOT/script/tool/bin/flutter_plugin_tools.dart analyze --packages <changed_packages>
+  # Run Dart unit tests
+  dart run $REPO_ROOT/script/tool/bin/flutter_plugin_tools.dart dart-test --packages <changed_packages>
+  ```
+
+  The tool can also run native and integration tests, but these may require a more complete environment than is available.
+- **Validation**: Run these checks to ensure that changes follow team guidelines:
+  ```bash
+  dart run $REPO_ROOT/script/tool/bin/flutter_plugin_tools.dart publish-check --packages <changed_packages>
+  dart run $REPO_ROOT/script/tool/bin/flutter_plugin_tools.dart readme-check --packages <changed_packages>
+  dart run $REPO_ROOT/script/tool/bin/flutter_plugin_tools.dart version-check --packages <changed_packages>
+  dart run $REPO_ROOT/script/tool/bin/flutter_plugin_tools.dart license-check
+  dart run $REPO_ROOT/script/tool/bin/flutter_plugin_tools.dart repo-package-info-check
+  ```
+
+### Specialized Workflows
+
+- **Federated Plugin Development**: If you change multiple packages in a federated plugin that depend on each other, use `make-deps-path-based` to make their pubspec.yaml files use `path:` dependencies. This allows you to test them together locally.
+  ```bash
+  dart run $REPO_ROOT/script/tool/bin/flutter_plugin_tools.dart make-deps-path-based --target-dependencies=<changed_plugin_packages>
+  ```
+
+  The CI system will run tests with path-based dependencies automatically, so this is not required for PRs, but can be useful for local testing.
+- **Updating Dependencies**: To update a dependency across multiple packages:
+  ```bash
+  dart run $REPO_ROOT/script/tool/bin/flutter_plugin_tools.dart update-dependency --pub-package <dependency_name> --packages <packages_to_update>
+  ```
+- **Updating README Code Samples**: If you change example code that is included in a README.md:
+  ```bash
+  dart run $REPO_ROOT/script/tool/bin/flutter_plugin_tools.dart update-excerpts --packages <changed_packages>
+  ```
+
+## Code Generators
+
+Some packages use code generators, and changes to those packages require running the relevant code generators.
+
+- **Pigeon**: If you change a file in a `pigeons/` directory, you must run the Pigeon generator:
+  ```bash
+  # Run from the package's directory
+  dart run pigeon --input pigeons/<changed_file>.dart
+  ```
+- **Mockito**: If you change code in a package that uses `mockito` for tests (check `dev_dependencies` in `pubspec.yaml`), you must run its mock generator:
+  ```bash
+  # Run from the package's directory
+  dart run build_runner build -d
+  ```
+
+## Code Style
+
+All code must adhere to the repository's style guides. The `format` command handles most of this, but be aware of the specific style guides for each language, as detailed in [CONTRIBUTING.md](./CONTRIBUTING.md#style):
+- **Dart**: Flutter style, formatted with `dart format`.
+- **C++**: Google style, formatted with `clang-format`.
+- **Java**: Google style, formatted with `google-java-format`.
+- **Kotlin**: Android Kotlin style, formatted with `ktfmt`.
+- **Objective-C**: Google style, formatted with `clang-format`.
+- **Swift**: Google style, formatted with `swift-format`.
+
+## Version and CHANGELOG updates
+
+Any PR that changes non-test code in a package should update its version in pubspec.yaml and add a corresponding entry in CHANGELOG.md.
+
+**This process can be automated**. The `update-release-info` command is the preferred way to handle this. It determines changed packages, bumps versions, and updates changelogs automatically.
+```bash
+dart run $REPO_ROOT/script/tool/bin/flutter_plugin_tools.dart update-release-info \
+  --version=minimal \
+  --base-branch=origin/main \
+  --changelog="A description of the changes."
+```
+
+- `--version=minimal`: Bumps patch for bug fixes, and skips unchanged packages. This is usually the best option unless a new feature is being added.
+  - When making public API changes, use `--version=minor` instead.
+- `--base-branch=origin/main`: Diffs against the `main` branch to find changed packages.
+
+If you update manually, follow semantic versioning and the repository's CHANGELOG format.