Issue Link
#150546
Target
stable
PR Link
Cherry pick PR: flutter-team-archive/engine#54517
Original PR: flutter-team-archive/engine#54329
Changelog Description
Previously, Flutter Windows would always use format GL_RGBA8 to create textures. On older devices that do not support this texture format, this would fail.
Now, Flutter Windows uses the format GL_BGRA_EXT format if the device has extension GL_EXT_texture_format_BGRA8888, or otherwise it'll fallback to GL_RGBA.
Impacted Users
End-customers on older Windows devices cannot run apps built using Flutter Windows 3.22 or 3.24.
Impact Description
For affected end-users, the Flutter Windows app is completely broken: users see a black screen.
Workaround
The app developer can switch to Flutter Windows 3.21 or older.
Risk
medium
Test Coverage
no
Validation Steps
None of our devices reproduce this bug. Our existing tests cover this bug and would've reproduced the issue if ran on an affected device.
We verified by asking affected customers to run an app with the fix and confirming it works as expected (here, here, and more).
Issue Link
#150546
Target
stable
PR Link
Cherry pick PR: flutter-team-archive/engine#54517
Original PR: flutter-team-archive/engine#54329
Changelog Description
Previously, Flutter Windows would always use format
GL_RGBA8to create textures. On older devices that do not support this texture format, this would fail.Now, Flutter Windows uses the format
GL_BGRA_EXTformat if the device has extensionGL_EXT_texture_format_BGRA8888, or otherwise it'll fallback toGL_RGBA.Impacted Users
End-customers on older Windows devices cannot run apps built using Flutter Windows 3.22 or 3.24.
Impact Description
For affected end-users, the Flutter Windows app is completely broken: users see a black screen.
Workaround
The app developer can switch to Flutter Windows 3.21 or older.
Risk
medium
Test Coverage
no
Validation Steps
None of our devices reproduce this bug. Our existing tests cover this bug and would've reproduced the issue if ran on an affected device.
We verified by asking affected customers to run an app with the fix and confirming it works as expected (here, here, and more).