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.
27 changes · page 1 of 1
- Glitches appear when scrolling on Android TV devices.
- Some widgets are not visible when nested inside of `ClipRRect` in CanvasKit mode when using Flutter web on Safari.
- fix error when using private variable setters in mixins on dart web.
- Type parameter nullability performs incorrectly in factory constructors.
- Fix null safety issue in TextFormField when Android devices pass no data
- Fix type conversion in TextInput that didn’t allow num types
- Fix unnecessary null safe exceptions in input decorators on Android
- Speculative fix for iOS screen flickering
- Using WebView leads to size error in platform_views since Flutter 3.3.0
- Apps crash when `FadeInImage` switches from cached to uncached images.
- Apps crash when combining emojis and Korean text.
- Move documentation build and deployment to post-submit.
- When debugging web apps, erroneous errors are displayed.
- On Flutter desktop apps, pixel snapping performs incorrectly when using opacity layers at certain DPRs and screen sizes.
- On android devices with a refresh rate greater than 60hz, frames jump when scrolling.
- App crashes on latest versions when AnimatedContainer / Container height is set to 0 and throws uncaught exception
- Fatal crash with java.lang.AssertionError when selecting text in TextField.
- Security vulnerability: There is a auth bypass vulnerability in Dart SDK, specifically dart:uri core library, used to parse and validate URLs.
- Avoid CFE crash when input contains invalid super parameters usage.
- Signing errors on iOS pod bundle resources on Xcode 14 "Signing for "x" requires a development team."
- Flutter tools ShaderCompilerException with exit code -1073740791.
- Custom embedders fail to build for 32 bit targets.
- Android plugins crash when using platform view's Virtual Display fallback.
- Package assets fail to load.
- Text rendering is handled incorrectly.
- Incorrect type propagation when using `late` variables in catch blocks.
- Windows apps crash when accessibility is enabled on apps that use widgets with custom semantic actions.