- Dart analyzer terminates during development
- Dart analyzer terminates during development
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.
3679 changes · page 91 of 92
- Dart analyzer terminates during development
- Apple AppStore submission fails with error: “The bundle Runner.app/Frameworks/App.framework does not sue Infpport the minimum OS Version specified in the Info.plist”
- Setting a custom observatory port for debugging does not take effect
- Setting autoFillHint to text form field may cause focus issues
- Potential race condition in FlutterPlatformViewsController
- Support targeting physical iOS devices on Apple Silicon
- Reading Android clipboard may throw a security exception if it contains media
- Multiple taps required to delete text in some input fields.
- Webviews in hybrid composition can cause a crash.
- Stylus tap gesture is improperly registered.
- Android Studio 4.1 not properly supported.
- VoiceOver accessibility issue with some pages.
- Native webviews may not be properly disposed of in hybrid composition.
- The new --analyze-size flag crashes when used with --split-debug-info
- autovalidate property inadvertently removed.
- Flutter Activity causing exceptions in some Android versions.
- Layout modifications performed by background threads causes exceptions on IOS14.
The existing cupertino_icons, 0.1.3 icons, are based on iOS 11 aesthetics with sharp angles and thin lines.
The previous auto validation API for the `Form` and `FormField` widgets didn't control when auto validation should occur. So the auto validation for these widgets always happened on first build when the widget was first visible to the user, and you weren't able to control when the auto validation should happen.
The `flutter create` templates for apps and plugins no longer create Android wrapping based on the v1 Android embedding as part of our gradual Android v1 embedding deprecation process described in our Android Migration Summary.
- 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.