Skip to content

Flutter web not rendering the UI on latest Chrome #171402

@leidig54

Description

@leidig54

Steps to reproduce

Unable to reproduce on my own device, however I am getting a concerningly rapid increase in reports from my users that the UI isn't showing when they visit the app on Chrome. Other browsers work fine. I managed to get a call with one of them to inspect the logs:

The website is https://pro.joinoto.com

Link to the same issue discussed elsewhere - https://forum.itsallwidgets.com/t/flutter-web-rendering-and-chrome-update/3643

This is pretty critical for us (healthcare app) and results in a complete blank screen.

Expected results

The UI should load.

Actual results

No UI - blank screen.

Code sample

https://pro.joinoto.com

Screenshots or Video

Screenshots / Video demonstration Image

Logs

Logs
[GroupMarkerNotSet (crbug.com/242999)!:A05028008C4B0000]A pro.joinoto.com/:1

Automatic fallback to software WebGL has been deprecated.
Please use the --enable-unsafe-swiftshader (about:flags#enable-unsafe-swiftshader) flag to opt in to lower security guarantees for trusted content.

Flutter Doctor output

Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.32.5, on macOS 15.5 24F74 darwin-arm64, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 16.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.3)
[✓] VS Code (version 1.101.1)
[✓] Connected device (3 available)
[✓] Network resources

Metadata

Metadata

Assignees

No one assigned

    Labels

    blockedIssue is blocked by another issuebrowser: chrome-desktoponly manifests in desktop Chromecustomer: crowdAffects or could affect many people, though not necessarily a specific customer.found in release: 3.32Found to occur in 3.32found in release: 3.33Found to occur in 3.33has reproducible stepsThe issue has been confirmed reproducible and is ready to work onplatform-webWeb applications specificallyr: fixedIssue is closed as already fixed in a newer versionteam-webOwned by Web platform team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions