[path_provider] Document null vs UnsupportedError return semantics (#…

…11793)

Updates the dartdoc for `getDownloadsDirectory` in `path_provider` and the matching `getDownloadsPath` contract on `PathProviderPlatform` to explain both return-value cases:

- `null` — the platform supports the concept of a downloads directory but no such directory is currently available (concrete example: Linux without `xdg-user-dir` installed, or where `xdg-user-dir` fails when called).
- `UnsupportedError` — the current platform has no concept of a downloads directory at all.

Previously the dartdoc only mentioned the `UnsupportedError` case, which left users unsure when they might see a `null` result.

The wording matches the explanations already given by maintainers in the linked issue thread.

Fixes flutter/flutter#143238

## Pre-Review Checklist

This is a documentation-only change to public dartdoc comments. No code behavior changes; no new tests are required per the auto-exempt rules for changes that only affect comments/documentation.

[path_provider] Document null vs UnsupportedError return semantics (#…

…11793)

Updates the dartdoc for `getDownloadsDirectory` in `path_provider` and the matching `getDownloadsPath` contract on `PathProviderPlatform` to explain both return-value cases:

- `null` — the platform supports the concept of a downloads directory but no such directory is currently available (concrete example: Linux without `xdg-user-dir` installed, or where `xdg-user-dir` fails when called).
- `UnsupportedError` — the current platform has no concept of a downloads directory at all.

Previously the dartdoc only mentioned the `UnsupportedError` case, which left users unsure when they might see a `null` result.

The wording matches the explanations already given by maintainers in the linked issue thread.

Fixes flutter/flutter#143238

## Pre-Review Checklist

This is a documentation-only change to public dartdoc comments. No code behavior changes; no new tests are required per the auto-exempt rules for changes that only affect comments/documentation.

[webview_flutter] Implement getCookies (#10833)

This pr adds a way to retrive cookies from webview by using native platform api provided by `CookieManager` and `WKHTTPCookieStore`

Addresses flutter/flutter#27795

## Pre-Review Checklist

**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.

[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.

[in_app_purchase_android] Add showInAppMessages support (#107412) (#1…

…1214)

As mentioned in [#107412](flutter/flutter#107412), a new native feature (showInAppMessages) has been added.

```dart
final androidPlatformAddition = InAppPurchase.instance.getPlatformAddition<InAppPurchaseAndroidPlatformAddition>();
final result = await androidPlatformAddition.showInAppMessages();
```

## Pre-Review Checklist

**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.

[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.

[camera] Fix web facingMode capability handling (#11728)

[camera_web] Fix facingMode capability handling

Fixes flutter/flutter#174985

Prevents `availableCameras()` from throwing a TypeError when a browser returns an invalid `facingMode` capability. The plugin now treats invalid or missing facing mode capabilities as unavailable, allowing `availableCameras()` to continue and fall back to `CameraLensDirection.external`.

Tests:
- `dart format packages/camera/camera_web/lib/src/camera_service.dart packages/camera/camera_web/example/integration_test/camera_service_test.dart`
- `flutter analyze`
- `flutter test`
- `flutter drive --release --driver=test_driver/integration_test.dart --target=integration_test/camera_service_test.dart -d chrome`
- `flutter drive --release --driver=test_driver/integration_test.dart --target=integration_test/camera_web_test.dart -d chrome`

## Pre-Review Checklist

[pigeon] make swift enum CaseIterable (#11702)

instead of generating
```swift
enum FooEnum: Int {
  case foo = 0
  ...
```
we will now generate
```swift
enum FooEnum: Int, CaseIterable {
  case foo = 0
  ...
```
allowing consumers to use `FooEnum.allCases` to iterate over all possible enum values in swift platform code

fixes flutter/flutter#186447

## Pre-Review Checklist

**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.

[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.

[shared_preferences] Switch to Kotlin Pigeon (#11661)

Replaces the Java Pigeon generator with the Kotlin Pigeon generator, and updates API signatures and number handling for Kotlin/Java generator differences.

Part of flutter/flutter#158287

## Pre-Review Checklist

[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.

[pigeon] updates toString and isNullish methods (#11625)

prequel pr to #11352 to land non NI changes to simplify pr.

[google_maps_flutter_ios_sdk9] Fix title in google maps sdk9 readme (#…

…11826)

Google maps sdk9 readme had a typo where it said sdk10 instead in the title

*List which issues are fixed by this PR. You must list at least one issue.*

## Pre-Review Checklist

**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.

[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.

[webview] Add new method for cross plugin webview access (#11714)

A new way of supporting cross plugin communication is coming in Flutter 3.44 which allows for access to plugin published values through the `FlutterPluginBinding` on Android and the `FlutterPluginRegistry` on iOS. Update native WebView access to support these new methods and deprecate the old methods.

refs: flutter/flutter#121527 flutter/flutter#182753

## Pre-Review Checklist