Every change Boring Doc has indexed from official sources: breaking-change guides, hotfix changelogs and release notes. Filter by category, impact, platform, series and evidence type.
4 changes · page 1 of 1
`DropdownButton` and `DropdownButtonFormField` now include an `enabled` property to explicitly manage their interactive state, and the `onChanged` callback is no longer marked as `required`.
The Material and Cupertino design libraries are now available as standalone packages: `package:material_ui` and `package:cupertino_ui`. In Flutter 3.47, developers can opt in to these packages ahead of the formal deprecation of the in-framework design libraries.
To prevent `Intent`-based vulnerability exploits, the Flutter Android embedder (`FlutterActivity` and `FlutterFragmentActivity`) now verifies the sender of `Intent` objects before processing `EXTRA_INITIAL_ROUTE`, `EXTRA_DART_ENTRYPOINT`, `EXTRA_DART_ENTRYPOINT_ARGS`, `EXTRA_CACHED_ENGINE_ID`, and `EXTRA_CACHED_ENGINE_GROUP_ID`.
Previously, the Flutter Android embedding accepted engine configuration flags (such as `--dart-flags`, `--route`, or tracing flags) at launch time through Android `Intent` extras in all build modes. This mechanism allowed developers and tools—including the Flutter CLI when using `--use-application-binary`—to dynamically configure running applications without modifying their source code or manifest.