material_3_demo does not start

[rusty-snake]

flutter run:

ERROR: lib/src/component_screen.dart:993:35: Error: Required named parameter 'groupValue' must be provided.
ERROR:             RadioListTile<Options>(
...
ERROR: lib/src/component_screen.dart:984:14: Error: The method 'RadioGroup' isn't defined for the class '_RadiosState'.
ERROR:  - '_RadiosState' is from 'package:material_3_demo/src/component_screen.dart' ('lib/src/component_screen.dart').
ERROR: Try correcting the name to the name of an existing method, or defining a method named 'RadioGroup'.
ERROR:       child: RadioGroup(
ERROR:              ^^^^^^^^^^
ERROR: Target kernel_snapshot_program failed: Exception

flutter doctor -v:

[✓] Flutter (Channel stable, 3.32.8, on Fedora Linux 42 (Workstation Edition) 6.15.8-200.fc42.x86_64, locale de_DE.UTF-8)
    • Flutter version 3.32.8 on channel stable at /home/.../flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision edada7c56e (vor 13 Tagen), 2025-07-25 14:08:03 +0000
    • Engine revision ef0cd00091
    • Dart version 3.8.1
    • DevTools version 2.45.1

[!] Android toolchain - develop for Android devices (Android SDK version 36.0.0) [1.576ms]
    • Android SDK at /home/.../android_sdk
    • Platform android-36, build-tools 36.0.0
    • Java binary at: /usr/bin/java
      This JDK was found in the system PATH.
      To manually set the JDK path, use: `flutter config --jdk-dir="path/to/jdk"`.
    • Java version OpenJDK Runtime Environment (Red_Hat-21.0.8.0.9-1) (build 21.0.8+9)
    ! Some Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses

[✗] Chrome - develop for the web (Cannot find Chrome executable at google-chrome) [21ms]
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

[✓] Linux toolchain - develop for Linux desktop
    • clang version 20.1.8 (Fedora 20.1.8-3.fc42)
    • cmake version 3.31.6
    • ninja version 1.12.1
    • pkg-config version 2.3.0
    ! Unable to access driver information using 'eglinfo'.
      It is likely available from your distribution (e.g.: apt install mesa-utils)

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/to/linux-android-setup for detailed instructions).

[✓] Connected device (1 available)
    • Linux (desktop) • linux • linux-x64 • Fedora Linux 42 (Workstation Edition) 6.15.8-200.fc42.x86_64

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 3 categories.

Commit: 2ea903a

[ericwindmill]

This is happening because material_3_demo was updated for the new release prematurely. Apologies for that. If you run flutter channel beta in your CLI, and then try to run the project, it will work. Otherwise, it will work on the stable channel on August 13th.

In general, it's beneficial for most developers use the beta channel of Flutter, unless you're pinning to a specific version.

[jwinarske]

@ericwindmill it would make a lot of sense to track stable, opposed to beta. Or at least have a branching scheme that supports stable.

It definitely adds a layer of confusion for devs, and impacts the usability of samples across the board. I need to evaluate removing samples from meta-flutter now, which is a big impact for folks.

[ericwindmill]

[@ericwindmill](https://github.com/ericwindmill) it would make a lot of sense to track stable, opposed to beta. Or at least have a branching scheme that supports stable.

It definitely adds a layer of confusion for devs, and impacts the usability of samples across the board.

I agree -- This repo typically is generally setup to track stable. In this instance, a mistake was made that I didn't realize until this issue was filed. (I'm not sure how it got through, to be honest, because CI should've prevented it.)

I need to evaluate removing samples from meta-flutter now, which is a big impact for folks.

Can you tell me more about this? Does meta-flutter depend on this repository? This repository is going through major changes in the very near future.

[ericwindmill]

Will be fixed by #2714