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.
29 changes · page 1 of 1
- Cannot deploy to physical device running iOS 14
- Performance regression for Image animation.
- WebView may freeze in release mode on iOS.
- Task switching may freeze on some Android versions.
- Building AARs may cause a stack overflow.
- Certain assets may cause issues with iOS builds.
- Passing null values from functions run via Isolates throws an exception.
- Wrong hour/minute order in timePicker in RTL mode.
- Crash due to serialization of generic DartType (UnknownType)
- build ios --release can crash with ArgumentError: Invalid argument(s)
- iOS platform view cancels gesture while a new clip layer is added during the gesture
- SliverList throws Exception when first item is SizedBox.shrink()
- TimePicker is not correct in RTL (right-to-left) languages
- New DatePicker widget is not fully localized
- Double date separators appearing in DatePicker, preventing date selection
- App.framework path in Podfile incorrect
- Creating an Android-only plug-in creates a no-op iOS folder.
In Flutter an `Intent` is an object that's typically bound to a keyboard key combination using the `Shortcuts` widget. An `Intent` can be bound to an `Action`, which can update the application's state or perform other operations. In the course of using this API, we identified several drawbacks in the design, so we have updated the Actions API to make it easier to use and understand.
A new getter, `TextInputClient.currentAutofillScope`, was added to the `TextInputClient` interface; all `TextInputClient` subclasses must provide a concrete implementation of `currentAutofillScope`.
A new set of basic material button widgets and themes have been added to Flutter. The original classes have been deprecated and will eventually be removed. The overall goal is to make buttons more flexible, and easier to configure via constructor parameters or themes.
Instances of `Dialog`, as well as `SimpleDialog`, `AlertDialog`, and `showTimePicker`, now have a default shape of a `RoundedRectangleBorder` with a `BorderRadius` of 4.0 pixels. This matches the current specifications of Material Design. Prior to this change, the default behavior for `Dialog.shape`'s `BorderRadius` was 2.0 pixels.
The framework throws an assertion error when it detects there are multiple navigators registered with one hero controller scope.
A new boolean getter `isWaitingForExitingDecision` was added to the route transition record and the `isEntering` getter was renamed to `isWaitingForEnteringDecision`. In the `resolve()` method for the transition delegate, use the `isWaitingForExitingDecision` to check if an exiting route actually needs an explicit decision on how to transition off the screen. If you try to make a decision for an existing route that _isn't_ waiting for a decision, Flutter throws an assertion error.
Instances of `RenderEditable` must be laid out before processing hit testing. Trying to hit-test a `RenderEditable` object before layout results in an assertion such as the following:
The services layer now depends on the scheduler layer. Previously, the opposite was true. This may affect you if you have defined custom bindings overriding Flutter's `SchedulerBinding` or `ServicesBinding`.
We changed the semantics traverse order of the overlay entries in modal routes. Accessibility talk back or voice over now focuses the scope of a modal route first instead of its modal barrier.
A new method,`void showAutocorrectionPromptRect(int start, int end)`, was added to the `TextInputClient` interface.
The `TestWidgetsFlutterBinding.clock` now comes from `package:clock` and not `package:quiver`.
Instances of `TextField` must have a `MaterialLocalizations` present in the widget tree. Trying to instantiate a `TextField` without the proper localizations results in an assertion such as the following: