Скачать или смотреть What's new in Flutter 3.29.2

Flutter 3.29.2 incorporates several enhancements and fixes across different platforms. Specifically, updates address rendering issues with rotated text and resolve crashes on older Android devices when using the Impeller rendering engine. Furthermore, glyph errors on Android and iOS with Impeller have been corrected, and background image decoding on iOS has been improved. Web performance sees gains through CanvasKit rendering optimisations, alongside fixes for crashes related to image operations on iOS. Finally, Android platform view handling is enhanced, and issues with double downloads and simultaneous scrolling and animation crashes are resolved.

What is the significance of the change to the Skia fallback for pre-API 29 Android devices?
This change ensures that Flutter applications running on Android devices with API levels lower than 29 will consistently use the Skia rendering backend, regardless of the state of Impeller. This provides a more predictable rendering behaviour on older Android versions.

What does the "EXC_BAD_ACCESS" error related to Impeller indicate?
The "EXC_BAD_ACCESS Exception 1, Code 1, Subcode 0 greater than Attempted to dereference null pointer" error, as seen in the provided issue, signifies a critical crash within the Flutter engine's Impeller rendering backend on iOS. Specifically, the crash occurs during the setup of a render pass within the impeller::Canvas, indicating an attempt to access a memory location that is no longer valid or has not been properly initialised (a null pointer).

What information can be gleaned from the crash log provided in the "EXC_BAD_ACCESS" issue?
The crash log provides a detailed stack trace showing the sequence of function calls leading to the crash. It indicates that the issue originates within Impeller's rendering pipeline, specifically around canvas creation and display list processing (impeller::Canvas::SetupRenderPass, impeller::CanvasDlDispatcher::CanvasDlDispatcher, impeller::DisplayListToTexture). The thread that crashed is identified as "io.flutter.1.raster", which is responsible for rasterising Flutter's rendering commands.

What is the purpose of moving the AHB (Android Hardware Buffers) check into Flutter main?
Moving the AHB check into the Flutter main codebase centralises the logic for determining whether Android Hardware Buffers can be used for rendering. This can simplify the rendering pipeline and potentially allow for more consistent behaviour across different Android versions and devices. The associated change also prevents the disabling of ImageReader on Android API level 29.

Why did a previous attempt to move the AHB check and use Vulkan surfaces on API 29 get reverted?
A previous attempt to move the AHB check to Vulkan and use Vulkan surfaces on Android API level 29 was reverted due to issues where the Vulkan implementation was being incorrectly disabled on all devices. The fix in the relanded pull request specifically addresses this by ensuring Vulkan is only disabled on devices where AHB imports are known to not work correctly.

What is the rationale behind detecting MediaTek SoCs and falling back to GLES?
The Flutter team implemented logic to detect MediaTek system-on-chips (SoCs) on Android devices and force a fallback to OpenGL ES (GLES) instead of using the Vulkan rendering backend. This decision was made because certain MediaTek SoCs were found to have issues that did not work well with Vulkan at the time. The Flutter team indicated that this check might be relaxed in the future if MediaTek SoCs are found to offer better Vulkan support.

What does the Impeller error "Could not find glyph position in the atlas" signify?
This Impeller error, "Break on 'ImpellerValidationBreak' to inspect point of failure: Could not find glyph position in the atlas," indicates that the rendering engine was unable to locate the positional information for a specific glyph (character) within the font atlas being used for text rendering. This can occur due to various reasons, potentially including incorrect loading of the font atlas, issues with subpixel rendering calculations, or race conditions during text layout and rendering. Debugging information suggests the issue might be related to subpixel differences and the retrieval of the correct FontGlyphAtlas based on the rounded scale.

🌍 Stay Connected:
For more updates and content, follow me on:
🔹 LinkedIn:   / usamasarwarpro  
🔹 Facebook:   / usamasarwarpro  
🔹 Instagram:   / usamasarwarpro  
🔹 Twitter:   / usamasarwarpro  
🔹 Website: https://www.usama.dev
🔹 GitHub: https://github.com/UsamaSarwar
🔹 WhatsApp: https://wa.me/923100007773

📌 Keywords & Tags:
#Flutter #Podcast #UsamaSarwar