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.
28 changes · page 1 of 1
- macOS binaries not codesigned
- Segmentation fault on specific code
- Cocoapod transitive dependencies with bitcode fail to link against debug Flutter framework
- Adding a WidgetSpan widget causes web HTML renderer painting issue
- Dragging the "draggable" widget causes widget to freeze in the overlay layer on Web
- Flutter crash after going to version 2
- Unable to deep link into Android app
- NoSuchMethodError: The method 'cancel' was called on null at AnsiSpinner.finish
- Fix Autovalidate enum references in fix data
- When multiple Flutter engines are active, destroying one engine causes crash
- Flutter may show multiple snackbars when Scaffold is nested
- CanvasKit throws error when using Path.from
- '_initialButtons == kPrimaryButton': is not true
- Fix Autovalidate enum references in fix data
- Bad state exception can occur when HTTPS connection attempt errors or is aborted
- Uint8List reports type exception while using + operator in null safety mode
- Building for macOS target fails when Flutter is installed from website
A `BuildContext` parameter was added to `TextEditingController.buildTextSpan`.
`FlutterActivity` or `FlutterFragment`, and don't manually embed a `FlutterView` inside your own custom `Activity` (this should be uncommon), you can stop reading.
Flutter now defaults to _not_ clip except for a few specialized widgets (such as `ClipRect`). To override the no-clip default, explicitly set `clipBehavior` in widgets constructions.
A new method named `computeDryLayout` was added to the `RenderBox` protocol. Subclasses of `RenderBox` are expected to implement it to correctly report their desired size given a set of `BoxConstraints` during intrinsic calculations. Subclasses that implement `computeDryLayout` no longer need to override `performResize`.
This migration guide describes conversion of code that uses the `nullOk` parameter on multiple `of` static accessors and related accessors to use alternate APIs with nullable return values.
Flutter now applies the semantic label of `button` to all interactive Material Chips for accessibility purposes.
The `SnackBar` API within the `Scaffold` is now handled by the `ScaffoldMessenger`, one of which is available by default within the context of a `MaterialApp`.
The `ThemeData` properties that controlled the look of selected text in Material widgets have been moved into their own `TextSelectionTheme`. These properties include `cursorColor`, `textSelectionColor`, and `textSelectionHandleColor`. The defaults for these properties have also been changed to match the Material Design specification.
To control the behavior of `maxLength` in the `LengthLimitingTextInputFormatter`, use `maxLengthEnforcement` instead of the now-deprecated `maxLengthEnforced`.
If you write Java JUnit tests (such as Robolectric tests) against the Flutter engine's Java embedding and used the `FlutterMain.setIsRunningInRobolectricTest(true)` API, replace it with the following:
In accordance with Flutter's Deprecation Policy, deprecated APIs that reached end of life after the 1.22 stable release have been removed. This is the first time that deprecated APIs have been removed from Flutter, and some of these deprecations predate our migration guide policy.