[camera_web] Fix TypeError when reading the torch capability - #12647

…er#192485)

flutter/packages@9af9c60...36e088a

2026-09-09 daniel.leon@cloudsufi.com [quick_actions] Adopt code-excerpts
for README (flutter/packages#12643)
2026-09-08 65155920+0xharkirat@users.noreply.github.com [camera_web] Fix
TypeError when reading the torch capability (flutter/packages#12647)
2026-09-08 gibbonsj97@gmail.com [google_maps_flutter_web] Avoid
replacing advanced marker content on move (flutter/packages#11952)
2026-09-08 mit@google.com [material_ui][cupertino_ui] Change issue
tracker label in pubspec.yaml (flutter/packages#12792)
2026-09-08 saurabhmirajkar000@gmail.com [material_ui] Fix FilledButton
Material 3 default style docs (flutter/packages#12620)
2026-09-08 21270878+elliette@users.noreply.github.com [infra] Use a
modified no-response workflow in flutter/packages
(flutter/packages#12745)
2026-09-08 21270878+elliette@users.noreply.github.com [material_ui]
Migrate M3 Banner template to use new gen_defaults
(flutter/packages#12734)
2026-09-08 engine-flutter-autoroll@skia.org Roll Flutter from
63170e9 to b444e78 (13 revisions) (flutter/packages#12791)
2026-09-08 fluttergithubbot@gmail.com Sync release-go_router-18.0.1 to
main (flutter/packages#12725)
2026-09-08 fluttergithubbot@gmail.com Sync release-material_ui-1.1.1 to
main (flutter/packages#12726)
2026-09-08 stuartmorgan@google.com [tool] Adopt `platform` 3.2.0
(flutter/packages#12789)
2026-09-07 50643541+Mairramer@users.noreply.github.com [material_ui] Fix
SliverGeometry maxPaintExtent assertion in CarouselView.weighted
(flutter/packages#12563)
2026-09-05 engine-flutter-autoroll@skia.org Roll Flutter from
5a6cfa7 to 63170e9 (15 revisions) (flutter/packages#12767)
2026-09-04 engine-flutter-autoroll@skia.org Manual roll Flutter from
70797e1 to 5a6cfa7 (52 revisions) (flutter/packages#12760)
2026-09-04 brackenavaron@gmail.com [material_ui] port drawer tests over
from flutter/widgets (flutter/packages#12711)
2026-09-04 tarrinneal@gmail.com add cooldown (flutter/packages#12708)
2026-09-04 joeldumasbg@gmail.com [in_app_purchase] Support StoreKit 2
introductory offer eligibility JWS (flutter/packages#12584)
2026-09-04 21270878+elliette@users.noreply.github.com [material_ui]
Migrate M3 Badge template to use new gen_defaults
(flutter/packages#12733)
2026-09-04 stuartmorgan@google.com [google_maps_flutter] Convert heatmap
controller to Swift (flutter/packages#12713)
2026-09-04 97480502+b-luk@users.noreply.github.com [material_ui] Remove
unused `maintainState` constructor parameter in `scaffold_test.dart`
(flutter/packages#12754)
2026-09-04 a1rwulf@users.noreply.github.com [video_player_avfoundation]
Route video over AirPlay (flutter/packages#12490)
2026-09-04 jerome.dellamaria@proton.me [google_fonts] Add
google_fonts_lite file to allow tree-shaking of the other huge files
(flutter/packages#11433)
2026-09-04 engine-flutter-autoroll@skia.org Roll Flutter from
0cbd1a4 to 70797e1 (27 revisions) (flutter/packages#12727)
2026-09-04 stuartmorgan@google.com Update Chrome for stable tests
(flutter/packages#12747)

If this roll has caused a breakage, revert this CL and set the roller
to dry run mode using the controls here:
https://autoroll.skia.org/r/flutter-packages-flutter-autoroll
Please CC flutter-ecosystem@google.com on the revert to ensure that a
human
is aware of the problem.

To file a bug in Flutter:
https://github.com/flutter/flutter/issues/new/choose

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

…#12647)

## What broke

`setFlashMode` and `takePicture` threw on any camera that has a flash.

The Image Capture specification declares `sequence<boolean> torch` in
`MediaTrackCapabilities`. `package:web` is generated from that specification, so
`torchNullable` was typed `JSArray<JSBoolean>?`.

No browser ships that shape. Chromium and WebKit both declare a bare `boolean torch`.
Reading the property threw before the torch could be applied. The error depends on
the compiler:

| Compiler | Error |
| --- | --- |
| DDC | `TypeError: true: type 'bool' is not a subtype of type 'JSArray<Object?>?'` |
| dart2js | `NoSuchMethodError: method not found: 'gq'` |
| dart2wasm | `ArgumentError: Invalid argument(s)` |

The same line held two more defects:

- `.first` gave the wrong answer for `[false, true]`. A specification-shaped sequence
  lists the values the source accepts, so that means the torch can be turned on.
- `.first` threw `StateError` on an empty sequence.

## The fix

Read `torch` as `JSAny?` and add `canEnableTorch`, which accepts either shape and
returns false for anything else.

A sequence is answered with `any` instead of `first`, and is only trusted when every
element is a boolean. Anything unrecognised raises `torchModeNotSupported` instead of
crashing, and prints a debug-only warning so the shape can be reported.

## Test matrix

| Browser reports | Before | After |
| --- | --- | --- |
| `true` | TypeError | torch on |
| `false` | TypeError | torchModeNotSupported |
| `[false, true]` | wrong answer | torch on |
| `[true]` | torch on | torch on |
| `[false]` | torchModeNotSupported | torchModeNotSupported |
| `[]` | StateError | torchModeNotSupported |
| key absent | torchModeNotSupported | torchModeNotSupported |
| `'yes'` | TypeError | torchModeNotSupported + warning |
| `['yes']` | TypeError | torchModeNotSupported + warning |

Nine cases are covered by integration tests. Six of them fail without this change.

## Devices tested

All nine shapes were run through the real plugin code on each of these. All passed.

| Device | Browser | Result |
| --- | --- | --- |
| Moto G56 5G, Android 16 | Chrome 151 | 9 / 9 |
| macOS 26.3 | Safari 26.3 | 9 / 9 |
| iPhone 17 Pro simulator, iOS 26.1 | Safari | 9 / 9 |
| macOS 26.3 | Chrome 151, dart2js and dart2wasm | 9 / 9 |

On the Moto G56 the rear camera reports `torch: true` as a bare boolean, and the flash
now turns on. The front camera does not report the key at all and raises
`torchModeNotSupported` as expected.

## What was added

- `canEnableTorch` on `NonStandardFieldsOnMediaTrackCapabilities`, which reads either shape.
- A debug-only `debugPrint` warning for a shape that is neither, so an unknown browser can
  be reported rather than failing quietly.
- Nine integration tests covering every shape, plus a check that a recognised shape never warns.
- A CHANGELOG entry and a version bump to `0.3.5+6`.

## What was removed

- The `JSArray<JSBoolean>?` type on `torchNullable`, which no browser matches.
- The `?.toDart.first.toDart ?? false` chain in `_setTorchMode`.

## Issues fixed by this PR

Fixes flutter/flutter#191384

## Pre-Review Checklist

🤖 Generated with [Claude Code](https://claude.com/claude-code)

…#12647)

## What broke

`setFlashMode` and `takePicture` threw on any camera that has a flash.

The Image Capture specification declares `sequence<boolean> torch` in
`MediaTrackCapabilities`. `package:web` is generated from that specification, so
`torchNullable` was typed `JSArray<JSBoolean>?`.

No browser ships that shape. Chromium and WebKit both declare a bare `boolean torch`.
Reading the property threw before the torch could be applied. The error depends on
the compiler:

| Compiler | Error |
| --- | --- |
| DDC | `TypeError: true: type 'bool' is not a subtype of type 'JSArray<Object?>?'` |
| dart2js | `NoSuchMethodError: method not found: 'gq'` |
| dart2wasm | `ArgumentError: Invalid argument(s)` |

The same line held two more defects:

- `.first` gave the wrong answer for `[false, true]`. A specification-shaped sequence
  lists the values the source accepts, so that means the torch can be turned on.
- `.first` threw `StateError` on an empty sequence.

## The fix

Read `torch` as `JSAny?` and add `canEnableTorch`, which accepts either shape and
returns false for anything else.

A sequence is answered with `any` instead of `first`, and is only trusted when every
element is a boolean. Anything unrecognised raises `torchModeNotSupported` instead of
crashing, and prints a debug-only warning so the shape can be reported.

## Test matrix

| Browser reports | Before | After |
| --- | --- | --- |
| `true` | TypeError | torch on |
| `false` | TypeError | torchModeNotSupported |
| `[false, true]` | wrong answer | torch on |
| `[true]` | torch on | torch on |
| `[false]` | torchModeNotSupported | torchModeNotSupported |
| `[]` | StateError | torchModeNotSupported |
| key absent | torchModeNotSupported | torchModeNotSupported |
| `'yes'` | TypeError | torchModeNotSupported + warning |
| `['yes']` | TypeError | torchModeNotSupported + warning |

Nine cases are covered by integration tests. Six of them fail without this change.

## Devices tested

All nine shapes were run through the real plugin code on each of these. All passed.

| Device | Browser | Result |
| --- | --- | --- |
| Moto G56 5G, Android 16 | Chrome 151 | 9 / 9 |
| macOS 26.3 | Safari 26.3 | 9 / 9 |
| iPhone 17 Pro simulator, iOS 26.1 | Safari | 9 / 9 |
| macOS 26.3 | Chrome 151, dart2js and dart2wasm | 9 / 9 |

On the Moto G56 the rear camera reports `torch: true` as a bare boolean, and the flash
now turns on. The front camera does not report the key at all and raises
`torchModeNotSupported` as expected.

## What was added

- `canEnableTorch` on `NonStandardFieldsOnMediaTrackCapabilities`, which reads either shape.
- A debug-only `debugPrint` warning for a shape that is neither, so an unknown browser can
  be reported rather than failing quietly.
- Nine integration tests covering every shape, plus a check that a recognised shape never warns.
- A CHANGELOG entry and a version bump to `0.3.5+6`.

## What was removed

- The `JSArray<JSBoolean>?` type on `torchNullable`, which no browser matches.
- The `?.toDart.first.toDart ?? false` chain in `_setTorchMode`.

## Issues fixed by this PR

Fixes flutter/flutter#191384

## Pre-Review Checklist

🤖 Generated with [Claude Code](https://claude.com/claude-code)