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.
30 changes · page 1 of 1
[flutter-intellij/4642]https://github.com/flutter/flutter-intellij/issues/4642 - Intellij/Android Studio plugins fail to show connected Android devices.
- xcdevice polling may use all free hard drive space
- Exhausted heap space can cause machine to freeze
- DropdownButtonFormField is not re-rendered after value is changed programmatically
- CupertinoSegmentedControl does not always respond to selections
- Incorrect git error may be presented when flutter upgrade fails
- Hot reload may fail after a hot restart
- iOS builds may fail with “The path does not exist” error message
- Updating `AndroidView` layer tree causes crash on Xiaomi and Moto devices
- Build `--tree-shake-icons` build option crashes computer
- Crash while getting static type context for signature shaking
- Xcode legacy build system causes build failures on iOS
- Regression in `Navigator.pushAndRemoveUntil`
Removed Flutter's `FloatingActionButton` (FAB) dependency on `ThemeData` accent properties.
Two new values were added to the `TargetPlatform` enum that could require additional cases in switch statements that switch on a `TargetPlatform` and don't include a `default:` case.
The local position returned by `AnnotatedRegionLayers` in an annotation search has been changed to be relative to the clipping region instead of the layer. This makes the local position more meaningful and reliable, but breaks code that directly performs annotation searches and uses the local position.
A new `ColoredBox` widget has been added to the framework, and the `Container` widget has been optimized to use it if a user specifies a `color` instead of a `decoration`.
Instances of `CupertinoTabBar` must have a `Localizations`parent in order to provide a localized `Semantics` hint. Trying to instantiate a `CupertinoTabBar` without localizations results in an assertion such as the following:
The generic type of `ParentDataWidget` has changed from `RenderObjectWidget` to `ParentData`.
`ImageCache` now has a method called `containsKey`. `ImageProvider` subclasses should not override `resolve`, but instead should implement new methods on `ImageProvider`. These changes were submitted as a single commit to the framework.
The `maxByteSize` of the `ImageCache` is no longer automatically made larger to accommodate large images.
`MouseTracker` and related symbols are moved from the `gestures` package, resulting in error messages such as undefined classes or methods. Import them from `rendering` package instead.
Removed `MouseTracker`'s methods `attachAnnotation`, `detachAnnotation`, and `isAnnotationAttached`.
[`CupertinoThemeData.brightness`] is now nullable.
This optimization improves performance for route transitions, but it may uncover missing calls to `setState` in your app.
no backwards-compatible way to make `AlertDialog` scrollable by default. Instead, the parameter will remain and you can set `scrollable` to true if you want a scrollable `AlertDialog`.
The state of a `TestTextInput` instance, a stub for the system's onscreen keyboard, is now reset between tests.
Add a field, `currentTextEditingValue`, to the `TextInputClient` interface to get the current value of an editable text field from a platform client.
A recent global key duplication detection refactor now requires `Element` subclasses that override the `forgetChild()` to call `super()`.
The `Route` class no longer manages its overlay entries in overlay, and its `install()` method no longer has an `insertionPoint` parameter. The `isInitialRoute` property in `RouteSetting` has been deprecated, and `Navigator.pop()` no longer returns a value.